Topic: Bitcoin Core starts to load then shuts down (Read 164 times)

Thanks for the info, shouldn't assume it's printed by Bitcoin Core just because i want to run Bitcoin Core. But is it possible a message not logged to debug.log when Bitcoin Core crashed?

Is that the data from the very bottom of the debug.log file? Bitcoin Core appends to this file... and between each run it usually creates a bunch of empty lines so you can see where one lot of debug ends and the next begins.

Make sure you have scrolled all the way to the bottom of the debug.log file and then post the last couple of hundred lines of debug... Additionally, I would recommend copy/pasting to https://pastebin.com/ and then copying the unique URL that it generates into your post here. It helps keep the thread tidy, and  it will handle a lot more lines than trying to put them all in a single post here.

It's a message that's printed before Core even starts.

That's not a bitcoin core message. Not only isn't this string in the repository, but the timestamp on the left is missing. cgroup is a feature that's used by Snap packages.

There isn't anything when you run Bitcoin Core with CMD. It'll only run Bitcoin Core and not display anything else.

Anyhow OP, if that is all you get from the debug.log. It is an ungraceful shutdown, debug.log will have several lines about shutting down Bitcoin Core instead of just stopping there abruptly. Is there any antivirus or any administration programs that blocks Bitcoin Core from running? Inter-Logic seems like some company that is involved in IT management, is it a company device?

The debug.log is not erased on each bitcoin core invocation so the beginning of the log file contains the logs from the first launch. Therefore it is natural that there is an anchors.dat opening error the first time bitcoin core is ran, because it doesn't exist yet. It's not a fatal error.

OP, are there more entries in the log file after this, particularly at the end?

Is this newly installed Bitcoin core in your machine?
Or do you have the old version installed on the same machine and upgraded it to the latest version?

Can you try to re-download and install the Bitcoin core but before you reinstall it make sure to make a backup copy of bitcoin data if it was already fully synced before or just move the whole bitcoin data to another folder then reinstall after.


I can't seem to find any other problem from your debug log except for this "ERROR: DeserializeFileDB: Failed to open file D:\Bitcoin\anchors.dat" but it shouldn't be the cause of the crash. There might be other reasons why it crashes from start up.

If it still doesn't work after reinstall try to uninstall bitcoin core make sure that you already have a backup of your bitcoin data to another folder. Now try to download the zip file version from this link below. And then extract the zip file and open the bin folder>bitcoin-qt.exe

- https://bitcoin.org/en/download

If everything works fine you can point your old backup data if you don't want to redownload again the whole block data.

Hi,

Whenever I start Bitcoin Core, it shuts down at the end of the splash screen stage.

The debug.log contains:

