Error: Error handling packet: error: relation "vehicle" does not exist
Closed this issue · 2 comments
sentry-io commented
Sentry Issue: RUSTY-MOTORS-SERVER-1E
Error: Error handling packet: error: relation "vehicle" does not exist
File "../packages/transactions/src/internal.ts", line 90, in processInput
const err = new Error(`Error handling packet: ${String(error)}`);
File "../packages/transactions/src/internal.ts", line 172, in receiveTransactionsData
const response = await processInput({
drazisil commented
[20:50:28.143] DEBUG (mcos:getCompleteVehicleInfo): Received Message: GenericRequest {"msgNo":145,"data":"02000000","data2":"00000000a33572966d37248836386d9784a8a21e99188cd176fc8b13d6317844191e828062ed3e00f8fb26ad55f684a65f802d0a08e0f07e4052d9b6063d678da14e2399428ec034cf0a9fc936eaf5ee8d0c853064910b4561f5c433133bb0bbe41e1c8007c3ddd80dc89e049d9e87f74eb73133ea7afd790b2b02689f26694434824cc3598bae4436edaf3fbe292f80e56101515781bb7ae0dcd580d4523bd1b0ca0176d12a8e4e6215d1bd7884ff513fd496b64e57ffa374b75d3ddb779ba7cf8809cb283726e9233cb5b8b48a56baf33182e98ffcd6639933cf4878e10aa598c067b957df14b6ad23cb5c2d4c305f0b3bcd5c326597234cbd763382d66bbfac1c3538a2b28f08f244937131710651983776"}
[20:50:28.143] DEBUG (mcos:getCompleteVehicleInfo): Requesting vehicleId: 2 delta: 0
[20:50:28.143] DEBUG (mcos:getCompleteVehicleInfo): Vehicle with id 2 not found in cache, fetching from DB
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: Error handling packet: error: relation "vehicle" does not exist
at processInput (file:///home/drazisil/mcos/dist/server.js:8904:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async receiveTransactionsData (file:///home/drazisil/mcos/dist/server.js:8949:20)
[20:50:28.171] ERROR (mcos:getCompleteVehicleInfo): Error in Fetching car: error: relation "vehicle" does not exist
[20:50:28.171] ERROR (mcos:getCompleteVehicleInfo): Error handling data: Error: Error handling packet: error: relation "vehicle" does not exist
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: Message Number Not Handled: 25140 (Unknown
at processInput (file:///home/drazisil/mcos/dist/server.js:8908:9)
at receiveTransactionsData (file:///home/drazisil/mcos/dist/server.js:8949:26)
at Socket.<anonymous> (file:///home/drazisil/mcos/dist/server.js:3055:5)
at Socket.emit (node:events:519:28)
at Socket.emit (node:domain:488:12)
at addChunk (node:internal/streams/readable:559:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
at Readable.push (node:internal/streams/readable:390:5)
at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
[20:50:28.178] DEBUG (mcos:getCompleteVehicleInfo): Message type: Server
[20:50:28.178] DEBUG (mcos:getCompleteVehicleInfo): Calling onData handler
[20:50:28.178] TRACE (mcos:getCompleteVehicleInfo): Raw message: 0d01544f4d43190000000822e89e3cd92ce9c711167227b32c7dcaf63e2e148c6028f95e745fd410ada1035c5409c02d59583e4d595f8ed199a66c02aa28414c929a209b2f1ade4d562cdbcd64fab6c17888089a36e69c8db8c17fe95b8710d215db132ebf7afcf8741bf2c9f6358ba7c8ea3ab4eb486053dcf534ff39e5eb58830ed8d8f615732fc1c61791f7c83b6699d6a70d11b3bad9d20fc2a5df56df378749cafaf34f5f1e9c94cd85ff5ddd79cb30912ffc7bd8a179b9098e806c698c20bf6ff9475ada0bc6a540b9f23953eb7234b9a6ca5a91e8557fc26575dd5aa0ed04825f1707ec840fd22590c89a8ea226bbe779e0d43e42fa56cb4e111c84a378597ea5fb764107421a1cef27c9fd0
[20:50:28.178] DEBUG (mcos:getCompleteVehicleInfo): Received Transaction Server packet: ca06a25c-4de4-4f3a-a2a2-ac9caac0c313
[20:50:28.178] DEBUG (mcos:getCompleteVehicleInfo): Received Transaction Server packet: ServerMessage: {"header":"ServerHeader: {\"length\":269,\"mcoSig\":\"TOMC\",\"sequence\":25,\"flags\":8}","data":"22e89e3cd92ce9c711167227b32c7dcaf63e2e148c6028f95e745fd410ada1035c5409c02d59583e4d595f8ed199a66c02aa28414c929a209b2f1ade4d562cdbcd64fab6c17888089a36e69c8db8c17fe95b8710d215db132ebf7afcf8741bf2c9f6358ba7c8ea3ab4eb486053dcf534ff39e5eb58830ed8d8f615732fc1c61791f7c83b6699d6a70d11b3bad9d20fc2a5df56df378749cafaf34f5f1e9c94cd85ff5ddd79cb30912ffc7bd8a179b9098e806c698c20bf6ff9475ada0bc6a540b9f23953eb7234b9a6ca5a91e8557fc26575dd5aa0ed04825f1707ec840fd22590c89a8ea226bbe779e0d43e42fa56cb4e111c84a378597ea5fb764107421a1cef27c9fd"}
[20:50:28.178] DEBUG (mcos:getCompleteVehicleInfo): Message is encrypted
[20:50:28.178] DEBUG (mcos:getCompleteVehicleInfo): Encrypted buffer: 22e89e3cd92ce9c711167227b32c7dcaf63e2e148c6028f95e745fd410ada1035c5409c02d59583e4d595f8ed199a66c02aa28414c929a209b2f1ade4d562cdbcd64fab6c17888089a36e69c8db8c17fe95b8710d215db132ebf7afcf8741bf2c9f6358ba7c8ea3ab4eb486053dcf534ff39e5eb58830ed8d8f615732fc1c61791f7c83b6699d6a70d11b3bad9d20fc2a5df56df378749cafaf34f5f1e9c94cd85ff5ddd79cb30912ffc7bd8a179b9098e806c698c20bf6ff9475ada0bc6a540b9f23953eb7234b9a6ca5a91e8557fc26575dd5aa0ed04825f1707ec840fd22590c89a8ea226bbe779e0d43e42fa56cb4e111c84a378597ea5fb764107421a1cef27c9fd
[20:50:28.178] DEBUG (mcos:getCompleteVehicleInfo): Decrypted buffer: 3462927323e0e2d93fab202d663a66f84702b3b58f3c7cf09e59068c2ee0f85cd2859066415bf2160c15cd14f1028976dce77e6d975ffeda2dee625645cc1a3d51e94277be91d38f8ae4f3479e967e0515a3f30b20dc2d26a518b216c2c0f0baa9a5e97e9337d3df5fb3cb6e8b0403218c16242d4f12f910e3908ca588ccd7a42b2e1a34a43c09f1d22634f31328fc8dfac1ca4bfa02b697278a846f8fb368b65d5e24647045b0fd46705b67ce80fe53548baacccc994d56aaac28eeb2606f1a281a6c2c29174164fc6ab7956a0a68c589f1d288857dcc18d1b52157637632f1ae8a60d86968aafbfd43ac673c5fadbd0f165e9ebf977eb758403e3ee806a6859c718529
[20:50:28.178] DEBUG (mcos:getCompleteVehicleInfo): Decrypted message: ServerMessage: {"header":"ServerHeader: {\"length\":269,\"mcoSig\":\"TOMC\",\"sequence\":25,\"flags\":0}","data":"3462927323e0e2d93fab202d663a66f84702b3b58f3c7cf09e59068c2ee0f85cd2859066415bf2160c15cd14f1028976dce77e6d975ffeda2dee625645cc1a3d51e94277be91d38f8ae4f3479e967e0515a3f30b20dc2d26a518b216c2c0f0baa9a5e97e9337d3df5fb3cb6e8b0403218c16242d4f12f910e3908ca588ccd7a42b2e1a34a43c09f1d22634f31328fc8dfac1ca4bfa02b697278a846f8fb368b65d5e24647045b0fd46705b67ce80fe53548baacccc994d56aaac28eeb2606f1a281a6c2c29174164fc6ab7956a0a68c589f1d288857dcc18d1b52157637632f1ae8a60d86968aafbfd43ac673c5fadbd0f165e9ebf977eb758403e3ee806a6859c718529"}
[20:50:28.178] DEBUG (mcos:getCompleteVehicleInfo): Calling processInput()
drazisil commented
Root cause: Database table vehicle
not found.
Solution: Verify required database tabled exist on server boot.