Title: bitcoind failed when reindexing
Post by: cryptedlife on October 28, 2017, 06:05:44 PM
In bitcoin.conf I have Then I startered bitcoind -reindex -daemon Then at block 485691 my bitcoind was interrupted with ERROR: 2017-10-28 13:27:29 receive version message: /Satoshi:0.14.0/: version 70015, blocks=492084, us=x.x.x.x:44864, peer=10977
2017-10-28 13:27:29 receive version message: /Satoshi:0.9.99/: version 70002, blocks=-1, us=x.x.x.x:8333, peer=10978
2017-10-28 13:27:29 Misbehaving: 205.251.22.236:4139 peer=10971 (0 -> 1)
2017-10-28 13:27:29 ProcessMessages(ping, 8 bytes) FAILED peer=10971
2017-10-28 13:27:29 receive version message: /Satoshi:0.14.2/: version 70015, blocks=492084, us=x.x.x.x:60804, peer=10979
2017-10-28 13:27:29 receive version message: /Satoshi:0.14.99/: version 70015, blocks=492084, us=x.x.x.x:46830, peer=10980
2017-10-28 13:27:31 receive version message: /nodes.bitcoin-russia.ru:0.0.1f/: version 70015, blocks=492084, us=x.x.x.x:8333, peer=109
81
2017-10-28 13:27:33 Imported mempool transactions from disk: 0 successes, 0 failed, 10345 expired
2017-10-28 13:27:34 Leaving block file 1000: CBlockFileInfo(blocks=212, size=133795768, heights=485480...485691, time=2017-09-16...2017-09-17
)
2017-10-28 13:27:35 Pre-allocating up to position 0x1000000 in blk01001.dat
2017-10-28 13:27:44 *** System error: CAutoFile::write: write failed: iostream error
2017-10-28 13:27:45 Error: Error: A fatal internal error occurred, see debug.log for details
2017-10-28 13:27:45 ERROR: ProcessNewBlock: AcceptBlock FAILED
2017-10-28 13:27:54 *** System error: CAutoFile::write: write failed: iostream error
2017-10-28 13:27:51 tor: Thread interrupt
2017-10-28 13:27:54 Error: Error: A fatal internal error occurred, see debug.log for details
2017-10-28 13:27:54 ERROR: ProcessNewBlock: AcceptBlock FAILED
2017-10-28 13:27:54 opencon thread exit
2017-10-28 13:27:54 msghand thread exit
2017-10-28 13:27:54 torcontrol thread exit
2017-10-28 13:27:54 addcon thread exit
2017-10-28 13:27:54 net thread exit
2017-10-28 13:27:54 scheduler thread interrupt
2017-10-28 13:27:55 Shutdown: In progress...
2017-10-28 13:27:56 Dumped mempool: 1.1e-05s to copy, 0.123345s to dump
2017-10-28 13:30:30 Shutdown: done
Then I tried to start bitcoind again (without -reindex) And got ERROR again: ...
2017-10-28 17:38:48 Checking all blk files are present...
2017-10-28 17:38:48 LoadBlockIndexDB: transaction index enabled
2017-10-28 17:38:48 LoadBlockIndexDB: hashBestChain=00000000000000000019a37a36788e73a2eecaa1f1ad7bbc0ae89fa23c922bd6 height=485691 date=2017-09-17 05:49:53 progress=0.956959
2017-10-28 17:38:49 init message: Rewinding blocks...
2017-10-28 17:38:51 init message: Verifying blocks...
2017-10-28 17:38:51 Verifying last 6 blocks at level 3
2017-10-28 17:38:51 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-10-28 17:39:17 No coin database inconsistencies in last 7 blocks (4839 transactions)
2017-10-28 17:39:17 block index 66290ms
2017-10-28 17:39:17 init message: Loading wallet...
2017-10-28 17:39:17 nFileVersion = 140200
2017-10-28 17:39:17 Keys: 102 plaintext, 0 encrypted, 102 w/ metadata, 102 total
2017-10-28 17:39:17 wallet 689ms
2017-10-28 17:39:17 setKeyPool.size() = 100
2017-10-28 17:39:17 mapWallet.size() = 0
2017-10-28 17:39:17 mapAddressBook.size() = 1
2017-10-28 17:39:17 mapBlockIndex.size() = 489692
2017-10-28 17:39:17 nBestHeight = 485691
2017-10-28 17:39:17 torcontrol thread start
2017-10-28 17:39:17 AddLocal(x.x.x.x:8333,1)
2017-10-28 17:39:17 Discover: IPv4 enp0s25: x.x.x.x
2017-10-28 17:39:17 init message: Loading addresses...
2017-10-28 17:39:18 Imported mempool transactions from disk: 1 successes, 0 failed, 0 expired
2017-10-28 17:39:19 Loaded 62417 addresses from peers.dat 1211ms
2017-10-28 17:39:19 init message: Loading banlist...
2017-10-28 17:39:19 init message: Starting network threads...
2017-10-28 17:39:19 net thread start
2017-10-28 17:39:19 dnsseed thread start
2017-10-28 17:39:19 msghand thread start
2017-10-28 17:39:19 init message: Done loading
2017-10-28 17:39:19 addcon thread start
2017-10-28 17:39:19 opencon thread start
2017-10-28 17:39:19 receive version message: /bitcoin-seeder:0.01/: version 60000, blocks=350000, us=x.x.x.x:8333, peer=0
2017-10-28 17:39:30 Loading addresses from DNS seeds (could take a while)
2017-10-28 17:39:30 117 addresses found from DNS seeds
2017-10-28 17:39:30 dnsseed thread exit
2017-10-28 17:39:31 socket recv error Connection reset by peer (104)
2017-10-28 17:39:48 receive version message: /Satoshi:0.15.0/: version 70015, blocks=492099, us=x.x.x.x:42068, peer=2
2017-10-28 17:39:48 receive version message: /Satoshi:0.15.0/: version 70015, blocks=492099, us=x.x.x.x:39708, peer=3
2017-10-28 17:39:58 *** System error: CAutoFile::write: write failed: iostream error
2017-10-28 17:39:58 Error: Error: A fatal internal error occurred, see debug.log for details
2017-10-28 17:39:58 ERROR: ProcessNewBlock: AcceptBlock FAILED
2017-10-28 17:39:58 tor: Thread interrupt
2017-10-28 17:39:58 torcontrol thread exit
2017-10-28 17:39:58 addcon thread exit
2017-10-28 17:39:58 opencon thread exit
2017-10-28 17:39:58 net thread exit
2017-10-28 17:40:04 scheduler thread interrupt
2017-10-28 17:40:07 *** System error: CAutoFile::write: write failed: iostream error
2017-10-28 17:40:07 Shutdown: In progress...
2017-10-28 17:40:07 Error: Error: A fatal internal error occurred, see debug.log for details
2017-10-28 17:40:07 ERROR: ProcessNewBlock: AcceptBlock FAILED
2017-10-28 17:40:07 msghand thread exit
2017-10-28 17:40:09 Dumped mempool: 1.1e-05s to copy, 0.20966s to dump
2017-10-28 17:40:11 Shutdown: done
Guys, how to fix this?
Title: Re: bitcoind failed when reindexing
Post by: achow101 on October 28, 2017, 09:49:45 PM
It looks like bitcoind was unable to write to the file blk01001.dat in the blocks folder inside of your datadir. Make sure that you have enough disk space and that the user bitcoind is running under has permission to write to that file.
Title: Re: bitcoind failed when reindexing
Post by: Spendulus on October 31, 2017, 02:17:41 PM
The problem is quite obvious, your blockchain is corrupted, what you can do is to reindex or just delete the entire blockchain to again start.
Some virus scanners will delete various blocks in the blockchain, thus corrupting it.
Title: Re: bitcoind failed when reindexing
Post by: cryptedlife on November 02, 2017, 10:56:23 PM
The problem is quite obvious, your blockchain is corrupted, what you can do is to reindex or just delete the entire blockchain to again start.
Thank you. But that happened right when I was at 70% of reindexing the entire blockchain.
Title: Re: bitcoind failed when reindexing
Post by: cryptedlife on November 02, 2017, 10:57:40 PM
The problem is quite obvious, your blockchain is corrupted, what you can do is to reindex or just delete the entire blockchain to again start.
Some virus scanners will delete various blocks in the blockchain, thus corrupting it. I don't have virus scanners on that server. Any other ideas how to fix it? Do you think the only way is to start from scratch? :(
Title: Re: bitcoind failed when reindexing
Post by: SopihxiDesil on November 03, 2017, 01:58:22 PM
I think to problem is here "Dumped mempool" mean no connection to pool. I have to same problem with connection, but it dont show "Dumped mempool"
Title: Re: bitcoind failed when reindexing
Post by: boogersguy on November 04, 2017, 10:14:00 AM
Did you check your disk space?
Have you tried running without Tor?
Title: Re: bitcoind failed when reindexing
Post by: MrCrank on November 05, 2017, 06:54:45 AM
If this problem with disk space only..
I can offer to you use prune mode - you can save free space
Please read details here https://bitcointalk.org/index.php?topic=1599458.0
Title: Re: bitcoind failed when reindexing
Post by: BitcoinDiamond on November 07, 2017, 12:50:28 PM
Free up space! Bigger the better.
|