Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Stage 5 block verification failed for #7020003 in Kovan sync #8506

Closed
AyushyaChitransh opened this issue Apr 27, 2018 · 9 comments
Closed

Stage 5 block verification failed for #7020003 in Kovan sync #8506

AyushyaChitransh opened this issue Apr 27, 2018 · 9 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P9-somedaymaybe 🌞 Issue might be worth doing eventually.
Milestone
2.0 Ethereum

Comments

@AyushyaChitransh
Copy link

I'm running:

  • Which Parity version?: version Parity/v1.9.7-unstable-7919629f3-20180423/x86_64-linux-gnu/rustc1.25.0 and Parity/v1.10.2-unstable-f4ae813fd-20180423/x86_64-linux-gnu/rustc1.25.0
  • Which operating system?: Linux
  • How installed?: from source
  • Are you fully synchronized?: no
  • Which network are you connected to?: kovan
  • Did you try to restart the node?: yes

What Fails:

./target/release/parity --chain kovan --base-path ~/kovan/

But after snapshots are complete, I get the following error:

Stage 5 block verification failed for #7020003 (d819?3088)
Error: Block(InvalidGasUsed(Mismatch { expected: 519436, found: 504783 }))

Tried these too:

  • Restarting parity with same --base-path after snapshots were downloaded.
  • Restarting parity with new --base-path

What works:

./target/release/parity --chain kovan --base-path ~/kovan/ --no-warp

This has been syncing properly for now. And peers are also there.

Below are the logs for failed attempts to sync

[ayushyac@ip-10-25-32-150 parity]$ ./target/release/parity --chain kovan --base-path ~/kovan
2018-04-27 13:36:25 UTC Starting Parity/v1.9.7-unstable-7919629f3-20180423/x86_64-linux-gnu/rustc1.25.0
2018-04-27 13:36:25 UTC Keys path /home/ayushyac/kovan/keys/Kovan
2018-04-27 13:36:25 UTC DB path /home/ayushyac/kovan/chains/kovan/db/9bf388941c25ea98
2018-04-27 13:36:25 UTC Path to dapps /home/ayushyac/kovan/dapps
2018-04-27 13:36:25 UTC State DB configuration: fast
2018-04-27 13:36:25 UTC Operating mode: active
2018-04-27 13:36:25 UTC Configured for Kovan using AuthorityRound engine
2018-04-27 13:36:31 UTC Public node URL: enode://31df2d541a8088a56ce76394cd4b05b8e9d406cf32d385e71b9ee1d446be059ede35771072c57edf48df1f1da5a852921a87ae5e82915704f584b0399eb87b7c@10.25.32.150:30303
2018-04-27 13:36:34 UTC Stage 5 block verification failed for #7020003 (d819?3088)
Error: Block(InvalidGasUsed(Mismatch { expected: 519436, found: 504783 }))
^C2018-04-27 13:36:36 UTC Finishing work, please wait...
[ayushyac@ip-10-25-32-150 parity]$ rm -rf ~/kovan/
[ayushyac@ip-10-25-32-150 parity]$ ./target/release/parity --chain kovan --base-path ~/kovan
2018-04-27 13:36:44 UTC Starting Parity/v1.9.7-unstable-7919629f3-20180423/x86_64-linux-gnu/rustc1.25.0
2018-04-27 13:36:44 UTC Keys path /home/ayushyac/kovan/keys/Kovan
2018-04-27 13:36:44 UTC DB path /home/ayushyac/kovan/chains/kovan/db/9bf388941c25ea98
2018-04-27 13:36:44 UTC Path to dapps /home/ayushyac/kovan/dapps
2018-04-27 13:36:44 UTC State DB configuration: fast
2018-04-27 13:36:44 UTC Operating mode: active
2018-04-27 13:36:44 UTC Configured for Kovan using AuthorityRound engine
2018-04-27 13:36:50 UTC Public node URL: enode://040a39139aa1cf1604f3119b57f27ba2d88384b1f585677b016e3b55512e176b4df776b1dac1532c704a0a2f58a0e649bdcb870e9df9f0ef237a29e942d922df@10.25.32.150:30303
2018-04-27 13:36:54 UTC Syncing snapshot 21/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:37:04 UTC Syncing snapshot 43/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:37:09 UTC Syncing snapshot 49/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:37:19 UTC Syncing snapshot 61/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:37:25 UTC Syncing snapshot 68/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:37:34 UTC Syncing snapshot 78/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:37:39 UTC Syncing snapshot 83/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:37:46 UTC Syncing snapshot 91/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:37:54 UTC Syncing snapshot 107/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:37:59 UTC Syncing snapshot 117/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:38:04 UTC Syncing snapshot 125/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:38:09 UTC Syncing snapshot 134/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:38:14 UTC Syncing snapshot 141/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:38:19 UTC Syncing snapshot 150/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:38:24 UTC Syncing snapshot 159/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:38:29 UTC Syncing snapshot 168/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:38:34 UTC Syncing snapshot 174/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:38:39 UTC Syncing snapshot 183/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:38:45 UTC Syncing snapshot 190/227        #0    4/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:38:55 UTC Syncing snapshot 203/227        #0    5/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:39:05 UTC Syncing snapshot 221/227        #0    5/25 peers   8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:39:16 UTC Stage 5 block verification failed for #7020003 (d819?3088)
Error: Block(InvalidGasUsed(Mismatch { expected: 519436, found: 504783 }))
2018-04-27 13:39:39 UTC     #17946    1/25 peers   6 MiB chain 131 KiB db 0 bytes queue 949 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:40:14 UTC     #25566    1/25 peers   4 MiB chain 131 KiB db 0 bytes queue 1 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:40:44 UTC     #32354    1/25 peers   6 MiB chain 131 KiB db 0 bytes queue 3 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:41:19 UTC     #39536    1/25 peers   7 MiB chain 131 KiB db 0 bytes queue 3 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:41:54 UTC     #48680    1/25 peers   6 MiB chain 131 KiB db 0 bytes queue 5 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-04-27 13:42:29 UTC     #57443    1/25 peers   6 MiB chain 131 KiB db 0 bytes queue 5 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
@Tbaut
Copy link
Contributor

