Transaction Stuck many days - Resolved, BUT...

[Lakshmana]

Hi all,


I can see there are more than enough topics on stuck transactions... Anyway, maybe I'm lucky.

Any help will be appreciated. Thank you in advance..


Bitcoin Client Software and Version Number:  Bitcoin Core 0.14.1
Operating System: Mac OS Sierra, 10.12.4, 64bit
System Hardware Specs: 2,66 GHz Intel Core 2 Duo, 8 GB RAM, 136 GB available on disc


Description of Problem:

My Bitcoin Core copy started to freeze/crash repeatedly, like within a minute after start. So I figured I try and send the coins from it to another address. I was quick enough to start the transaction before the wallet crashed again, the amount was subtracted, but the transaction never moved on.

It's been 5 days now. I know now that the fee was too low by now - I haven't been using bitcoin for some time, and back then there were no problems like this.


I tried to follow the "How to make a Full RBF transaction" guide from "All about "stuck" transactions..." with no particularly good result. I placed a plain text file with the -zapwallettxes command into the "Bitcoin Core Wallet Data" folder, then run the wallet once, then removed. After this the question mark next to the transaction in the wallet disappeared, but that's about all that changed.

The transaction is not to be found via blockchain.info. It says there is no such transaction.

I tried to pm Quickseller and macbook-air as recommended, but without success.



Any Related Addresses: receiving address: 18f9GwoHfHM5iwNZncATmErhtK56WuesPD

Any Related Transaction IDs: ac59a899562540886e143b4478bdd0d3feb4fd4c0a6b80b4572ea149243b0f68

Screenshot of the problem:

http://imgur.com/a/KZvIm

Log Files from the Bitcoin Client: Don't know how to add a file

[1715099227]

1715099227

[1715099227]

1715099227

[1715099227]

1715099227

[1715099227]

1715099227

[1715099227]

1715099227

[onnz423]

I could not found a tx with id: ac59a899562540886e143b4478bdd0d3feb4fd4c0a6b80b4572ea149243b0f68
If you check the Chain.so you will see that no one has sent btc to that adress according to blockchain.
If you are selling goods, please do not send them before the transaction has atleast one confirmation since i cannot fint it from block explorers at all.
I tried to accelerate with ViaBTC tool but it said "Transaction does not exist" so wait for 1 confirmation before sending the goods.
I hope this helps you

Edit: it is probably dropped by the nodes so you need to resend.

[achow101]

Your transaction either has been dropped or never hit the network at all due to crashes.

Can you please post the debug.log file? Just copy and paste the contents of the log file into a post here. Get as much from the bottom as you can.

[Lakshmana]

Thanks onnz423 and achow101!


- I'm not selling goods. This transaction was me sending money to me. (Bitcoin Core to Coinbase).

- Ad resend: The wallet now shows almost no balance (after the broken transaction), but I still have my wallet.dat file backed up from the time BEFORE the trasaction. I tried to run BTC Core with the backed up wallet and it shows the original balance before the broken transaction (Last transaction shown is 9 weeks ago). But the wallet still crashed after like a minute or so.

- I'm posting the debug.log bellow. It contains perhaps also that one session with the backed up wallet.dat file.

- I also was able to copy the raw transaction, if that's helpful


Appreciate your help guys.

[Lakshmana]

Your transaction either has been dropped or never hit the network at all due to crashes.

Can you please post the debug.log file? Just copy and paste the contents of the log file into a post here. Get as much from the bottom as you can.

Ad "has been dropped vs. never hit the network" -  I started checking the transaction ID pretty early after initiating. I used blockchain.info for that and also there I got a negative result right from the beginning (transaction nonexistent).

[Lakshmana]

Here's the debug.log:

https://expirebox.com/download/98a409995aa1275efb263c57e11aa0e9.html

[achow101]

It looks like you have a corrupted block. Go to the blocks folder inside the Bitcoin Core datadir. Delete the highest numbered blk*.dat file and the highest numbered rev*.dat file. Then start Bitcoin Core. It should ask you to reindex the database. Click Yes and let it do that. It will look like it is redownloading the blockchain, but it is just rebuilding its databases.

[Lakshmana]

It looks like you have a corrupted block. Go to the blocks folder inside the Bitcoin Core datadir. Delete the highest numbered blk*.dat file and the highest numbered rev*.dat file. Then start Bitcoin Core. It should ask you to reindex the database. Click Yes and let it do that. It will look like it is redownloading the blockchain, but it is just rebuilding its databases.

Hi achow101,


