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
The node stuck at block #5899999 #8897
Labels
F3-annoyance 💩
The client behaves within expectations, however this “expected behaviour” itself is at issue.
M4-core ⛓
Core client code / Rust.
Milestone
Comments
1scrooge
changed the title
i'm stuck at block #5899999
The node stuck at block #5899999
Jun 14, 2018
did you try to restart parity? |
Tbaut
added
F3-annoyance 💩
The client behaves within expectations, however this “expected behaviour” itself is at issue.
M4-core ⛓
Core client code / Rust.
labels
Jun 14, 2018
Experiencing same issue with Ropsten, restart does not help:
|
@Tbaut sure. |
@PaterSantyago this is not related. Please see my comment #8845 (comment) @1scrooge please upgrade to the latest parity release. |
@Tbaut nope, I'm syncing with --no-warp option, as you wrote in your comment |
@PaterSantyago this is still not related (Ropsten vs ETC), please keep this issue on track and comment on the other issue. |
@Tbaut v1.11.3 beta helped. Thank you |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
F3-annoyance 💩
The client behaves within expectations, however this “expected behaviour” itself is at issue.
M4-core ⛓
Core client code / Rust.
I'm running:
docker parity:v1.9.3
Network: ethereum classic mainnet
Also I have tryed v1.10.6
The text was updated successfully, but these errors were encountered: