Bitcoin Forum
June 16, 2024, 03:36:53 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: BitCoin Core 0.14.2 Error On OpenSuse  (Read 432 times)
WeeHughie (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
September 12, 2017, 06:30:45 PM
 #1

I have not opened my Bitcoin Wallet for some time - I had bitcoin-qt version

bitcoin-0.8.6

That would no longer run on my system, but I did not upgrade until I tried today, and downloaded bitcoin-0.14.2-x86_64-linux-gnu.tar.gz

When I run
./bitcoin-qt

The wallet opens, verifies 100% blocks, does a few other things and then I get an error which says to check the debug.log.

This is what is in the debug.log - not sure what to try next:

2017-09-12 18:02:15 Bitcoin version v0.14.2
2017-09-12 18:02:15 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-09-12 18:02:16 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-09-12 18:02:16 Default data directory /home/xxx/.bitcoin
2017-09-12 18:02:16 Using data directory /home/xxx/.bitcoin
2017-09-12 18:02:16 Using config file /home/xxx/.bitcoin/bitcoin.conf
2017-09-12 18:02:16 Using at most 125 automatic connections (1024 file descriptors available)
2017-09-12 18:02:16 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-09-12 18:02:16 Using 2 threads for script verification
2017-09-12 18:02:16 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-09-12 18:02:16 Using wallet wallet.dat
2017-09-12 18:02:16 init message: Verifying wallet...
2017-09-12 18:02:16 CDBEnv::Open: LogDir=/home/xxx/.bitcoin/database ErrorFile=/home/xxx/.bitcoin/db.log
2017-09-12 18:02:16 scheduler thread start
2017-09-12 18:02:16 Bound to [::]:8333
2017-09-12 18:02:16 Bound to 0.0.0.0:8333
2017-09-12 18:02:16 Cache configuration:
2017-09-12 18:02:16 * Using 2.0MiB for block index database
2017-09-12 18:02:16 * Using 8.0MiB for chain state database
2017-09-12 18:02:16 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-09-12 18:02:16 init message: Loading block index...
2017-09-12 18:02:16 Opening LevelDB in /home/xxx/.bitcoin/blocks/index
2017-09-12 18:02:17 Opened LevelDB successfully
2017-09-12 18:02:17 Using obfuscation key for /home/xxx/.bitcoin/blocks/index: 0000000000000000
2017-09-12 18:02:17 Opening LevelDB in /home/xxx/.bitcoin/chainstate
2017-09-12 18:02:17 Opened LevelDB successfully
2017-09-12 18:02:17 Using obfuscation key for /home/xxx/.bitcoin/chainstate: 0000000000000000
2017-09-12 18:02:21 LoadBlockIndexDB: last block file = 594
2017-09-12 18:02:21 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=115, size=90368443, heights=424274...424388, time=2016-08-08...2016-08-09)
2017-09-12 18:02:21 Checking all blk files are present...
2017-09-12 18:02:21 LoadBlockIndexDB: transaction index disabled
2017-09-12 18:02:21 LoadBlockIndexDB: hashBestChain=0000000000000000039a8b76137b58f7e289eece0d8318008cafb31e02241c5f height=424387 date=2016-08-09 08:22:43 progress=0.582266
2017-09-12 18:02:21 init message: Rewinding blocks...
2017-09-12 18:02:23 init message: Verifying blocks...
2017-09-12 18:02:23 Verifying last 6 blocks at level 3
2017-09-12 18:02:23 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-09-12 18:04:27 No coin database inconsistencies in last 7 blocks (12504 transactions)
2017-09-12 18:04:27  block index          130561ms
2017-09-12 18:04:28 init message: Loading wallet...
2017-09-12 18:04:28 nFileVersion = 140200
2017-09-12 18:04:28 Keys: 0 plaintext, 205 encrypted, 0 w/ metadata, 205 total
2017-09-12 18:04:28  wallet                  627ms
2017-09-12 18:04:28 setKeyPool.size() = 101
2017-09-12 18:04:28 mapWallet.size() = 10
2017-09-12 18:04:28 mapAddressBook.size() = 4
2017-09-12 18:04:28 mapBlockIndex.size() = 424840
2017-09-12 18:04:28 nBestHeight = 424387
2017-09-12 18:04:28 AddLocal(74.220.163.69:8333,1)
2017-09-12 18:04:28 torcontrol thread start
2017-09-12 18:04:28 Discover: IPv4 eth0: 74.220.163.69
2017-09-12 18:04:28 init message: Loading addresses...
2017-09-12 18:04:28 upnp thread start
2017-09-12 18:04:29 Loaded 194 addresses from peers.dat  101ms
2017-09-12 18:04:29 init message: Loading banlist...
2017-09-12 18:04:29 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=594, nPos=89380745)
2017-09-12 18:04:29 *** Failed to read block
2017-09-12 18:04:29 init message: Starting network threads...
2017-09-12 18:04:29 init message: Done loading
2017-09-12 18:04:29 dnsseed thread start
2017-09-12 18:04:29 opencon thread start
2017-09-12 18:04:29 msghand thread start
2017-09-12 18:04:29 addcon thread start
2017-09-12 18:04:29 net thread start
2017-09-12 18:04:37 No valid UPnP IGDs found
2017-09-12 18:04:37 upnp thread exit
2017-09-12 18:04:40 Loading addresses from DNS seeds (could take a while)
2017-09-12 18:04:40 197 addresses found from DNS seeds
2017-09-12 18:04:40 dnsseed thread exit
2017-09-12 18:04:57 Failed to connect best blockFailed to open mempool file from disk. Continuing anyway.
2017-09-12 18:04:57 GUI: QXcbConnection: XCB error: 3 (BadWindow), sequence: 651, resource id: 43732092, major code: 40 (TranslateCoords), minor code: 0
2017-09-12 18:04:57 tor: Thread interrupt
2017-09-12 18:04:57 torcontrol thread exit
2017-09-12 18:04:57 addcon thread exit
2017-09-12 18:04:57 opencon thread exit
2017-09-12 18:04:57 net thread exit
2017-09-12 18:04:57 msghand thread exit
2017-09-12 18:04:57 scheduler thread interrupt
2017-09-12 18:04:57 Shutdown: In progress...
2017-09-12 18:04:58 Shutdown: done
aleksej996
Sr. Member
****
Offline Offline

Activity: 490
Merit: 389


Do not trust the government


View Profile
September 12, 2017, 06:43:47 PM
 #2

I would say that your blockchain is corrupted.

You should rename folders "blocks" and "chainstate" to something else like "blocks1" and "chainstate1" and run the program again.

This should create new folders "blocks" and "chainstate" and it should start syncing from the beginning normally.
WeeHughie (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
September 12, 2017, 06:52:50 PM
 #3

Thank you so much for the quick reply! Have done that.. and am now seeing the wallet GUI and it is now syncing. Seems it could take awhile.. but at least have gotten further than I was.

Much appreciated!
aleksej996
Sr. Member
****
Offline Offline

Activity: 490
Merit: 389


Do not trust the government


View Profile
September 12, 2017, 06:55:34 PM
 #4

Thank you so much for the quick reply! Have done that.. and am now seeing the wallet GUI and it is now syncing. Seems it could take awhile.. but at least have gotten further than I was.

Much appreciated!

No problem, see you in couple of weeks.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!