I did as you suggested and removed blk00789.dat  and rev00789.dat. These were the highest numbered files. After that Bitcoin Core started up normally and it didn't ask anything. Then it crashed as previously.






2017-05-10 10:03:43 Bitcoin version v0.14.1
2017-05-10 10:03:43 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-05-10 10:03:44 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-05-10 10:03:45 Default data directory /Users/Roman/Library/Application Support/Bitcoin
2017-05-10 10:03:45 Using data directory /Volumes/Data/Bitcoin Core Wallet Data
2017-05-10 10:03:45 Using config file /Volumes/Data/Bitcoin Core Wallet Data/bitcoin.conf
2017-05-10 10:03:45 Using at most 125 automatic connections (2560 file descriptors available)
2017-05-10 10:03:45 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-05-10 10:03:45 Using 2 threads for script verification
2017-05-10 10:03:45 scheduler thread start
2017-05-10 10:03:45 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-05-10 10:03:45 Using wallet wallet.dat
2017-05-10 10:03:45 init message: Verifying wallet...
2017-05-10 10:03:45 CDBEnv::Open: LogDir=/Volumes/Data/Bitcoin Core Wallet Data/database ErrorFile=/Volumes/Data/Bitcoin Core Wallet Data/db.log
2017-05-10 10:03:45 Bound to [::]:8333
2017-05-10 10:03:45 Bound to 0.0.0.0:8333
2017-05-10 10:03:45 Cache configuration:
2017-05-10 10:03:45 * Using 2.0MiB for block index database
2017-05-10 10:03:45 * Using 8.0MiB for chain state database
2017-05-10 10:03:45 * Using 290.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-05-10 10:03:45 init message: Loading block index...
2017-05-10 10:03:45 Opening LevelDB in /Volumes/Data/Bitcoin Core Wallet Data/blocks/index
2017-05-10 10:03:45 Opened LevelDB successfully
2017-05-10 10:03:45 Using obfuscation key for /Volumes/Data/Bitcoin Core Wallet Data/blocks/index: 0000000000000000
2017-05-10 10:03:45 Opening LevelDB in /Volumes/Data/Bitcoin Core Wallet Data/chainstate
2017-05-10 10:03:45 Opened LevelDB successfully
2017-05-10 10:03:46 Using obfuscation key for /Volumes/Data/Bitcoin Core Wallet Data/chainstate: 0000000000000000
2017-05-10 10:03:51 LoadBlockIndexDB: last block file = 788
2017-05-10 10:03:51 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=67, size=65581676, heights=455012...455357, time=2017-02-27...2017-03-02)
2017-05-10 10:03:51 Checking all blk files are present...
2017-05-10 10:03:51 LoadBlockIndexDB: transaction index disabled
2017-05-10 10:03:51 LoadBlockIndexDB: hashBestChain=000000000000000001f0d2bb3f05a1ed5ea55bce5a9c83c20f4bc45cbb090072 height=455091 date=2017-02-28 07:36:52 progress=0.910686
2017-05-10 10:03:51 init message: Rewinding blocks...
2017-05-10 10:03:54 init message: Verifying blocks...
2017-05-10 10:03:54 Verifying last 6 blocks at level 3
2017-05-10 10:03:54 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-05-10 10:06:19 No coin database inconsistencies in last 7 blocks (13448 transactions)
2017-05-10 10:06:19  block index          153812ms
2017-05-10 10:06:19 init message: Loading wallet...
2017-05-10 10:06:19 nFileVersion = 140100
2017-05-10 10:06:19 Keys: 103 plaintext, 0 encrypted, 103 w/ metadata, 103 total
2017-05-10 10:06:19  wallet                  255ms
2017-05-10 10:06:19 setKeyPool.size() = 101
2017-05-10 10:06:19 mapWallet.size() = 2
2017-05-10 10:06:19 mapAddressBook.size() = 2
2017-05-10 10:06:19 mapBlockIndex.size() = 465136
2017-05-10 10:06:19 nBestHeight = 455091
2017-05-10 10:06:19 torcontrol thread start
2017-05-10 10:06:19 init message: Loading addresses...
2017-05-10 10:06:19 Loaded 62464 addresses from peers.dat  353ms
2017-05-10 10:06:19 init message: Loading banlist...
2017-05-10 10:06:19 init message: Starting network threads...
2017-05-10 10:06:19 net thread start
2017-05-10 10:06:19 dnsseed thread start
2017-05-10 10:06:19 addcon thread start
2017-05-10 10:06:19 opencon thread start
2017-05-10 10:06:19 msghand thread start
2017-05-10 10:06:19 init message: Done loading
2017-05-10 10:06:30 Loading addresses from DNS seeds (could take a while)
2017-05-10 10:06:33 119 addresses found from DNS seeds
2017-05-10 10:06:33 dnsseed thread exit
2017-05-10 10:06:58 UpdateTip: new best=0000000000000000013f3f59c7051907d13320547c6ff432ff1cde46412cba9e height=455092 version=0x20000000 log2_work=86.05065 tx=200446168 date='2017-02-28 07:38:32' progress=0.910685 cache=15.2MiB(6669tx)
2017-05-10 10:06:58 AddToWallet ac59a899562540886e143b4478bdd0d3feb4fd4c0a6b80b4572ea149243b0f68 
2017-05-10 10:06:58 GUI: Platform customization: "macosx"
2017-05-10 10:06:59 connect() to [2606:6000:6118:8b00:441c:bb95:bc07:4c7b]:8333 failed: No route to host (65)
2017-05-10 10:06:59 ProcessMessages(version, 102 bytes) FAILED peer=0
2017-05-10 10:06:59 GUI: PaymentServer::LoadRootCAs: Loaded  168  root certificates
2017-05-10 10:07:28 UpdateTip: new best=00000000000000000093f4196e9e5a0b4797402f6529c473ebe5108aa1a5c822 height=455093 version=0x20000000 log2_work=86.050684 tx=200448198 date='2017-02-28 07:42:46' progress=0.910689 cache=23.7MiB(12090tx)
2017-05-10 10:07:40 connect() to [2a02:7aa0:43:1::182]:8333 failed: No route to host (65)
2017-05-10 10:07:40 connect() to [2a02:2149:8715:6900:b5e2:4b5d:7358:6dc0]:8333 failed: No route to host (65)
2017-05-10 10:08:10 UpdateTip: new best=00000000000000000071ea191b88ad96e77d4d221ae7bb3714c11d4c058b879f height=455094 version=0x20000000 log2_work=86.050718 tx=200449637 date='2017-02-28 07:44:11' progress=0.910690 cache=31.1MiB(17526tx)
2017-05-10 10:08:10 version handshake timeout from 1
2017-05-10 10:08:29 UpdateTip: new best=0000000000000000020f40bad7803134b6de285c9cf13de8c6b968e93a85425b height=455095 version=0x20000000 log2_work=86.050752 tx=200451852 date='2017-02-28 07:50:50' progress=0.910696 cache=33.6MiB(22103tx)
2017-05-10 10:08:30 connect() to [2a02:c7d:193f:c600:18f3:d52:207e:1e5a]:8333 failed: No route to host (65)
2017-05-10 10:08:31 connect() to [2001::9d38:6ab8:38ab:31dd:b6df:f83c]:8333 failed: No route to host (65)
2017-05-10 10:08:32 connect() to 178.162.211.175:8333 failed after select(): Connection refused (61)
2017-05-10 10:09:24 UpdateTip: new best=0000000000000000018a6ff6c758e9ae18f0a0e77d0e4adb72c1157e4573db0a height=455096 version=0x20000000 log2_work=86.050786 tx=200452808 date='2017-02-28 07:53:40' progress=0.910698 cache=35.6MiB(28010tx)
2017-05-10 10:09:24 receive version message: /Satoshi:0.13.2/: version 70015, blocks=465733, us=94.230.146.253:56454, peer=3
2017-05-10 10:10:00 UpdateTip: new best=0000000000000000012bff77b984f0c27b808c3aa153d0e514ac3bd75d938684 height=455097 version=0x20000000 log2_work=86.05082 tx=200454722 date='2017-02-28 08:00:19' progress=0.910704 cache=38.4MiB(33119tx)
2017-05-10 10:10:00 version handshake timeout from 4
2017-05-10 10:10:26 version handshake timeout from 5
2017-05-10 10:10:32 UpdateTip: new best=0000000000000000025b2c82013f3678821f0604d61c032ac97df6a62a11bdad height=455098 version=0x20000000 log2_work=86.050855 tx=200456869 date='2017-02-28 08:04:18' progress=0.910707 cache=41.0MiB(38556tx)
2017-05-10 10:10:46 UpdateTip: new best=0000000000000000005d33ddfa1d04726e5cc2bf2dbda504061408af840cfe96 height=455099 version=0x20000000 log2_work=86.050889 tx=200459103 date='2017-02-28 08:14:51' progress=0.910716 cache=43.9MiB(42453tx)
2017-05-10 10:10:46 receive version message: /Satoshi:0.13.2/: version 70015, blocks=465733, us=94.230.146.253:56462, peer=5
2017-05-10 10:10:46 receive version message: /Satoshi:0.13.1/: version 70014, blocks=465734, us=94.230.146.253:56467, peer=6
2017-05-10 10:10:46 connect() to 69.30.233.34:8333 failed after select(): Connection refused (61)
2017-05-10 10:11:07 UpdateTip: new best=000000000000000001419a77f67ff640977fd15680d3774fff5713842ddea95c height=455100 version=0x20000002 log2_work=86.050923 tx=200461393 date='2017-02-28 08:19:21' progress=0.910721 cache=45.2MiB(46617tx)
2017-05-10 10:11:14 connect() to [2001::5ef5:79fb:109b:1422:cdce:7936]:8333 failed: No route to host (65)
2017-05-10 10:11:19 UpdateTip: new best=0000000000000000008b95318a69d8ca0e8b6d2cfc83dfc37fdaa3612333a541 height=455101 version=0x20000002 log2_work=86.050957 tx=200463859 date='2017-02-28 08:32:35' progress=0.910732 cache=47.0MiB(50076tx)
2017-05-10 10:11:20 connect() to [2001::5ef5:79fd:3c17:10b2:2aae:2082]:8333 failed: No route to host (65)
2017-05-10 10:11:33 version handshake timeout from 7
2017-05-10 10:11:53 UpdateTip: new best=00000000000000000082193eae5c9283e75293c26b36079825a9b3d3f23ff987 height=455102 version=0x20000000 log2_work=86.050991 tx=200466118 date='2017-02-28 08:33:48' progress=0.910733 cache=52.7MiB(55908tx)
2017-05-10 10:11:53 receive version message: /Satoshi:0.13.1/: version 70014, blocks=465734, us=94.230.146.253:56468, peer=7
2017-05-10 10:11:53 connect() to [2001::5ef5:79fd:411:94ea:a2db:5643]:8333 failed: No route to host (65)
2017-05-10 10:12:46 UpdateTip: new best=000000000000000001c8e4f31305b4ed6809c3c3c040a49c0ca0ac3f6d94c100 height=455103 version=0x20000000 log2_work=86.051025 tx=200467084 date='2017-02-28 08:37:00' progress=0.910736 cache=55.9MiB(61028tx)
2017-05-10 10:12:46 version handshake timeout from 8
2017-05-10 10:12:46 version handshake timeout from 9
2017-05-10 10:12:51 UpdateTip: new best=000000000000000001bc179e64a1a099c76adf9fca480d8fd9b81a2ef32b5056 height=455104 version=0x20000000 log2_work=86.051059 tx=200467969 date='2017-02-28 08:41:46' progress=0.910740 cache=56.3MiB(62266tx)
2017-05-10 10:12:51 receive version message: /Satoshi:0.13.2/: version 70015, blocks=465734, us=94.230.146.253:56493, peer=8
2017-05-10 10:12:51 receive version message: /Satoshi:0.14.1/: version 70015, blocks=465735, us=[::]:0, peer=10
2017-05-10 10:13:25 UpdateTip: new best=000000000000000001e07bc999889e9493a80413da8e332bb0b2f424c34af6ce height=455105 version=0x20000000 log2_work=86.051093 tx=200469848 date='2017-02-28 08:47:19' progress=0.910744 cache=58.7MiB(66855tx)
2017-05-10 10:13:25 version handshake timeout from 10
2017-05-10 10:13:25 connect() to [2601:200:8101:af50:e4b9:675d:8fad:a72f]:8333 failed: No route to host (65)
2017-05-10 10:13:26 connect() to [2001::9d38:90d7:2402:1d3b:b325:f174]:8333 failed: No route to host (65)
2017-05-10 10:13:26 connect() to 37.187.109.146:8333 failed after select(): Connection refused (61)
2017-05-10 10:13:37 UpdateTip: new best=0000000000000000020724e60302794280133cb9c45f2dd8c95bde796b75af92 height=455106 version=0x20000002 log2_work=86.051127 tx=200472194 date='2017-02-28 08:58:34' progress=0.910754 cache=60.0MiB(70035tx)
2017-05-10 10:13:38 connect() to [2001::4137:9e76:3cef:b053:a185:4604]:8333 failed: No route to host (65)
2017-05-10 10:13:45 LevelDB read failure: Corruption: block checksum mismatch
2017-05-10 10:13:45 Corruption: block checksum mismatch
2017-05-10 10:13:48 Error reading from database: Database corrupted

