This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Losing peers and falling out of sync #10626
Comments
jam10o-new
added
F2-bug 🐞
The client fails to follow expected behavior.
M4-core ⛓
Core client code / Rust.
labels
May 3, 2019
Having this issue on 2.4.5 running
These nodes are running on 4 vCPUs, 16GB ram, ubuntu 18.04 on Digital Ocean. |
#10371 that is a known issue with an as-of-yet unidentified cause |
The same problem
Start up log 2019-06-05 11:02:35 Starting Parity-Ethereum/v2.5.1-beta-adabd81-20190514/x86_64-linux-gnu/rustc1.35.0
2019-06-05 11:02:35 Keys path /data/parity/keys/ethereum
2019-06-05 11:02:35 DB path /data/parity/chains/ethereum/db/906a34e69aec8c0d
2019-06-05 11:02:35 State DB configuration: archive +Trace
2019-06-05 11:02:35 Operating mode: active
2019-06-05 11:02:36 Configured for Ethereum using Ethash engine
2019-06-05 11:02:38 Listening for new connections on 127.0.0.1:8546. Log with '-l sync=debug' 2019-06-05 10:52:01 IO Worker #0 DEBUG sync 58 -> Invalid packet 0
2019-06-05 10:52:49 IO Worker #0 DEBUG sync Wasn't able to finish transaction propagation within a deadline.
....
2019-06-05 10:52:49 IO Worker #1 DEBUG sync Unexpected packet 2 from unregistered peer: 286:Geth/v5.5.2-be43774/linux/go1.9.7
2019-06-05 10:53:45 IO Worker #1 DEBUG sync Wasn't able to finish transaction propagation within a deadline. Lost peers happened for several times and before lost peers, the IO Worker takes many time to do transaction propagation until deadline |
I solved my problem:
|
Closing issue due to its stale state. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Having issues losing peers since yesterday morning (approx 08:00 - 09:00 UTC). Parity starts up fine, syncs to the latest block, then proceeds to drop peers and fall out of sync regularily.
Likely related?: Sometimes, syncing will stop completely with 0 blocks
Qed
. During these pauses, we seem to accumulate peers normally but syncing remains "stuck" - I have not caught this since enabling trace logging.During both cases, restart parity then everything resumes correctly for a short time.
Full archive + tracing started with:
The text was updated successfully, but these errors were encountered: