Closed shsmith closed 6 years ago
That's weird. Is this reproducible on a different machine? Is this ElectrumX 1.2 as tagged (there are many commits since then)
This is happening with git HEAD tagged 1.2.1. I had similar issues back when 1.2 came out, which is why abc1.hsmiths.com is still running 1.1.x. I am attempting to do the rebuild in a clone of that environment.
I suspect maybe it is the bitcoin database causing this. I am reindexing to see if that makes a difference.
Is there a foundry for the ABC blockchain and electrumx DB somewhere? Building these from zero is a barrier to spinning up new nodes.
Ah yes JWU42 had that issue - the bitcoind DB was corrupt and he couldn't sync. He resync-ed bitcoind and all was fine.
I'm not sure if there's a way to determine bitcoind "lying"; the base assumption of ElectrumX is that the bitcoin node is reliable and friendly. Its data is largely assumed good.
I don't think this kind of chain-sync logic has changed for a long time in e-x. Most changes have been to networking or other layers on top that should not affect the DB.
Note your hash was all zeroes. IMO this is more likely a DB driver bug or an O/S bug than a bitcoind or e-x bug. But let us know how a resync of bitcoind helps with everything else the same.
I let electrumX sync while bitcoind was reindexing and it made it past height 234,946. Seems likely it was indeed bitcoind index corruption.
I am attempting to update a BitcoinCash node to the version 6 database format. The rebuild fails hard with this traceback:
At this point the output stops and CPU load is 0. After several minutes of waiting I pressed ^C and got this output:
If I start electrumx again it starts at height 202,490 but fails again with the same tracebacks.
I tried deleting the new db to completely start over but it gets stuck at the same place on the next try.
Things were working ok with the previous database version and ElectrumX 1.1.1