Tbaut commented Apr 30, 2018

What is the difference with #6503 ?

@Tbaut Tbaut added Z7-duplicate 🖨 Issue is a duplicate. Closer should comment with a link to the duplicate. F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. labels Apr 30, 2018
@Tbaut Tbaut added this to the 1.11 milestone Apr 30, 2018
@AyushyaChitransh
Copy link
Author

@Tbaut I faced #6503 on my private chain and that was due to incorrect genesis file. Also, user in that issue told that

it tries to download the same snapshot for eternity and won't proceed. And this time it panicked.

Following things are different in this issue:

  • Private chain is not being used, instead, this happened on kovan
  • The problem does not seem to concern with the genesis file.
  • This occured on the latest version of parity.
  • This issue is resolved using --no-warp

Therefore I thought there might be some problem with snapshots in kovan. But am not sure, so I thought it would be better to post it here.

@5chdn 5chdn modified the milestones: 1.11, 1.12 May 1, 2018
@zhousi666
Copy link

I have the same problem. I want to know how you handled it. Can you help me?

@AyushyaChitransh
Copy link
Author

@linzhoushi2017 as I said, I used --no-warp and it synced correctly without errors.

@Tbaut Tbaut added P9-somedaymaybe 🌞 Issue might be worth doing eventually. and removed Z7-duplicate 🖨 Issue is a duplicate. Closer should comment with a link to the duplicate. labels May 2, 2018
@rsinensis
Copy link

Using --no-warp doesn't work on me.

2018-05-23 15:09:10  Stage 5 block verification failed for #26 (7658…0c32)
Error: Block(InvalidReceiptsRoot(Mismatch { expected: 2297c2fcb5f7517a5b275a992f49fe42c92c0b5ee303f44ad5c0d7dcc036c608, found: 45bef3c8f45af0174311babea84ed659c7380a7249e2fe1ac5d7749f2918a383 }))

