-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Error: Block(InvalidGasUsed(Mismatch { expected: 82410, found: 98892 })) #6503
Comments
What's the exact version of your client? |
Starting Parity/v1.8.0-unstable-03e039b-20170911/x86_64-macos/rustc1.20.0 |
In my case I have run into this problem on my private testnet that has been running with mostly "geth" clients for 2 months. I have tried the following parity versions:
The error:
The block in question:
|
@5chdn I'll open a new issue. Maybe it's a bug. |
I am getting same error in my private network of 5 authority nodes and 4 normal sync nodes. The error I receive is:
I tried folowing steps to avoid this error:
But still, it receives the above mentioned error. I don't know why it is not syncing. If I keep the engine_signer on, then it continues with its own chain. |
Can you check what Parity version was used to produce that block? Did you update the chainspec when switching between versions? I think it might be some of the byzantium features enabled by default (or misconfigured in chainspec file). |
Additional InfoOut of 5, One of the authority running v1.8.5 has gone out of sync. My chain-spec file is here. |
I followed these steps in attempt to solve the problem:
ResultThe sync stops at problematic block and stays there with an error message:
|
To avoid this error:
I copied data from |
I am still unable to find root cause of this error which keeps arising after about ten to twelve hours.
|
I was able to correct those errors after I included most of the EIPs mentioned in mainnet genesis. My new genesis has following parameters and it works without those errors.
|
That's good to know. I also want to implement a PoA blockchain for a project and was thinking of using parity. Please report back if you find more problems. :) |
I try to run Parity with Ropsten Testnet (via config, just that nothing else).
I download on an external volume to save diskspace (i dont have enough space to download directly).
I already tried this several times, but i couldn't manage to finish the download in one session (slow connection).
Everytime I restart via "cargo run --release" it starts downloading some snapshots, maybe 0-3 more and then it encounters some error like this:
Usually it trys to download the same snapshot for eternity and won't proceed. This time it threw this:
that's why I am posting it here 👍
The text was updated successfully, but these errors were encountered: