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
We have 3 machines which have been synced using the same config. We were migrating from machine 1 to machine 2 and machine 2 crashed.
So we tried to move the key back to machine 1, then machine 1 stopped syncing. We resynced machine 2 from the snapshot and whenever the key is not on either machine, they run properly with no issues. But the moment we restart with the key, the nodes stop syncing.
On machine 3, we did fresh snapshot download and restarted with the validator key. But first we see an error like this:
WARN garbage collection: Error in gc: GC Error: block on canonical chain shouldn't have refcount 0
ERROR metrics: Error when exporting postponed receipts count DB Not Found Error: BLOCK: AX8wFPoyVoULT9N7hMcVLxJtPBYZj4EkBhbhThKYZ7WN.
But once the validator key is removed and the node is restarted, the node syncs with no issues. Then, if we put the validator key back, it stops syncing.
The validator key doesn't seem to be running on any machine.
We also saw another error while trying to sync machine 3 from snapshot(after 1 restart or neard) with the validator key on it:
Could you share config.json for each machine?
Do you move node_key.json too or just validator_key.json?
So after upgrading all machines to 2.2.0, it only works if neither machine run as validator?
Contact Details
suryansh@luganodes.com
What happened?
We have 3 machines which have been synced using the same config. We were migrating from machine 1 to machine 2 and machine 2 crashed.
So we tried to move the key back to machine 1, then machine 1 stopped syncing. We resynced machine 2 from the snapshot and whenever the key is not on either machine, they run properly with no issues. But the moment we restart with the key, the nodes stop syncing.
On machine 3, we did fresh snapshot download and restarted with the validator key. But first we see an error like this:
Then after a restart, we see:
and if we restart again, we see:
But once the validator key is removed and the node is restarted, the node syncs with no issues. Then, if we put the validator key back, it stops syncing.
The validator key doesn't seem to be running on any machine.
We also saw another error while trying to sync machine 3 from snapshot(after 1 restart or neard) with the validator key on it:
And then once the logs start moving we see logs like this:
Version
Node type
RPC (Default)
Are you a validator?
Relevant log output
INFO stats: State 4cupEDQnemFXCa6s9Z3ankCBgj4sXDSnb2SP4KJTX51T[0: parts] 32 peers ⬇ 5.13 MB/s ⬆ 4.08 MB/s 0.00 bps 0 gas/s CPU: 296%, Mem: 22.4 GB INFO stats: State 4cupEDQnemFXCa6s9Z3ankCBgj4sXDSnb2SP4KJTX51T[0: apply in progress] 31 peers ⬇ 5.27 MB/s ⬆ 4.63 MB/s 0.00 bps 0 gas/s CPU: 306%, Mem: 6.47 GB
Node head info
Node upgrade history
DB reset history
Multiple times today on all our machines.
The text was updated successfully, but these errors were encountered: