-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorg causes orderly shutdown on btcd when addrindex=1 #340
Comments
First, we're you running an outdated version of the Second, @aakselrod are you able to succesfully retireve either of these txids:
with a call to |
@Roasbeef, I was running master from about 2-3 weeks ago. I haven't seen any issues since I pulled the most recent master yesterday, but I don't think we've seen any reorgs in the past day either. Even with the most up-to-date code, btcd would stop as soon as it started with the corrupted database, so I couldn't send a |
A reorg on the testnet yesterday seems to have triggered this issue:
Re-count of the order of events that triggered the shutdown above:
Restart attempt with
Result of trying to lookup the missing tx: ➜ testnet btcctl getrawtransaction fa6764111c4784d8ff56371f88046dbdca34be434d6e5136f759b15efbced153
-5: No information available about transaction Interestingly, a reorg on the 20th was handled without fail:
|
I believe this has been resolved with #354. @aakselrod is doing some testing to ensure that is the case. |
- Delete spent TX in setclearSpentData when unspent by block disconnect on reorg. - Test spent TX deletion when reorg causes block disconnect. - Test for correct NewestSha results after DropAfterBlockBySha. - Fix DropAfterBlockBySha to update info for NewestSha.
- Delete spent TX in setclearSpentData when unspent by block disconnect on reorg. - Test spent TX deletion when reorg causes block disconnect. - Test for correct NewestSha results after DropAfterBlockBySha. - Fix DropAfterBlockBySha to update info for NewestSha.
- Delete spent TX in setclearSpentData when unspent by block disconnect on reorg; return an error when there's more than one record to delete in the spent TX as that should never happen. - Test spent TX deletion when reorg causes block disconnect. - Test for correct NewestSha results after DropAfterBlockBySha. - Fix DropAfterBlockBySha to update info for NewestSha.
- Delete spent TX in setclearSpentData when unspent by block disconnect on reorg; return an error when there's more than one record to delete in the spent TX as that should never happen. - Test spent TX deletion when reorg causes block disconnect. - Test for correct NewestSha results after DropAfterBlockBySha. - Fix DropAfterBlockBySha to update info for NewestSha. - Updated copyright statements in modified files
- Delete spent TX in setclearSpentData when unspent by block disconnect on reorg; return an error when there's more than one record to delete in the spent TX as that should never happen. - Test spent TX deletion when reorg causes block disconnect. - Test for correct NewestSha results after DropAfterBlockBySha. - Fix DropAfterBlockBySha to update info for NewestSha. - Updated copyright statements in modified files
- Delete spent TX in setclearSpentData when unspent by block disconnect on reorg; return an error when there's more than one record to delete in the spent TX as that should never happen. - Test spent TX deletion when reorg causes block disconnect. - Test for correct NewestSha results after DropAfterBlockBySha. - Fix DropAfterBlockBySha to update info for NewestSha. - Updated copyright statements in modified files
btcd seems to shut itself down during or shortly after a reorg when addrindex=1. It seems to corrupt the DB as simply restarting btcd just makes it shut itself right back down on the spot. Sample logs (from a btcd running on testnet3):
and
Here's a log from a restart attempt:
The text was updated successfully, but these errors were encountered: