*blockchain.BlockChain start failed / *node.BlockdagFull start failed / transactions is empty

[leon-DK]

2025-10-17|13:25:31.518 [INFO ] Try to restore block state for EVM module=BDAG evm.hash=0xbade7dfaac2ca6a2636b157689e86e34f4162294920b28bf2ed9e944140fa587 evm.number=13069199 state.order=13286819
2025-10-17|13:25:31.519 [INFO ] update BdagPool snapshot module=BDAG size=2
2025-10-17|13:25:31.520 [INFO ] Imported new chain segment number=13,069,199 hash=bade7d..0fa587 blocks=1 txs=0 mgas=0.000 elapsed=1.044ms mgasps=0.000 age=3h29m snapdiffs=2.71MiB triediffs=248.95KiB triedirty=75.60KiB
2025-10-17|13:25:31.520 [INFO ] Try to restore block state for EVM module=BDAG evm.hash=0x1b15f7807ead55708c60e31de2e6937480d3b78259868dabd412f8f255bf594f evm.number=13069200 state.order=13286820
2025-10-17|13:25:31.520 [INFO ] update BdagPool snapshot module=BDAG size=2
2025-10-17|13:25:31.521 [INFO ] Imported new chain segment number=13,069,200 hash=1b15f7..bf594f blocks=1 txs=0 mgas=0.000 elapsed=1.092ms mgasps=0.000 age=3h29m snapdiffs=2.71MiB triediffs=249.04KiB triedirty=75.60KiB
2025-10-17|13:25:31.521 [INFO ] Try to restore block state for EVM module=BDAG evm.hash=0x59c4ddded350e91dba74c4d8708541a27eb4fdcd2d07638bcd78a57ba59fd4ec evm.number=13069201 state.order=13286821
2025-10-17|13:25:31.522 [INFO ] Imported new chain segment number=13,069,201 hash=59c4dd..9fd4ec blocks=1 txs=0 mgas=0.000 elapsed=1.085ms mgasps=0.000 age=3h28m57s snapdiffs=2.71MiB triediffs=249.10KiB triedirty=75.60KiB
2025-10-17|13:25:31.522 [INFO ] update BdagPool snapshot module=BDAG size=2
2025-10-17|13:25:31.522 [INFO ] Try to restore block state for EVM module=BDAG evm.hash=0x7243fcc572fdddd860f65888cfaf1c000ac147ac56fd179901868c7f25c64560 evm.number=13069202 state.order=13286824
2025-10-17|13:25:31.522 [INFO ] Try to rebuild evm block module=BDAG state.order=13286824
2025-10-17|13:25:31.522 [ERROR] *blockchain.BlockChain start failed: bdag chain env error:targetEVM.number=13069241, targetEVM.hash=0xb1be8a1895c13d9e970a9cbc53f002ba31fb2ecdc3adc046d4dd8c5410d8b900, targetState.order=13286865, cur.number=13009979, cur.hash=0x6063418bbc90ff5563865ff846279870c952456466fc4d1a655d9bd34c0186b2, transactions is empty module=service
2025-10-17|13:25:31.522 [ERROR] *node.BlockdagFull start failed: bdag chain env error:targetEVM.number=13069241, targetEVM.hash=0xb1be8a1895c13d9e970a9cbc53f002ba31fb2ecdc3adc046d4dd8c5410d8b900, targetState.order=13286865, cur.number=13009979, cur.hash=0x6063418bbc90ff5563865ff846279870c952456466fc4d1a655d9bd34c0186b2, transactions is empty module=service
2025-10-17|13:25:31.522 [ERROR] Uable to start server error="bdag chain env error:targetEVM.number=13069241, targetEVM.hash=0xb1be8a1895c13d9e970a9cbc53f002ba31fb2ecdc3adc046d4dd8c5410d8b900, targetState.order=13286865, cur.number=13009979, cur.hash=0x6063418bbc90ff5563865ff846279870c952456466fc4d1a655d9bd34c0186b2, transactions is empty"
2025-10-17|13:25:31.522 [INFO ] Stopping Server module=node
2025-10-17|13:25:31.522 [INFO ] Close module=CDB name="Chain DB"
2025-10-17|13:25:31.522 [INFO ] update BdagPool snapshot module=BDAG size=2
2025-10-17|13:25:31.526 [INFO ] Shutdown complete
2025-10-17|13:25:31.526 [ERROR] bdag chain env error:targetEVM.number=13069241, targetEVM.hash=0xb1be8a1895c13d9e970a9cbc53f002ba31fb2ecdc3adc046d4dd8c5410d8b900, targetState.order=13286865, cur.number=13009979, cur.hash=0x6063418bbc90ff5563865ff846279870c952456466fc4d1a655d9bd34c0186b2, transactions is empty
2025-10-17|13:25:31.977 [WARN ] liveness probe failed url=http://127.0.0.1:6061/healthz err="Get "http://127.0.0.1:6061/healthz\": dial tcp 127.0.0.1:6061: connect: connection refused"
2025-10-17|13:26:32.977 [ERROR] liveness probe exceeded timeout; forcing shutdown url=http://127.0.0.1:6061/healthz timeout=1m0s err="Get "http://127.0.0.1:6061/healthz\": dial tcp 127.0.0.1:6061: connect: connection refused"
2025-10-17|13:26:32.977 [INFO ] stopping worker and inner binary
2025-10-17|13:26:32.977 [WARN ] inner binary exited with error err="exit status 1"
2025-10-17|13:26:32.977 [INFO ] worker stopped

[zrusznak]

Read my post "nodes are failing left and right" :-}
Those log lines mean the container’s wrapper process (the “worker”) keeps checking its own internal health endpoint at http://127.0.0.1:6061/healthz, but the main node binary never actually starts — so the probe times out and the wrapper shuts it down every minute.

That symptom almost always points to the BDAG chain environment corruption (the same bdag chain env error you saw earlier) or a missing local state reset.
The code is corrupt ,you cannot do anything about it.

[leon-DK]

Yes this obviously occurred after a crash (again..)
Just wanted to point out the fact that the data gets corrupted a lot.
Like you say, nodes failing left and right and chain data being corrupted in the process.
Something needs to happen..

[zrusznak]

Now if you going to restart it will crash in less than 30 sec