2021-06-04T10:55:55Z Bitcoin Core version v0.21.1 (release build)
2021-06-04T10:55:55Z Qt 5.9.8 (static), plugin=windows (static)
2021-06-04T10:55:55Z System: Windows 10 (10.0), x86_64-little_endian-llp64
2021-06-04T10:55:55Z Screen: \\.\DISPLAY1 1920x1080, pixel ratio=1.0
2021-06-04T10:55:55Z Screen: \\.\DISPLAY2 1920x1080, pixel ratio=1.0
2021-06-04T10:55:56Z Assuming ancestors of block have valid signatures.
2021-06-04T10:55:56Z Setting nMinimumChainWork=
2021-06-04T10:55:56Z Using the 'sse4(1way),sse41(4way),avx2(8way)' SHA256 implementation
2021-06-04T10:55:56Z Using RdSeed as additional entropy source
2021-06-04T10:55:56Z Using RdRand as an additional entropy source
2021-06-04T10:55:56Z Default data directory C:\Users\richard.INTER-LOGIC\AppData\Roaming\Bitcoin
2021-06-04T10:55:56Z Using data directory D:\Bitcoin
2021-06-04T10:55:56Z Config file: D:\Bitcoin\bitcoin.conf (not found, skipping)
2021-06-04T10:55:56Z Using at most 125 automatic connections (2048 file descriptors available)
2021-06-04T10:55:56Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2021-06-04T10:55:56Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2021-06-04T10:55:56Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2021-06-04T10:55:56Z Script verification uses 7 additional threads
2021-06-04T10:55:56Z scheduler thread start
2021-06-04T10:55:56Z Using wallet directory D:\Bitcoin
2021-06-04T10:55:56Z init message: Verifying wallet(s)...
2021-06-04T10:55:56Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2021-06-04T10:55:56Z Using wallet D:\Bitcoin\wallet.dat
2021-06-04T10:55:56Z BerkeleyEnvironment::Open: LogDir=D:\Bitcoin\database ErrorFile=D:\Bitcoin\db.log
2021-06-04T10:55:56Z init message: Loading banlist...
2021-06-04T10:55:56Z SetNetworkActive: true
2021-06-04T10:55:56Z Using /16 prefix for IP bucketing
2021-06-04T10:55:56Z Cache configuration:
2021-06-04T10:55:56Z * Using 2.0 MiB for block index database
2021-06-04T10:55:56Z * Using 8.0 MiB for chain state database
2021-06-04T10:55:56Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2021-06-04T10:55:56Z init message: Loading block index...
2021-06-04T10:55:56Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2021-06-04T10:55:56Z Opening LevelDB in D:\Bitcoin\blocks\index
2021-06-04T10:55:56Z Opened LevelDB successfully
2021-06-04T10:55:56Z Using obfuscation key for D:\Bitcoin\blocks\index: 0000000000000000
2021-06-04T10:56:00Z LoadBlockIndexDB: last block file = 2556
2021-06-04T10:56:00Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=96, size=124308380, heights=680993...681088, time=2021-04-28...2021-04-29)
2021-06-04T10:56:00Z Checking all blk files are present...
2021-06-04T10:56:01Z Opening LevelDB in D:\Bitcoin\chainstate
2021-06-04T10:56:02Z Opened LevelDB successfully
2021-06-04T10:56:02Z Using obfuscation key for D:\Bitcoin\chainstate: 0000000000000000
2021-06-04T10:56:02Z Loaded best chain: hashBestChain=height=681087 date=2021-04-29T11:32:14Z progress=0.983189
2021-06-04T10:56:02Z init message: Rewinding blocks...
2021-06-04T10:56:03Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started
2021-06-04T10:56:03Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s)
2021-06-04T10:56:03Z init message: Verifying blocks...
2021-06-04T10:56:03Z Verifying last 6 blocks at level 3
2021-06-04T10:56:03Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2021-06-04T10:56:13Z No coin database inconsistencies in last 6 blocks (13160 transactions)
2021-06-04T10:56:13Z  block index           16694ms
2021-06-04T10:56:13Z init message: Loading wallet...
2021-06-04T10:56:13Z BerkeleyEnvironment::Open: LogDir=D:\Bitcoin\database ErrorFile=D:\Bitcoin\db.log
2021-06-04T10:56:13Z [default wallet] Wallet File Version = 60000
2021-06-04T10:56:13Z [default wallet] Keys: 1020 plaintext, 0 encrypted, 903 w/ metadata, 1020 total. Unknown wallet records: 1
2021-06-04T10:56:13Z [default wallet] Wallet completed loading in             278ms
2021-06-04T10:56:13Z [default wallet] setKeyPool.size() = 1000
2021-06-04T10:56:13Z [default wallet] mapWallet.size() = 268
2021-06-04T10:56:13Z [default wallet] m_address_book.size() = 14
2021-06-04T10:56:13Z block tree size = 681176
2021-06-04T10:56:13Z nBestHeight = 681087
2021-06-04T10:56:13Z loadblk thread start
2021-06-04T10:56:13Z torcontrol thread start
2021-06-04T10:56:13Z Bound to [::]:8333
2021-06-04T10:56:13Z Bound to 0.0.0.0:8333
2021-06-04T10:56:13Z Bound to 127.0.0.1:8334
2021-06-04T10:56:13Z init message: Loading P2P addresses...
2021-06-04T10:56:13Z Loaded 75345 addresses from peers.dat  308ms
2021-06-04T10:56:13Z ERROR: DeserializeFileDB: Failed to open file D:\Bitcoin\anchors.dat
2021-06-04T10:56:13Z 0 block-relay-only anchors will be tried for connections.
2021-06-04T10:56:13Z init message: Starting network threads...
2021-06-04T10:56:13Z net thread start
2021-06-04T10:56:13Z dnsseed thread start
2021-06-04T10:56:13Z Waiting 300 seconds before querying DNS seeds.
2021-06-04T10:56:13Z addcon thread start
2021-06-04T10:56:13Z opencon thread start
2021-06-04T10:56:13Z init message: Done loading
2021-06-04T10:56:13Z msghand thread start


I have removed a few Ids from this log in case publishing them could compromise my wallet. (No ideas, just being careful!)