@Tbaut
Copy link
Contributor

Tbaut commented May 23, 2018

I could not reproduce the problem :(

@drewstaylor
Copy link

drewstaylor commented May 28, 2018 •
edited by Tbaut
Loading

I encountered this issue today and it seems to have set the head of blockchain snapshot way far back in time:

ubuntu@ip-172-31-80-54:~$ parity --chain=kovan --jsonrpc-hosts=all --jsonrpc-interface=all --jsonrpc-cors=all
2018-05-28 18:43:14 UTC Starting Parity/v1.10.4-unstable-39b9f1e-20180514/x86_64-linux-gnu/rustc1.26.0
2018-05-28 18:43:14 UTC Keys path /home/ubuntu/snap/parity/12080/.local/share/io.parity.ethereum/keys/Kovan
2018-05-28 18:43:14 UTC DB path /home/ubuntu/snap/parity/12080/.local/share/io.parity.ethereum/chains/kovan/db/9bf388941c25ea98
2018-05-28 18:43:14 UTC Path to dapps /home/ubuntu/snap/parity/12080/.local/share/io.parity.ethereum/dapps
2018-05-28 18:43:14 UTC State DB configuration: fast
2018-05-28 18:43:14 UTC Operating mode: active
2018-05-28 18:43:14 UTC Configured for Kovan using AuthorityRound engine
2018-05-28 18:43:15 UTC Removed existing file '/home/ubuntu/snap/parity/12080/.local/share/io.parity.ethereum/jsonrpc.ipc'.
2018-05-28 18:43:20 UTC Public node URL: enode://5c1719952a1a2ec9e57712cedf22e28473a38223aa8616fb1587d72f7898914385557909b7ef5b5378719c57d2b5b9847355cab2e0b7887fa4f48d84cfee3436@172.31.80.54:30303
2018-05-28 18:43:23 UTC Stage 5 block verification failed for #7485112 (cb69…f223)
Error: Block(InvalidGasUsed(Mismatch { expected: 63286, found: 23259 }))
2018-05-28 18:43:45 UTC    #133276    0/25 peers   3 MiB chain 3 MiB db 0 bytes queue 7 MiB sync  RPC:  0 conn,  0 req/s,   0 µs

@5chdn
Copy link
Contributor

5chdn commented Jun 13, 2018

Just a misbehaving client. Please upgrade to 1.10.6 or 1.11.3, remove your nodes.json and try to resync the chain.

@5chdn 5chdn closed this as completed Jun 13, 2018
@pabloruiz55
Copy link

Out of the sudden I started to get this today.

2018-08-22 11:20:23  Stage 5 block verification failed for #8455037 (0x4870…e8ea)
Error: Error(Block(InvalidGasUsed(Mismatch { expected: 0x3674a, found: 0x32cbc })), State { next_error: None, backtrace: None })
2018-08-22 11:20:49  Syncing #8455036 0x1adc…952d     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #8455021    2/25 peers   31 KiB chain 2 MiB db 0 bytes queue 12 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-08-22 11:21:19       #1042    0/25 peers   31 KiB chain 2 MiB db 0 bytes queue 12 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-08-22 11:21:49       #1042    0/25 peers   31 KiB chain 2 MiB db 0 bytes queue 12 KiB sync  RPC:  0 conn,  0 req/s,   0 µs

Updated to v1.11.8-stable, tried deleting nodes.json, tried using --no-warp, but to no avail. Any ideas?

@Tbaut Tbaut mentioned this issue Aug 23, 2018
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P9-somedaymaybe 🌞 Issue might be worth doing eventually.
Projects
None yet
Milestone
2.0 Ethereum
Development

No branches or pull requests
7 participants
@pabloruiz55 @drewstaylor @rsinensis @AyushyaChitransh @5chdn @zhousi666 @Tbaut