[achow101]

Hi achow101,


I did as you suggested and removed blk00789.dat  and rev00789.dat. These were the highest numbered files. After that Bitcoin Core started up normally and it didn't ask anything. Then it crashed as previously.

Interesting. You need to get it to reindex the databases. Go to the Bitcoin Core datadir and find the file named bitcoin.conf or make it if it doesn't exist. Then add the following line to it:

Code:

reindex=1

Then start Bitcoin Core. It will be reindexing the databases. Once it is done, go back to that file and remove that line so it doesn't reindex every time you start the program.

[Lakshmana]

Hi achow101,


I did as you suggested and removed blk00789.dat  and rev00789.dat. These were the highest numbered files. After that Bitcoin Core started up normally and it didn't ask anything. Then it crashed as previously.

Interesting. You need to get it to reindex the databases. Go to the Bitcoin Core datadir and find the file named bitcoin.conf or make it if it doesn't exist. Then add the following line to it:

Code:

reindex=1

Then start Bitcoin Core. It will be reindexing the databases. Once it is done, go back to that file and remove that line so it doesn't reindex every time you start the program.

Ok, after initiating the reindexing process, Bitcoin Core took some reasonable amount of time to reindex the database, but once it was done with that, it started from scratch again, this time saying "Synchronizing with network". This went on for two nights and a day, after which I saw that it is probably in some kind of loop. Finally it gave me the "error reading database/shutting down" message. From then on it behaves the same way as it did before - crashing every minute or so.

