bitcoind – Bitcoin-cli retains crashing round block 810180 and can all the time restart at block 809941

0
64


So I am downloading and syncing the blockchain utilizing bitcoin core. Every time it teaches block 810810, the terminal will simply shut by itself after which I restart the node, it is going to begin syncing from block 809940. The debug.log file does not present any errors, it simply stops at that time. This has occurred about 5 instances in a row now. The laptop computer I am operating it on has 8gb of ram and a terabyte of harddrive area. I checked for any {hardware} failures however the harddrive passes all checks. For what it is value, my bitcoin.conf file appears like:

prune=5000

That is it.

The debug log’s output after I run it with simply the -daemon flag is:


2023-10-07T00:29:39Z UpdateTip: new finest=00000000000000000000f560e0495f776189c1ba681c8fe4068ecd33d16584d6 peak=810181 model=0x302a0000 log2_work=94.450324 tx=902025944 date="2023-10-01T18:26:02Z" progress=0.998156 cache=270.2MiB(1774949txo)

2023-10-07T00:29:39Z New outbound peer linked: model: 70015, blocks=810972, peer=268 (outbound-full-relay)

2023-10-07T00:29:51Z UpdateTip: new finest=00000000000000000001efe8dc90d79e52d1de934ecffc03572d847ea8fc7296 peak=810182 model=0x241c2000 log2_work=94.450337 tx=902028692 date="2023-10-01T18:33:00Z" progress=0.998158 cache=271.1MiB(1781754txo)

2023-10-07T00:29:58Z UpdateTip: new finest=000000000000000000040caf3f438bb15731f6dc0f5ce1eaa6cd2ee8213d72dd peak=810183 model=0x22c88000 log2_work=94.450350 tx=902031063 date="2023-10-01T18:35:09Z" progress=0.998158 cache=271.6MiB(1786104txo)

The previous couple of strains of the debug file when operating it with the flags -nodaemon and -debug are:

2023-10-07T06:30:41Z [net] obtained block 00000000000000000000f560e0495f776189c1ba681c8fe4068ecd33d16584d6 peer=56
2023-10-07T06:30:41Z [net] Added connection peer=63
2023-10-07T06:30:41Z [validation] Pre-allocating as much as place 0x5000000 in blk03857.dat
2023-10-07T06:30:41Z [bench] FlushStateToDisk: discover recordsdata to prune began
2023-10-07T06:30:51Z [rand] Feeding 18303 bytes of dynamic atmosphere knowledge into RNG

Any concept what might be happening? It is taken me 10 days to get thus far. I actually hope I can proceed from right here.

LEAVE A REPLY

Please enter your comment!
Please enter your name here