Backwards Sync Halt

[siladu]

dev-elc-bu-tk-mainnet-simon-fix-busy3-06 halted here:

{"@timestamp":"2024-10-07T09:57:30,916","level":"INFO","thread":"nioEventLoopGroup-3-4","class":"BackwardSyncContext","message":"Backward sync phase 2 of 2, 8.82% completed, imported 129 blocks of at least 1462 (c
urrent head 20911598, target head 20912931). Peers: 25","throwable":""}

and started again with no intervention here:

{"@timestamp":"2024-10-08T09:02:11,378","level":"INFO","thread":"ForkJoinPool.commonPool-worker-902","class":"BackwardSyncStep","message":"Backward sync phase 1 of 2, 98.41% completed, downloaded 8229 headers of a
t least 8362. Peers: 25","throwable":""}

Following the halt (while no INFO logs being produced), I queried admin_peers, then enabled a minute of DEBUG, followed by a minute of TRACE logging...

dev-elc-bu-tk-mainnet-simon-fix-busy3-06_besu.log.gz
dev-elc-bu-tk-mainnet-simon-fix-busy3-06_admin_peers.log

---

dev-elc-bu-tk-mainnet-simon-fix-busy3-14 halted here:

{"@timestamp":"2024-10-07T08:02:33,502","level":"INFO","thread":"nioEventLoopGroup-3-7","class":"BackwardSyncContext","message":"Backward sync phase 2 of 2, 8.43% completed, imported 126 blocks of at least 1495 (c
urrent head 20910988, target head 20912357). Peers: 25","throwable":""}

Following the halt (while no INFO logs being produced), I queried admin_peers, then enabled a minute of TRACE logging...

dev-elc-bu-tk-mainnet-simon-fix-busy3-14_besu.log.gz
dev-elc-bu-tk-mainnet-simon-fix-busy3-14_admin_peers.log

---

It also happened on dev-elc-bu-tk-mainnet-simon-fix-busy2-03 but I only grabbed the admin_peers, not the logs...
dev-elc-bu-tk-mainnet-simon-fix-busy2-03_admin_peers.log