|
Title: electrs panic, what to do ? Post by: Rexall on July 08, 2024, 05:37:34 AM Hi All,
I am running bitcoin-25.1 and electrs 0.1.0 on an ubuntu-server linux box. Something has gotten corrupted, perhaps due to a power outage. I can look up blocks in mempool but not addresses. When I try to look up an address mempool returns: Error loading address data. (Connection to server lost, please retry) bitcoind seems to be ok: { "chain": "main", "blocks": 851208, "headers": 851208, "bestblockhash": "00000000000000000002ccc5f0d8854b61026a419c8930e6b92106158fc028f7", "difficulty": 79495195323031.48, ... Looking in /var/log/syslog I see: Jul 8 00:00:18 nodebox electrs[109893]: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { message: "Corruption: block checksum mismatch: stored = 2965610381, computed = 3759059513, type = 1 in /home/satoshi/electrs/bitcoin/232529.sst offset 73693426 size 2770" }', src/db.rs:279:44 Then it seems that electrs restarts itself and the same thing happens again. Over and over. What do I have to do to sort this? Is there a way to re-index everything? Thanks in advance for any tips. Rex Title: Re: electrs panic, what to do ? Post by: ABCbits on July 08, 2024, 09:08:26 AM I am running bitcoin-25.1 and electrs 0.1.0 on an ubuntu-server linux box. Looking in /var/log/syslog I see: Jul 8 00:00:18 nodebox electrs[109893]: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { message: "Corruption: block checksum mismatch: stored = 2965610381, computed = 3759059513, type = 1 in /home/satoshi/electrs/bitcoin/232529.sst offset 73693426 size 2770" }', src/db.rs:279:44 I know this is lazy answer, but electrs 0.1.0 released 6 years ago[1] while latest electrs version is 0.10.5. So it's probably faster to delete all electrs file/application and then install latest version of electrs. But looking at commit for version 0.1.0[2], it shows cargo run --release -- -vvv --timestamp --db-dir ./db can be used to make index. [1] https://github.com/romanz/electrs/releases/tag/v0.1.0 (https://github.com/romanz/electrs/releases/tag/v0.1.0) [2] https://github.com/romanz/electrs/tree/7a170c6e1153cabb4f3508f8f6a96ba9a0740faf (https://github.com/romanz/electrs/tree/7a170c6e1153cabb4f3508f8f6a96ba9a0740faf) Title: Re: electrs panic, what to do ? Post by: Rexall on July 08, 2024, 09:22:37 AM Thanks ABCbits,
I do see that command now on github. And if it only takes a couple of hours, might be the way to go. :) Title: Re: electrs panic, what to do ? Post by: DaveF on July 08, 2024, 10:23:38 AM I agree with @ABCbits your electrs (and core) are both out of date. We are talking about your money here why run software that is so far from current?
Also run smartctl (or similar) on the disk that is holding the data to make sure that it's not drive related. What hardware (and how old) are you running it on. Just because you can install and run it all on a 4th gen i3 does not mean you should..... -Dave Title: Re: electrs panic, what to do ? Post by: Rexall on July 10, 2024, 09:22:29 AM I agree with @ABCbits your electrs (and core) are both out of date. We are talking about your money here why run software that is so far from current? Also run smartctl (or similar) on the disk that is holding the data to make sure that it's not drive related. What hardware (and how old) are you running it on. Just because you can install and run it all on a 4th gen i3 does not mean you should..... -Dave Thanks Dave. Its a Dell Optiplex MicroPC, i5 processor, 8GB RAM, new 2TB SSD. Guessing it's not a hardware issue -- we have had power outages -- so I'm upgrading electrs and will upgrade bitcoind as soon as it's functional. Thanks for the tips. Rex |