-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Potential Database Corruption during sync #2603
Comments
That's probably a rocksdb OOM issue, judging by the sigsegv. |
Could not reproduce on my local VM (ubuntu 14.04) |
Adding some more info to this based on the suggestion from @keorn This doesn't seem to have to do specifically with many days of runtime as even after restarting parity, or attempting to sync a new copy of the chain from the network, the same issue is encountered. So even a brand new machine, running the latest version of parity, will be unable to sync to either network. Even using the newer While this seems to be due to a heavy set of blocks to process (around 2,420,000), possibly related to the recent exploit, it's important to note that this even failed to freshly sync from the network on a VPS with 16GB of RAM and 8 CPUs (Digital Ocean $160 droplet option). As such, even for more than capable machines this is a DoS for new nodes attempting to enter the network. And hints that the issue may not exactly be tied to the intense computation required for the exploit blocks. Also worth noting is that the panic/crash is immediate. So if I start parity to sync a fresh chain, let it crash at the problem block hours later, and then start it again, it will crash within about a second. My output in particular differs a bit from the original commenter's so I've included it below:
I have a working copy of the blockchain here (courtesy of another user) if it can be of any use debugging: full parity copy This copy includes the problem blocks but parity doesn't need to process them so the remainder of blocks sync as normal. |
I am also affected by this issue as soon as i run the executable.
Is there a workaround for this issue? or ETA for a fix? THANKS. |
You can download my copy at the "full parity node" link and copy the DB to your Just two things to keep in mind:
|
This should be fixed in 1.3.9. Please let us know if you see it again. |
Hi. I was using Parity 1.3.9... Everything was going well but syncing too slow, until such time it encountered this issue and won't let me sync on this block #2451318. Everytime I will restart the Parity, it will always crashed... This is the first time I have encountered such issue from when I started using 1.3.0 all the way to 1.3.9. Please let me know what should I do... I am now behind syncing to the latest block because of slow syncing recently...
|
this is fixed in master #2832 and will be fixed in the 1.3.10 stable. please test when those are release and reopen if the issue reappears. |
@5chdn probably not. Was there a out of memory or out of disk error on prior run? |
@arkpar can't tell, I was guiding him how to access the node logs and this is the first time he looked at it. We now reset the db and it works. |
Enough disk space (20GB)
4GB RAM node
Running latest master via:
$ cargo run --release --no-default-features --bin parity -- --relay-set strict --force-sealing
The text was updated successfully, but these errors were encountered: