-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New node unable to sync #18
Comments
I have seen that this Parity PR: introduced a bug that has been fixed 6 days ago: probably will disappear in the next release, let's wait and see. |
Happens quite frequent another evidence below (parity 2.3.9 stable): Imported #35794 0x665b…b53b (0 txs, 0.00 Mgas, 4 ms, 0.55 KiB) 2019-04-17 23:33:50 0/25 peers 6 MiB chain 25 MiB db 0 bytes queue 271 KiB sync RPC: 0 conn, 1 req/s, 27 µs |
Related to #10 |
I had the same problems with a global poa network with nodes in aws and azure. The network uses dynamic validators over a validator contract. Every node on the cloud worked without problems. My local parity node on mac runs very instable. After I install chronyd on my mac and synchronize the time not over the apple time server, everything works fine. The error messages did depend on the parity version I used. If I use the last stable, I did get “Bad block detected: TimestampOverflow with a blocktrace”. If I used v2.3.3 I did get “Bad block detected: TemporarilyInvalid(OutOfBounds”. With v2.4.5 I lost also every time that happened the peers. I hope this info’s are use full. |
We (@marcelorocha-e) are testing this possible fix: openethereum/parity-ethereum#10720 |
Solved in Parity v2.4.8 |
Starting parity clean with no db and get this after a while:
The text was updated successfully, but these errors were encountered: