nodes are crashing one by one

[zrusznak]

The error is that the "connection is refused at ...:6061"
Has anyone got the same issue?

[zrusznak]

2025-10-03|12:12:09.519 [INFO ] Stopping Server module=node
2025-10-03|12:12:09.519 [INFO ] Close module=CDB name="Chain DB"
2025-10-03|12:12:09.520 [INFO ] update BdagPool snapshot module=BDAG size=1
2025-10-03|12:12:09.533 [INFO ] Shutdown complete
2025-10-03|12:12:09.533 [ERROR] bdag chain env error:targetEVM.number=4333181, targetEVM.hash=0xf9fa6f88c73644373b6a12ec06875ff8cd62a050e78a332d964dee271a327db3, targetState.order=4457510, cur.number=4320000, cur.hash=0x033e237585ece74e1bc23cc6adcb94f136e269a3377fcb4d249a7958423bd3a3, transactions is empty
2025-10-03|12:12:09.927 [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-03|12:13:10.928 [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-03|12:13:10.928 [INFO ] stopping worker and inner binary
2025-10-03|12:13:10.928 [WARN ] inner binary exited with error err="exit status 1"
2025-10-03|12:13:10.928 [INFO ] worker stopped

[zrusznak]

http://127.0.0.1:6061/healthz
Is this a virus???????????????

[zrusznak]

@urkishan
2025-10-03|12:12:09.519 [INFO ] Stopping Server module=node
2025-10-03|12:12:09.519 [INFO ] Close module=CDB name="Chain DB"
2025-10-03|12:12:09.520 [INFO ] update BdagPool snapshot module=BDAG size=1
2025-10-03|12:12:09.533 [INFO ] Shutdown complete
2025-10-03|12:12:09.533 [ERROR] bdag chain env error:targetEVM.number=4333181, targetEVM.hash=0xf9fa6f88c73644373b6a12ec06875ff8cd62a050e78a332d964dee271a327db3, targetState.order=4457510, cur.number=4320000, cur.hash=0x033e237585ece74e1bc23cc6adcb94f136e269a3377fcb4d249a7958423bd3a3, transactions is empty
2025-10-03|12:12:09.927 [WARN ] liveness probe failed url=http://127.0.0.1:6061/healthz err="Get "[http://127.0.0.1:6061/healthz](http://127.0.0.1:6061/healthz%5C)": dial tcp 127.0.0.1:6061: connect: connection refused"
2025-10-03|12:13:10.928 [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](http://127.0.0.1:6061/healthz%5C)": dial tcp 127.0.0.1:6061: connect: connection refused"
2025-10-03|12:13:10.928 [INFO ] stopping worker and inner binary
2025-10-03|12:13:10.928 [WARN ] inner binary exited with error err="exit status 1"
2025-10-03|12:13:10.928 [INFO ] worker stopped

[zrusznak]

@urkishan ,@s-h-ubham ,@dev-580
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.