Classic: no syncing on 2.7.1 #11431
Comments
|
I've got the same problem. I will add that migration does not start on ethereum classic (it starts on ethereum mainnet, ropsten, but not classic). It begins on 2.7.0 |
|
Yup, same problem with me. Even changing the bootnodes to ones that I confirmed are active did not help. My node finds a few peers, but never syncs anything, and the blocks db seems to have reset so that latest block is showing up as 0 after updating |
|
Can you please check if the situation is improved on ETC using the 2.7.2 pre-release builds? Mac: https://gitlab.parity.io/parity/parity-ethereum/-/jobs/376316/artifacts/download |
|
No, this doesn't appear to fix the problem, in fact, when updating from 2.5 or 2.6 to 2.7.X (including this 2.7.2 pre release which I just checked), the whole DB seems to be destroyed. Logs from 2.5.13 running -lsync=debug (appearing to operate normally): Then I stopped parity, updated to 2.7.2, and got these logs: As you can see, after updating, the best block in the db is set to 0 (this is also reflected when getting latest block number from the rpc), and then parity will basically never find any peers, and no matter how long I leave it running (even if it finds peers), it will never sync any blocks (even after waiting for over an hour) I also don't see the log that shows db updating from 14 to 15 when updating to 2.7.2 like I did when upgrading to 2.7.X on my ropsten/mainnet nodes. Maybe that has something to do with it? |
The latest DB version is 14; db versions are not tied to release versions, so it could stay I can see the problem here too, just like you describe it. With 2.6.8 syncing works fine; on 2.7.2 it doesn't find any peers at all (and even when it does, it does not sync). |
I see. Regardless, when updating to 2.7.X from 2.5 or 2.6, the DB latest block seems to get reset to 0 on classic chains. I've tried this 3 or 4 times, and it happens every time. |
Confirmed. Or rather, if I sync classic for a while on 2.6.8 and then switch to 2.7.2 RPC reports |
|
Seems like there's a genesis hash mismatch between 2.6.x and 2.7.x which means that a 2.7 node will reject peers. E.g.: |
|
Hey, please reopen this issue if you still have the issue when Then just run it by $ curl -O https://github.com/paritytech/parity-ethereum/blob/stable/ethcore/res/ethereum/classic.json
$ parity --chain classic.json |
Hi,
I had Parity v2.5.13 on the classic chain, it worked fine. I updated to v2.7.1 without changing anything in the configuration and now it is stuck in this state:
actual state:
Parity stuck and does not start synchronisation. The
eth_blockNumbercall returns '7', although it was fully synchronised with the 2.5.13 version.expected behavior
Parity should keep synchronising and return an up to date block height.
steps to reproduce
troubleshooting
I have tried the following:
reserved_peersline in my config which points to a file containing the following nodes:I have removed the line from the config and restarted Parity again, but it did not solve the problem.
The text was updated successfully, but these errors were encountered: