search

neo-project / neo-node

MIT License
229 stars 224 forks source link

node: not syncing #873

Closed whitebit-robot closed 11 months ago

whitebit-robot commented 2 years ago

From snapshot: block: 290070/290070 connected: 0 unconnected: 0 [19:19:36.703] Operation is not valid due to the current state of the object.

From scratch: peers are connected but sync process stucks on the same height - 290070/300070. The message in logs is the same: Operation is not valid due to the current state of the object.

Node verison: 3.3.1 OS: ubuntu 18.04

Any suggestions how to fix this, please?

whitebit-robot commented 2 years ago

Solution: don't use version 3.3.1 Old version 3.2.1 works perfectly.

whitebit-robot commented 2 years ago

Ok, it does not really work. Version 3.2.1 stucks on block 1758990 with the below notification: Operation is not valid due to the current state of the object.

Upgrade to the latest version leads to error: Corruption: corrupted compressed block contents

How to make it work, guys?

EdgeDLT commented 2 years ago

Version 3.2.1 stucks on block 1758990 with the below notification: Operation is not valid due to the current state of the object.

Did you fully resync after downgrading to the correct version? Sounds like you have a state mismatch.

whitebit-robot commented 2 years ago

Yes, I fully resync. You can test it on your side. Linux version stucks. Windows version is OK.

shargon commented 11 months ago

Old, if remains, please re-open