Closed Frixoe closed 1 month ago
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?
@Frixoe do you still have this problem?
@telezhnaya No we don't.
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
Node head info
Node upgrade history
DB reset history