Will be glad for any ideas...


Logfile: https://expirebox.com/download/e5a3b3588aeb41174f72ee9c4b43f959.html

[achow101]

Ok, after initiating the reindexing process, Bitcoin Core took some reasonable amount of time to reindex the database, but once it was done with that, it started from scratch again, this time saying "Synchronizing with network". This went on for two nights and a day, after which I saw that it is probably in some kind of loop. Finally it gave me the "error reading database/shutting down" message. From then on it behaves the same way as it did before - crashing every minute or so.

Will be glad for any ideas...


Logfile: https://expirebox.com/download/e5a3b3588aeb41174f72ee9c4b43f959.html

That's interesting. It looks like some blocks are corrupted and that is what is causing the crash. I suggest that you redownload the blockchain entirely so it actually starts from scratch. Just delete the entire blocks folder in the datadir and it will redownload and resync the entire blockchain.

If the error still comes up after you do this, I think it is likely that you have a hardware error. If the error does come up again, run hardware diagnostics, especially for the hard drive and for the RAM and see if that comes up with any errors.

[Lakshmana]

Ok, after initiating the reindexing process, Bitcoin Core took some reasonable amount of time to reindex the database, but once it was done with that, it started from scratch again, this time saying "Synchronizing with network". This went on for two nights and a day, after which I saw that it is probably in some kind of loop. Finally it gave me the "error reading database/shutting down" message. From then on it behaves the same way as it did before - crashing every minute or so.

