bitcoin core 24.0 full node cease synchronisation for no causes or when restart bitcoind is {that a} bug?

0
63


0 bitcoin core was working good however since 4 days in the past it is stopped the syncing , the pockets have 2 caught transactions for low charge however that not the explanation I triad to make new pockets , eliminated mempool.dat file , make zapwallettxes (however not working in 24.0 model) , doing -reindex and lastly I eliminated all of the server in reinstalled every part and nonetheless similar drawback

this my .conf was working from 2 years

daemon=1
shrinkdebuglog=5

prune=1050

regtest=0

proxy=127.0.0.1:9050
hear=0

# this technique is deprecated, ought to be changed by rpcauth
rpcuser=bitcoind
rpcpassword=password

keypool=4000

txconfirmtarget=2
fallbackfee=0.0002
spendzeroconfchange=0

and this the logs each time I restart bitcoind service

2023-05-06T21:55:40Z Ignoring unknown configuration worth shrinkdebuglog
2023-05-06T21:55:40Z Bitcoin Core model v24.0.1 (launch construct)
2023-05-06T21:55:40Z InitParameterInteraction: parameter interplay: -proxy set -> setting -upnp=0
2023-05-06T21:55:40Z InitParameterInteraction: parameter interplay: -proxy set -> setting -natpmp=0
2023-05-06T21:55:40Z InitParameterInteraction: parameter interplay: -proxy set -> setting -discover=0
2023-05-06T21:55:40Z InitParameterInteraction: parameter interplay: -listen=0 -> setting -listenonion=0
2023-05-06T21:55:40Z InitParameterInteraction: parameter interplay: -listen=0 -> setting -i2pacceptincoming=0
2023-05-06T21:55:40Z Utilizing the 'sse4(1way),sse41(4way)' SHA256 implementation
2023-05-06T21:55:40Z Utilizing RdRand as an extra entropy supply
2023-05-06T21:55:40Z Default information listing /house/bitcoin/.bitcoin
2023-05-06T21:55:40Z Utilizing information listing /var/lib/bitcoind
2023-05-06T21:55:40Z Config file: /bitcoin/bitcoin.conf
2023-05-06T21:55:40Z Config file arg: daemon="1"
2023-05-06T21:55:40Z Config file arg: fallbackfee="0.0002"
2023-05-06T21:55:40Z Config file arg: keypool="4000"
2023-05-06T21:55:40Z Config file arg: hear="0"
2023-05-06T21:55:40Z Config file arg: proxy="127.0.0.1:9050"
2023-05-06T21:55:40Z Config file arg: prune="1050"
2023-05-06T21:55:40Z Config file arg: regtest="0"
2023-05-06T21:55:40Z Config file arg: rpcpassword=****
2023-05-06T21:55:40Z Config file arg: rpcuser=****
2023-05-06T21:55:40Z Config file arg: spendzeroconfchange="0"
2023-05-06T21:55:40Z Config file arg: txconfirmtarget="2"
2023-05-06T21:55:40Z Command-line arg: conf="/and so forth/bitcoin/bitcoin.conf"
2023-05-06T21:55:40Z Command-line arg: daemon=""
2023-05-06T21:55:40Z Command-line arg: datadir="/var/lib/bitcoind"
2023-05-06T21:55:40Z Command-line arg: pid="/run/bitcoind/bitcoind.pid"
2023-05-06T21:55:40Z Utilizing at most 125 computerized connections (1024 file descriptors out there)
2023-05-06T21:55:40Z Utilizing 16 MiB out of 16 MiB requested for signature cache, capable of retailer 524288 parts
2023-05-06T21:55:40Z Utilizing 16 MiB out of 16 MiB requested for script execution cache, capable of retailer 524288 parts
2023-05-06T21:55:40Z Script verification makes use of 7 further threads
2023-05-06T21:55:40Z scheduler thread begin
2023-05-06T21:55:40Z [http] creating work queue of depth 16
2023-05-06T21:55:40Z Config choices rpcuser and rpcpassword will quickly be deprecated. Domestically-run cases could take away rpcuser to make use of cookie-based auth,>
2023-05-06T21:55:40Z [http] beginning 4 employee threads
2023-05-06T21:55:40Z Utilizing pockets listing /var/lib/bitcoind
2023-05-06T21:55:40Z init message: Verifying pockets(s)…
2023-05-06T21:55:40Z Utilizing /16 prefix for IP bucketing
2023-05-06T21:55:40Z init message: Loading P2P addresses…
2023-05-06T21:55:40Z Loaded 714 addresses from friends.dat  3ms
2023-05-06T21:55:40Z init message: Loading banlist…
2023-05-06T21:55:40Z SetNetworkActive: true
2023-05-06T21:55:40Z Cache configuration:
2023-05-06T21:55:40Z * Utilizing 2.0 MiB for block index database
2023-05-06T21:55:40Z * Utilizing 8.0 MiB for chain state database
2023-05-06T21:55:40Z * Utilizing 440.0 MiB for in-memory UTXO set (plus as much as 286.1 MiB of unused mempool area)
2023-05-06T21:55:40Z init message: Loading block index…
2023-05-06T21:55:40Z Assuming ancestors of block 00000000000000000009c97098b5295f7e5f183ac811fb5d1534040adb93cabd have legitimate signatures.
2023-05-06T21:55:40Z Setting nMinimumChainWork=00000000000000000000000000000000000000003404ba0801921119f903495e
2023-05-06T21:55:40Z Prune configured to focus on 1050 MiB on disk for block and undo information.
2023-05-06T21:55:40Z Switching lively chainstate to Chainstate [ibd] @ peak -1 (null)
2023-05-06T21:55:40Z Opening LevelDB in /var/lib/bitcoind/blocks/index
2023-05-06T21:55:40Z Opened LevelDB efficiently
2023-05-06T21:55:40Z Utilizing obfuscation key for /var/lib/bitcoind/blocks/index: 0000000000000000
2023-05-06T21:55:40Z LoadBlockIndexDB: final block file = 0
2023-05-06T21:55:40Z LoadBlockIndexDB: final block file data: CBlockFileInfo(blocks=1, measurement=293, heights=0...0, time=2009-01-03...2009-01-03)
2023-05-06T21:55:40Z Checking all blk information are current...
2023-05-06T21:55:40Z Opening LevelDB in /var/lib/bitcoind/chainstate
2023-05-06T21:55:40Z Opened LevelDB efficiently
2023-05-06T21:55:40Z Utilizing obfuscation key for /var/lib/bitcoind/chainstate: 9b25a94db49ce1ad
2023-05-06T21:55:40Z Loaded finest chain: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f peak=0 date=2009-01-03T18:15:0>
2023-05-06T21:55:40Z init message: Verifying blocks…
2023-05-06T21:55:40Z  block index               6ms
2023-05-06T21:55:40Z init message: Pruning blockstore…
2023-05-06T21:55:40Z block tree measurement = 1
2023-05-06T21:55:40Z nBestHeight = 0
2023-05-06T21:55:40Z loadblk thread begin
2023-05-06T21:55:40Z Loaded 0 addresses from "anchors.dat"
2023-05-06T21:55:40Z 0 block-relay-only anchors can be tried for connections.
2023-05-06T21:55:40Z init message: Beginning community threads…
2023-05-06T21:55:40Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 ready for preliminary broadcast
2023-05-06T21:55:40Z loadblk thread exit
2023-05-06T21:55:40Z internet thread begin
2023-05-06T21:55:40Z dnsseed thread begin
2023-05-06T21:55:40Z Ready 11 seconds earlier than querying DNS seeds.

LEAVE A REPLY

Please enter your comment!
Please enter your name here