Description
During node startup, the P2P layer logs ERROR level messages for normal DHT cold-start behavior:
ERROR go-p2p/peerManager.go:102 error when advertising. {"error": "failed to find any peer in table"}
ERROR go-p2p/peerManager.go:117 error when finding peers {"error": "no peers are found"}
These are expected during the first few seconds before DHT peer discovery completes. Non-bootnode nodes always see these errors briefly after startup.
Suggestion
Downgrade these to WARN level in go-p2p (upstream dependency), or add a grace period in peerManager.JoinOverlay that suppresses error logging for the first N seconds after startup.
Impact
- Noisy logs during node startup confuse operators
- Makes it harder to spot real P2P errors in log output
- Triggers false alerts in log monitoring systems
Description
During node startup, the P2P layer logs
ERRORlevel messages for normal DHT cold-start behavior:These are expected during the first few seconds before DHT peer discovery completes. Non-bootnode nodes always see these errors briefly after startup.
Suggestion
Downgrade these to
WARNlevel ingo-p2p(upstream dependency), or add a grace period inpeerManager.JoinOverlaythat suppresses error logging for the first N seconds after startup.Impact