nimbus-eth2
nimbus-eth2 copied to clipboard
VC: WRN/INF log spam when BN is not synced
INF 2022-05-31 15:39:12.235+02:00 Beacon node has compatible configuration endpoint="localhost:11101 [Nimbus/v22.5.1-755821-stateofus]"
INF 2022-05-31 15:39:12.235+02:00 Beacon node has compatible configuration endpoint="localhost:11101 [Nimbus/v22.5.1-755821-stateofus]"
INF 2022-05-31 15:39:12.235+02:00 Beacon node has compatible configuration endpoint="localhost:11101 [Nimbus/v22.5.1-755821-stateofus]"
WRN 2022-05-31 15:39:12.235+02:00 Beacon node not in sync sync_distance=50 head_slot=3124646 endpoint="localhost:11101 [Nimbus/v22.5.1-755821-stateofus]"
WRN 2022-05-31 15:39:12.235+02:00 Beacon node not in sync sync_distance=50 head_slot=3124646 endpoint="localhost:11101 [Nimbus/v22.5.1-755821-stateofus]"
WRN 2022-05-31 15:39:12.235+02:00 Beacon node not in sync sync_distance=50 head_slot=3124646 endpoint="localhost:11101 [Nimbus/v22.5.1-755821-stateofus]"
VC with a single configured beacon node spamming the logs - at most one WRN per slot, and a controlled amount of INF should be logged. 85d023452494b348033be85033317ebd22799980