You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Neither of those are crashes. Those are caught exceptions, handled successfully. From the look of it, you have a bad peer. Remove all but one of them and allow your node to synchronize completely, then add them back one by one until you determine which peer is persistently sending you bad blocks.
The blocks themselves may not be bad. On closer examination, it looks like your node is suffering frequent forks during synching, which is not expected to happen with 1.1.1. Verify you're actually running 1.1.1 with cleos get info to your node. The reported version should be 40a2076.
You didn't include anything in the pasted output indicating an actual crash, but there is another very similar issue, filed today, that did. You may be experiencing #4884.
Hi there,
I'm re-sync'ing one of our nodes on the main-net, but when we sync'ed at about block number - #5826476, it crashed.
eos v1.1.1
config.ini
error:
I reproduced many times that it crashed every time.
Please help.
thanks.
The text was updated successfully, but these errors were encountered: