Author

Topic: Crashes routinely while syncing :-( (Read 952 times)

member
Activity: 149
Merit: 22
🔴🔵 FoxMixer.com 🔵🔴
April 25, 2017, 05:01:50 PM
#6
I also had a similar issue, for me it sporadically was crashing just after starting up with v14.1.
I had to wait for a minute or two before interacting with the UI and then it worked fine. Might have been some threading issue if the block check, the sync/communication worker and the user want to access data at the same time.
newbie
Activity: 16
Merit: 2
April 24, 2017, 02:00:58 PM
#5
Thanks, I fixed it by defragging, which worked for a bit, that'd be a boot time defrag, and then when it crashed again later I moved the Bitcoin directory, copied it and pasted it elsewhere and changed the settings so Bitcore used the newer version. So, disk problems then! If yours keeps crashing in the same place, it's probably worth assuming it's the hard drive and trying another one if you have it or moving the directory. I'm up to 2 years and 7 weeks now so it's motoring along ok, Thanks for your reply :-)
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
April 24, 2017, 01:24:24 PM
#4
It runs along happily for a while, then crashes, then crashes straight away when I try to restart it. I have to reindex after that. I believe it's version 13. I tried 14 but it didn't work well, can't remember why. I've seen threads saying that 14 will hammer your hardware and, well, it's an old machine. It's running on an old Dell which frankly I'm doubting is up to it. It's Windows 10 - the great unknown! There's plenty of available disk space. I've reindexed and restarted a few times and I have a suspicion that it's crashing at around the same period which suggests a disk problem. Next on my list is to note where it crashes and then try again with the bitcoin directory in a new location. At the moment it's got up to 2 years 48 weeks behind. Thanks for your response :-)

One of my machines appeared to crash at 2 years and 48 weeks as well and I have no idea why.
You could try downgrading from version 13 to 12.2 (the archives are avaliable on the official bitcoin website).

If that fails and you need an alternative you could try something like electrum.org (so you have control of the private keys) or I think there are some lighter versions of bitcoin core (and also pruning avaliable so a smaller amount of the blockchain is stored).
newbie
Activity: 16
Merit: 2
April 22, 2017, 12:21:38 AM
#3
It runs along happily for a while, then crashes, then crashes straight away when I try to restart it. I have to reindex after that. I believe it's version 13. I tried 14 but it didn't work well, can't remember why. I've seen threads saying that 14 will hammer your hardware and, well, it's an old machine. It's running on an old Dell which frankly I'm doubting is up to it. It's Windows 10 - the great unknown! There's plenty of available disk space. I've reindexed and restarted a few times and I have a suspicion that it's crashing at around the same period which suggests a disk problem. Next on my list is to note where it crashes and then try again with the bitcoin directory in a new location. At the moment it's got up to 2 years 48 weeks behind. Thanks for your response :-)
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
April 21, 2017, 07:01:55 PM
#2
What does it do exactly. Does it start up and instantly shut down or do you shut it down?

It could be a problem with this:
Code:
2017-04-21 07:13:10 Failed to connect best blockAddLocal([2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333,1)

Which looks like an external connection. Is there free disk space avaliable? If you reindex do you get the same problem (also is this the most recent version of core or a few versions early)?
newbie
Activity: 16
Merit: 2
April 21, 2017, 02:18:15 AM
#1
Keep getting this now :-) Drive problems, do we think? I've run checkdisk, all seems ok.

2017-04-21 07:12:17 Bitcoin version v0.13.1
2017-04-21 07:12:17 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-04-21 07:12:17 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-04-21 07:12:18 Default data directory C:\Users\Dell\AppData\Roaming\Bitcoin
2017-04-21 07:12:18 Using data directory C:\Users\Dell\AppData\Roaming\Bitcoin
2017-04-21 07:12:18 Using config file C:\Users\Dell\AppData\Roaming\Bitcoin\bitcoin.conf
2017-04-21 07:12:18 Using at most 125 connections (2048 file descriptors available)
2017-04-21 07:12:18 Using 2 threads for script verification
2017-04-21 07:12:18 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-04-21 07:12:18 Using wallet wallet.dat
2017-04-21 07:12:18 scheduler thread start
2017-04-21 07:12:18 init message: Verifying wallet...
2017-04-21 07:12:18 CDBEnv::Open: LogDir=C:\Users\Dell\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Dell\AppData\Roaming\Bitcoin\db.log
2017-04-21 07:12:18 Bound to [::]:8333
2017-04-21 07:12:18 Bound to 0.0.0.0:8333
2017-04-21 07:12:18 Cache configuration:
2017-04-21 07:12:18 * Using 2.0MiB for block index database
2017-04-21 07:12:18 * Using 8.0MiB for chain state database
2017-04-21 07:12:18 * Using 290.0MiB for in-memory UTXO set
2017-04-21 07:12:18 init message: Loading block index...
2017-04-21 07:12:18 Opening LevelDB in C:\Users\Dell\AppData\Roaming\Bitcoin\blocks\index
2017-04-21 07:12:19 Opened LevelDB successfully
2017-04-21 07:12:19 Using obfuscation key for C:\Users\Dell\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2017-04-21 07:12:19 Opening LevelDB in C:\Users\Dell\AppData\Roaming\Bitcoin\chainstate
2017-04-21 07:12:26 Opened LevelDB successfully
2017-04-21 07:12:26 Using obfuscation key for C:\Users\Dell\AppData\Roaming\Bitcoin\chainstate: 0a172bbd222feac1
2017-04-21 07:12:47 LoadBlockIndexDB: last block file = 188
2017-04-21 07:12:47 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=58, size=17163518, heights=326460...326895, time=2014-10-22...2014-10-25)
2017-04-21 07:12:47 Checking all blk files are present...
2017-04-21 07:12:52 LoadBlockIndexDB: transaction index disabled
2017-04-21 07:12:52 LoadBlockIndexDB: hashBestChain=000000000000000003962f6d925b37f6b9405badc04785c39b0d982c7ae48b07 height=326828 date=2014-10-24 21:06:58 progress=0.272434
2017-04-21 07:12:52 init message: Rewinding blocks...
2017-04-21 07:12:55 init message: Verifying blocks...
2017-04-21 07:12:55 Verifying last 6 blocks at level 3
2017-04-21 07:12:55 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-04-21 07:13:07 No coin database inconsistencies in last 7 blocks (4052 transactions)
2017-04-21 07:13:07  block index           48473ms
2017-04-21 07:13:07 init message: Loading wallet...
2017-04-21 07:13:07 nFileVersion = 140000
2017-04-21 07:13:07 Keys: 0 plaintext, 201 encrypted, 201 w/ metadata, 201 total
2017-04-21 07:13:07  wallet                  274ms
2017-04-21 07:13:07 mapBlockIndex.size() = 462821
2017-04-21 07:13:07 nBestHeight = 326828
2017-04-21 07:13:07 setKeyPool.size() = 99
2017-04-21 07:13:07 mapWallet.size() = 3
2017-04-21 07:13:07 mapAddressBook.size() = 2
2017-04-21 07:13:07 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=187, nPos=117248446)
2017-04-21 07:13:07 *** Failed to read block
2017-04-21 07:13:07 init message: Loading addresses...
2017-04-21 07:13:07 torcontrol thread start
2017-04-21 07:13:08 Loaded 67646 addresses from peers.dat  1093ms
2017-04-21 07:13:08 init message: Loading banlist...
2017-04-21 07:13:08 init message: Starting network threads...
2017-04-21 07:13:10 Failed to connect best blockAddLocal([2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333,1)
2017-04-21 07:13:11 Discover: smallformten - 2001:0:4137:9e76:3420:2fda:ae92:dc1e
2017-04-21 07:13:11 init message: Done loading
2017-04-21 07:13:11 dnsseed thread start
2017-04-21 07:13:11 net thread start
2017-04-21 07:13:11 addcon thread start
2017-04-21 07:13:11 opencon thread start
2017-04-21 07:13:11 msghand thread start
2017-04-21 07:13:11 tor: Thread interrupt
2017-04-21 07:13:11 dnsseed thread interrupt
2017-04-21 07:13:11 net thread interrupt
2017-04-21 07:13:11 addcon thread interrupt
2017-04-21 07:13:11 opencon thread interrupt
2017-04-21 07:13:11 scheduler thread interrupt
2017-04-21 07:13:11 msghand thread interrupt
2017-04-21 07:13:11 Shutdown: In progress...
2017-04-21 07:13:11 torcontrol thread exit
2017-04-21 07:13:11 StopNode()
2017-04-21 07:13:11 Shutdown: done
Jump to: