Parity refuses to import valid Ethereum mainnet block #11355
Comments
Same issue here on block 9186215. My other Parity nodes imported it correctly.
|
We now experienced the issue 6 times on multiple individual nodes and different blocks:
All nodes are running the latest stable parity version. |
@ppratscher @nfeignon Do you also have 2.6.7 nodes running? Did they import the block correctly? |
We've been seeing parity nodes falling out of sync on the 2.6.x beta branch and just dying over the past two weeks. |
With this specific error? |
noticing a number of our 2.5.11-stable nodes falling hundreds of blocks behind as well, this started happening today |
I'm only running 2.5.12 nodes. |
Unfortunately, because we are allocating so little hashrate to Eth at the moment we didn't notice until the logs had already been rotated out. When we upgraded Parity for Muir Glacier it had to rebuild the entire chain history though on all nodes that had died. We had four nodes die in the same way. |
@brianventuro All four "died" how? Stalled? Crashed? Or did they run into the |
@nysxah Do you mean 2.5.12? |
Last logs that I have from 2.6.6:
Nodes all just stalled with no error message. |
We are seeing the same issue (stalling with "UnverifiedTransaction" error messages) on 2.6.6 As mentioned above, restarting the node allows it to resume sync |
A bunch of Parity nodes I maintain began to randomly fall behind today, restarting Parity seems to have fixed things up. I am running the folllowing: |
@brianventuro @nysxah note that the Muir Glacier HF is due in two days (1/1) and that 2.6.6 and 2.5.11 are not compatible, so regardless of this issue please consider upgrading your nodes. |
@dvdplm of course, goes without saying we're going to upgrade. it's not uncommon for Parity to release a new version the day before a fork (speaking from experience), so we're keeping a close eye on things and will update/upgrade in-time. our service powers many web3 projects and dapps, so this is at the top of our priority. |
Our nodes on v2.6.7 are also randomly falling out of sync and needs restart. After restart refuses to sync
|
When we upgraded from 2.6.6 to 2.6.7 the chain db was completely rebuilt - unsure as to what causes that behavior - there was no error message or descriptive message explaining why either. It just started a fresh warp sync. |
@mewwts that seems to be a different issue than the one discussed here though: |
Our errors on 2.6.6 seem to be intermittent / inconsistent. We run 26 nodes on 2.6.6 and only 5 of them crashed with "UnverifiedTransaction" errors. We saw errors across --warp and --no-warp nodes, as well as on Windows + Linux distributions |
@dvdplm I'm sorry, we did see that in our logs, see this gist https://gist.github.com/mewwts/e013f6c2094905abbad80363bb2971ac |
We at Eidoo are experiencing the same error of @Hex-Capital with 2.5.12 |
also seen the same with a couple of my nodes (but not all) running the docker 2.6.7-beta image see https://gist.github.com/stephgosling/248b5687ff59f072dec320b488cb36d5 and https://gist.github.com/stephgosling/b75652a1e810677fe7929956e176ac54 A stop and start sorts them out. |
Instance from one of our nodes observed earlier today: https://gist.github.com/brianventuro/39eb9a823b1f87cf6cfdac91ae535b7e |
Rebooting fixed our mainnet and Kovan nodes, but not our xdai nodes. they're logging messages like
repeatedly and not publishing any messages to our infra listening to them. running 2.5.12. |
Same here at Verady - parity2.5.12 running for 8+ hours then: https://gist.github.com/kcanty/ea101b44df7f43b5dff0a8b135514b20 slightly different initial error - restart results in it starting to sync/import again right away. Obviously unsustainable in a production environment. Stage 1 block verification failed for 0xa423…36df: Error(Block(InvalidTransactionsRoot(Mismatch { expected: 0xe0c979c5e5d04ebfa5809d764fe5bbc963299b2297766bdf9c072187c7c2ba99, found: 0xfc2b40ec80a450924f21991b76ec79c113aaaffe3d193f68c21e0864b65053ec })), State { next_error: None, backtrace: InternalBacktrace { backtrace: None } }) |
here too , linux 2.5.11 stop sync (same bug of first post) , but upgrade to 2.5.13 is okay now |
Fixed by upgrading to 2.5.13/2.6.8. Thanks to everyone for reporting in! |
Adding additional info here, please let me know if this should be a separate issue and I will update. My node on the ETC network stopped syncing at some point last night (likely due to the aforementioned bug). Due to the now default This seems to have led to my previously fully validated chain being removed and created the need to resync completely. Log below, apologies that I don't have older more informative logs. Steps to reproduce (1-3 are best I can guess):
|
Today we started to see errors like the following in multiple of our Parity 2.5.12 nodes. After the error the client stops syncing and only resumes syncing after a restart. According to etherchain & etherscan the block in the error log is valid.
The text was updated successfully, but these errors were encountered: