-
Notifications
You must be signed in to change notification settings - Fork 1.7k
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Stage 3 block verification failed (with --light option) #6402
Comments
the 0 hdr/s issue is logged here #6319 and the block verification issue might be related to this issue. you could try resetting the database and sync again. note that light client support is still highly experimental and you should not use it in production. |
I just wanted to note that I had exactly the same error on the same block, with the light client:
I'm using |
Me also, with exactly the same numbers. I don't have any compaction setting.
Given 3 people with exactly matching numbers, would you consider reopening, @5chdn ? Also regarding your work-around Do you mean |
Can not reproduce this with latest master 1.8.x |
Any tips on my question about the database reset would be appreciated. Doing my |
Yes resetting the database means you start at |
I can confirm I've just had the same issue twice in a row, resetting the db in between. Twice on the same block, there must be something in it that light mode doesn't like.
I'm running parity 1.7.2 downloaded from https://github.com/paritytech/parity/releases, running on debian testing. |
I have the same issue on parity 1.7.3 on Mac OS X High Sierra.
Did |
Can confirm this issue persists even on |
This issue is also present for me in the |
I am having the "Stage 3 block verification failed" error and synchronization stuck at block # 4370000 without --light option. In fact I ran parity without any arguments. OS: Windows 10 x64. Parity version: Parity/v1.7.0-beta-5f2cabd-20170727/x86_64-windows-msvc/rustc1.18.0
|
@deonis78 there was a hard-fork on block 43700000 - please upgrade to 1.8.2 :) |
@5chdn Thank you very much for the explanation! Upgrading to 1.8.2 has helped. |
Can confirm just got this with latest version of Parity. Running full parity node with archiving and fat-db, having to sync on a SSD RAID0 array to try and make progress. Starting Parity/v1.10.0-nightly-c060d95-20180209/x86_64-linux-gnu/rustc1.23.0
However it still keeps syncing blocks so hasn't frozen at this block. So is this a warning or a error? |
If it keeps syncing it just received a block from another chain and discarded it, syncing from other light peers. In that cause it should be considered a warning not an error. It's notable that this appears only on even blocks, e.g., 3100000, 4370000. So closing this as non-issue. |
Still happens with 1.11.6 |
closing as hardcoded headers should help. Please reopen with logs if it still happens. |
I'm running:
Operating system: Manjaro (Linux, Arch based)
Parity version: 1.7.0-1 , installed from the repos
I ran parity with the --light option. Several times I had the sync process stop advancing (while still giving updates in the cli, just with hdr/s = 0 and the block being the same). I restarted parity whenever that happened (ctrl-c, and re-run, like 3-4 times).
Now I got the error:
and I'm stuck with it. I guess I could try to clear the database/settings and re-run parity, but I thought there might be some additional debugging info that could be extracted from the situation. It's a pretty clean install, I only added the following as a config file:
The text was updated successfully, but these errors were encountered: