Open EmrePiconbello opened 1 year ago
Is this error log from the daemon or from the archive process?
From archive process
To follow this up because of other weird behavior with postgre we move the postgre to remote isolated instance. Since we move it to remote postgre other issue we reported didn't happen. The remote postgre was causing this error to happen but after some conversation with Gareth we also learn remote postgre cause node to lag behind the chain. Under these circumstances I am very worried about sustainability of archive node.
Preliminary Checks
Description
2023-10-20 23:46:16 UTC [Error] Exception while handling RPC server request from "": $error error: "(src/connection.ml.Handshake_error.Handshake_error((Reading_header_failed(monitor.ml.Error(\"Rpc_transport: message too small or too big\"((Message_size 246454534799363)(Max_message_size 104857600))async_rpc/src/rpc_transport.ml:45:14)(\"Raised at BaseError.raise in file \\"src/error.ml\\" (inlined), line 8, characters 14-30\"\"Called from Core_kernel__Error.failwiths in file \\"src/error.ml\\", line 5, characters 2-50\"\"Called from Async_rpcRpc_transport.Unix_reader.read_forever.loop in file \\"async_rpc/src/rpc_transport.ml\\", line 78, characters 8-52\"\"Called from Async_unixReader0.Internal.read_one_chunk_at_a_time.(fun).loop.(fun) in file \\"src/reader0.ml\\", line 533, characters 27-61\"\"Called from Async_kernelJob_queue.run_job in file \\"src/job_queue.ml\\" (inlined), line 128, characters 2-5\"\"Called from Async_kernel__Job_queue.run_jobs in file \\"src/job_queue.ml\\", line 169, characters 6-47\")))))"
Steps to Reproduce
1.Run archive node 2.Follow the logs 3.You will see the error in every few hours.
...
Expected Result
Archive node archiving without missing a block
Actual Result
Archive missing blocks making the archive incomplete. Requires a recovery
How frequently do you see this issue?
Frequently
What is the impact of this issue on your ability to run a node?
High
Status
Additional information
No response