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
My parity is not sync #5837
Labels
Z1-question 🙋♀️
Issue is a question. Closer should answer.
Comments
Your database is corrupted. The easiest way is to resync. Just run
And you should be back to normal within a few minutes. By the way, you might want to upgrade to 1.6.8 soon. |
i usually do that but sometimes i do resync and it do it again... |
How did you install it? Usually the same procedure. If you are on linux, try
|
i downloaded the .deb installer and execute it. |
Just execute it again, yes. |
ok, thanks, i'm going to do it |
This was referenced Nov 20, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It stops and it doesn't want to start again and says this:
parity -l sync=trace
2017-06-14 11:19:00 main INFO parity::run Starting Parity/v1.6.6-beta-8c6e3f3-20170411/x86_64-linux-gnu/rustc1.16.0
2017-06-14 11:19:00 main INFO parity::run State DB configuration: fast
2017-06-14 11:19:00 main INFO parity::run Operating mode: passive
2017-06-14 11:19:00 main INFO ethcore::service Configured for Foundation using Ethash engine
2017-06-14 11:19:01 hyper-client INFO miner Updated conversion rate to Ξ1 = US$388.84 (306160930 wei/gas)
thread 'main' panicked at 'failed to update version: "Corruption: block checksum mismatch"', /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/result.rs:868
stack backtrace:
1: 0x559ddb78790c -
2: 0x559ddb78edfe -
3: 0x559ddb78ea04 -
4: 0x559ddb78f29b -
5: 0x559ddb78f134 -
6: 0x559ddb78f059 -
7: 0x559ddb78efe7 -
8: 0x559ddb7bbcdd -
9: 0x559ddb1c9268 -
10: 0x559ddb2fce58 -
11: 0x559ddb2c9ed8 -
12: 0x559ddb2f9b32 -
13: 0x559ddae5038b -
14: 0x559ddae6f828 -
15: 0x559ddae767aa -
16: 0x559ddae79475 -
17: 0x559ddb795ebb -
Abortado (`core' generado)
The text was updated successfully, but these errors were encountered: