My node received caught every week in the past it was model 26 I up to date to model 27 and re-downloaded entire chain. My node is caught ant block 840959.
I attempted reboot entire server.
I dont need to reindex all once more, it’ll take a complete week once more.
How I can remedy this downside?
I dont know if this may be associated however I additionally run lnd node.
Os: Ububtu 22.04
{Hardware}:
Intel Core i7-2600
HDD2x HDD SATA 3,0 TB
RAM4x RAM 4096 MB DDR3
Right here is a few data.
bitcoin-cli -getinfo
Chain: fundamental
Blocks: 840959
Headers: 840959
Verification progress: 99.7043%
Issue: 88104191118793.16
Community: in 10, out 10, complete 20
Model: 270000
Time offset (s): 0
Proxies: n/a
Min tx relay charge price (BTC/kvB): 0.00000000
Warnings: (none)
log file:
2024-05-01T18:49:37Z Bitcoin Core model v27.0 (launch construct)
2024-05-01T18:49:37Z InitParameterInteraction: parameter interplay: -externalip set -> setting -discover=0
2024-05-01T18:49:37Z Script verification makes use of 7 extra threads
2024-05-01T18:49:37Z Utilizing the 'sse4(1way),sse41(4way)' SHA256 implementation
2024-05-01T18:49:37Z Default knowledge listing /root/.bitcoin
2024-05-01T18:49:37Z Utilizing knowledge listing /dwelling/btc_node_data
2024-05-01T18:49:37Z Config file: /root/.bitcoin/bitcoin.conf
2024-05-01T18:49:37Z Config file arg: daemon="1"
2024-05-01T18:49:37Z Config file arg: datadir="/dwelling/btc_node_data"
2024-05-01T18:49:37Z Config file arg: externalip="*.*.*.*"
2024-05-01T18:49:37Z Config file arg: incrementalrelayfee="0.00000010"
2024-05-01T18:49:37Z Config file arg: maxconnections="125"
2024-05-01T18:49:37Z Config file arg: minrelaytxfee="0.00000000"
2024-05-01T18:49:37Z Config file arg: rpcallowip="0.0.0.0/0"
2024-05-01T18:49:37Z Config file arg: rpcpassword=****
2024-05-01T18:49:37Z Config file arg: rpcport="8332"
2024-05-01T18:49:37Z Config file arg: rpcuser=****
2024-05-01T18:49:37Z Config file arg: server="1"
2024-05-01T18:49:37Z Config file arg: txindex="1"
2024-05-01T18:49:37Z Config file arg: zmqpubrawblock="tcp://127.0.0.1:28332"
2024-05-01T18:49:37Z Config file arg: zmqpubrawtx="tcp://127.0.0.1:28333"
2024-05-01T18:49:37Z Utilizing at most 125 automated connections (1024 file descriptors accessible)
2024-05-01T18:49:37Z Utilizing 16 MiB out of 16 MiB requested for signature cache, in a position to retailer 524288 parts
2024-05-01T18:49:37Z Utilizing 16 MiB out of 16 MiB requested for script execution cache, in a position to retailer 524288 parts
2024-05-01T18:49:37Z No pockets help compiled in!
2024-05-01T18:49:37Z scheduler thread begin
2024-05-01T18:49:37Z WARNING: choice -rpcallowip was specified with out -rpcbind; this does not normally make sense
2024-05-01T18:49:37Z Binding RPC on deal with ::1 port 8332
2024-05-01T18:49:37Z Binding RPC on deal with 127.0.0.1 port 8332
2024-05-01T18:49:37Z Config choices rpcuser and rpcpassword will quickly be deprecated. Regionally-run cases could take away rpcuser to make use of cookie-based auth, or could also be changed with rpcauth. Please see share/rpcauth for rpcauth auth technology.
2024-05-01T18:49:37Z Beginning HTTP server with 4 employee threads
2024-05-01T18:49:37Z Utilizing /16 prefix for IP bucketing
2024-05-01T18:49:37Z init message: Loading P2P addresses…
2024-05-01T18:49:37Z Loaded 67144 addresses from friends.dat 322ms
2024-05-01T18:49:37Z init message: Loading banlist…
2024-05-01T18:49:37Z SetNetworkActive: true
2024-05-01T18:49:37Z AddLocal(*.*.*.*:8333,4)
2024-05-01T18:49:37Z Script verification makes use of 7 extra threads
2024-05-01T18:49:37Z Cache configuration:
2024-05-01T18:49:37Z * Utilizing 2.0 MiB for block index database
2024-05-01T18:49:37Z * Utilizing 56.0 MiB for transaction index database
2024-05-01T18:49:37Z * Utilizing 8.0 MiB for chain state database
2024-05-01T18:49:37Z * Utilizing 384.0 MiB for in-memory UTXO set (plus as much as 286.1 MiB of unused mempool house)
2024-05-01T18:49:37Z init message: Loading block index…
2024-05-01T18:49:37Z Assuming ancestors of block 000000000000000000026811d149d4d261995ec5b3f64f439a0a10e1a464af9a have legitimate signatures.
2024-05-01T18:49:37Z Setting nMinimumChainWork=000000000000000000000000000000000000000063c4ebd298db40af57541800
2024-05-01T18:49:37Z Opening LevelDB in /dwelling/btc_node_data/blocks/index
2024-05-01T18:49:37Z Opened LevelDB efficiently
2024-05-01T18:49:37Z Utilizing obfuscation key for /dwelling/btc_node_data/blocks/index: 0000000000000000
2024-05-01T18:49:42Z LoadBlockIndexDB: final block file = 4260
2024-05-01T18:49:42Z LoadBlockIndexDB: final block file data: CBlockFileInfo(blocks=38, dimension=62375251, heights=840791...841661, time=2024-04-25...2024-05-01)
2024-05-01T18:49:42Z Checking all blk information are current...
2024-05-01T18:49:43Z Initializing chainstate Chainstate [ibd] @ peak -1 (null)
2024-05-01T18:49:43Z Opening LevelDB in /dwelling/btc_node_data/chainstate
2024-05-01T18:49:43Z Opened LevelDB efficiently
2024-05-01T18:49:43Z Utilizing obfuscation key for /dwelling/btc_node_data/chainstate: 28f95d6aa09096aa
2024-05-01T18:49:43Z Loaded greatest chain: hashBestChain=000000000000000000023b43da4a5fa2ac60433f0d5205af3f0f4aeae872ae65 peak=840959 date=2024-04-26T14:07:04Z progress=0.997045
2024-05-01T18:49:43Z Opening LevelDB in /dwelling/btc_node_data/chainstate
2024-05-01T18:49:44Z Opened LevelDB efficiently
2024-05-01T18:49:44Z Utilizing obfuscation key for /dwelling/btc_node_data/chainstate: 28f95d6aa09096aa
2024-05-01T18:49:44Z [Chainstate [ibd] @ peak 840959 (000000000000000000023b43da4a5fa2ac60433f0d5205af3f0f4aeae872ae65)] resized coinsdb cache to eight.0 MiB
2024-05-01T18:49:44Z [Chainstate [ibd] @ peak 840959 (000000000000000000023b43da4a5fa2ac60433f0d5205af3f0f4aeae872ae65)] resized coinstip cache to 384.0 MiB
2024-05-01T18:49:44Z init message: Verifying blocks…
2024-05-01T18:49:44Z Verifying final 6 blocks at degree 3
2024-05-01T18:49:44Z Verification progress: 0%
2024-05-01T18:49:44Z Verification progress: 16%
2024-05-01T18:49:44Z Verification progress: 33%
2024-05-01T18:49:44Z Verification progress: 50%
2024-05-01T18:49:45Z Verification progress: 66%
2024-05-01T18:49:45Z Verification progress: 83%
2024-05-01T18:49:45Z Verification progress: 99%
2024-05-01T18:49:45Z Verification: No coin database inconsistencies in final 6 blocks (21785 transactions)
2024-05-01T18:49:45Z block index 8352ms
2024-05-01T18:49:45Z Opening LevelDB in /dwelling/btc_node_data/indexes/txindex
2024-05-01T18:49:46Z Opened LevelDB efficiently
2024-05-01T18:49:46Z Utilizing obfuscation key for /dwelling/btc_node_data/indexes/txindex: 0000000000000000
2024-05-01T18:49:46Z Setting NODE_NETWORK on non-prune mode
2024-05-01T18:49:46Z block tree dimension = 841662
2024-05-01T18:49:46Z nBestHeight = 840959
2024-05-01T18:49:46Z initload thread begin
2024-05-01T18:49:46Z Sure to 127.0.0.1:8334
2024-05-01T18:49:46Z Sure to [::]:8333
2024-05-01T18:49:46Z torcontrol thread begin
2024-05-01T18:49:46Z Sure to 0.0.0.0:8333
2024-05-01T18:49:46Z txindex thread begin
2024-05-01T18:49:46Z txindex is enabled at peak 840959
2024-05-01T18:49:46Z txindex thread exit
2024-05-01T18:49:46Z Loading 0 mempool transactions from disk...
2024-05-01T18:49:46Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 ready for preliminary broadcast
2024-05-01T18:49:46Z initload thread exit
2024-05-01T18:49:46Z Loaded 2 addresses from "anchors.dat"
2024-05-01T18:49:46Z 2 block-relay-only anchors might be tried for connections.
2024-05-01T18:49:46Z init message: Beginning community threads…
2024-05-01T18:49:46Z web thread begin
2024-05-01T18:49:46Z dnsseed thread begin
2024-05-01T18:49:46Z Ready 300 seconds earlier than querying DNS seeds.
2024-05-01T18:49:46Z addcon thread begin
2024-05-01T18:49:46Z opencon thread begin
2024-05-01T18:49:46Z init message: Performed loading
2024-05-01T18:49:46Z msghand thread begin
2024-05-01T18:49:46Z New block-relay-only v1 peer related: model: 70016, blocks=841672, peer=0
2024-05-01T18:49:47Z New block-relay-only v1 peer related: model: 70016, blocks=841672, peer=1
2024-05-01T18:49:53Z New outbound-full-relay v2 peer related: model: 70016, blocks=841672, peer=4
2024-05-01T18:49:54Z New outbound-full-relay v2 peer related: model: 70016, blocks=841672, peer=6
2024-05-01T18:49:55Z New outbound-full-relay v1 peer related: model: 70016, blocks=841672, peer=5
2024-05-01T18:49:56Z New outbound-full-relay v2 peer related: model: 70016, blocks=841672, peer=7
2024-05-01T18:49:56Z New outbound-full-relay v1 peer related: model: 70016, blocks=841672, peer=8
2024-05-01T18:49:56Z New outbound-full-relay v1 peer related: model: 70016, blocks=841672, peer=9
2024-05-01T18:49:57Z P2P friends accessible. Skipped DNS seeding.
2024-05-01T18:49:57Z dnsseed thread exit
2024-05-01T18:50:23Z New outbound-full-relay v1 peer related: model: 70016, blocks=841672, peer=18
2024-05-01T18:50:29Z New outbound-full-relay v1 peer related: model: 70016, blocks=841672, peer=20
2024-05-01T18:50:41Z New outbound-full-relay v1 peer related: model: 70016, blocks=841672, peer=22
2024-05-01T18:50:42Z New outbound-full-relay v1 peer related: model: 70016, blocks=841672, peer=24
2024-05-01T18:51:12Z New outbound-full-relay v1 peer related: model: 70016, blocks=841672, peer=37
2024-05-01T18:51:14Z New outbound-full-relay v1 peer related: model: 70016, blocks=841672, peer=36
2024-05-01T18:51:57Z New outbound-full-relay v1 peer related: model: 70016, blocks=841673, peer=44
2024-05-01T18:52:30Z New outbound-full-relay v1 peer related: model: 70016, blocks=841673, peer=46
2024-05-01T18:52:31Z New outbound-full-relay v2 peer related: model: 70016, blocks=841673, peer=47
2024-05-01T18:52:36Z New outbound-full-relay v1 peer related: model: 70015, blocks=841672, peer=48
getchaintips
bitcoin-cli getchaintips
[
{
"height": 841661,
"hash": "00000000000000000000d60f130278fd774a1f23ee464a8e1e0c65825f6eea44",
"branchlen": 702,
"status": "invalid"
},
{
"height": 840959,
"hash": "000000000000000000023b43da4a5fa2ac60433f0d5205af3f0f4aeae872ae65",
"branchlen": 0,
"status": "active"
}
]