Will be glad for any ideas...


Logfile: https://expirebox.com/download/e5a3b3588aeb41174f72ee9c4b43f959.html

That's interesting. It looks like some blocks are corrupted and that is what is causing the crash. I suggest that you redownload the blockchain entirely so it actually starts from scratch. Just delete the entire blocks folder in the datadir and it will redownload and resync the entire blockchain.

If the error still comes up after you do this, I think it is likely that you have a hardware error. If the error does come up again, run hardware diagnostics, especially for the hard drive and for the RAM and see if that comes up with any errors.

Ok, see you in a few weeks...

(As for the hardware, I bought a new hdd lately, specifically to avoid this kind of problems, and I'm monitoring it. The monitoring sfw says the hdd is 100% without any issues.)

[Lakshmana]

So, deleting the blockchain folder from the Bitcoin Core datadir did not work, as Bitcoin Core was unable to start when I removed it.

However, in the end I figured out a solution. I learned how to extract the private key from the backup copy of Bitcoin Core from this nice tutorial:

http://www.igotbitcoin.com/how-to-import-bitcoin-core-wallet-dat-file-into-multibit/


After that I restored my wallet successfully into a blockchain.info wallet, because that's what BitcoinWiki recommended doing. So I actually was in possession of my bitcoins again after some two weeks of struggle for like 20 - 30 minutes, only to get tricked by the blockchain.info wallet into sending the coins with a low fee again. Really what the blockchain.info web wallet does is it takes the worst possible fee and then recommends it as being the optimal amount. Well, is there any limit on how stupid this can get..?


So now stuck again...



ID: 4ab296394e445150f677b321387a273eeaf6855c33af5e810f78e70cd5a9c10c