Open twoeths opened 1 year ago
the block 0x961ee2ae2a7b0cb8f2623edcb1c7a408c8258ddfcd3a2a5c71cb6640ed2e5ed0
really does not part of canonical chain, that's why we got the error https://beaconcha.in/slot/0x961ee2ae2a7b0cb8f2623edcb1c7a408c8258ddfcd3a2a5c71cb6640ed2e5ed0
The other error in the log file is
Jun-28 09:39:11.349[chain] [36mverbose[39m: Clock slot slot=6761294
Jun-28 09:39:11.350[api] [31merror[39m: Error on submitPoolAttestations [0] slot=6761293, index=2 code=ATTESTATION_ERROR_UNKNOWN_OR_PREFINALIZED_BEACON_BLOCK_ROOT, root=0x8668b5a0199c5b52276f4529d309c5b080b30ee59d7ef68d592ea5c8e1f288f6
Error: ATTESTATION_ERROR_UNKNOWN_OR_PREFINALIZED_BEACON_BLOCK_ROOT
the request is likely from a fallbackUrl setup, node is syncing so UnknownBlock service is not enabled, so error was returned when next clock slot comes. I'd suggest having a better log to inform user in this case
@nflaig's error is the same, target root was really not part of canonical chain https://goerli.beaconcha.in/slot/c4d460df1cc7c4da058433f035f9a4b40cb9bc4ef2b4011e93425dc20b5259b5
when node is synced, we'll search for this block and there maybe no error but after a restart, this error will happen since req/resp only returns canonical chain. I think let it as is and reducing log level is enough, if possible we'll add "node is syncing" to the log to investigate this issue easier in the future
According to logging policy, these errors should probably be debug logs
Describe the bug
On a restart, we can get an error like, see https://discord.com/channels/593655374469660673/593655641445367808/1123615328761552958
beacon-2023-06-28-trunc.log
@nflaig also got this error consistently
Expected behavior
verbose/debug
log levelSteps to reproduce
No response
Additional context
No response
Operating system
Linux
Lodestar version or commit hash
v1.9.0