"Invalid validator" messages logged by the proxies

[gastonponti]

WARN [05-25|19:51:21.381] Error in sending message func=AsyncMulticastCeloMsg msgCode=17 peer="Peer efc6f01d5f6091d8 <my validator ip address>:50350" ethMsgCode=17 err="shutting down"

Proxies seems to be maintaining connections with validators that are not part of the validator set anymore

[bcamacho]

I recently encountered an issue with my Baklava node and discovered that others had experienced the same. I conducted a quick search, found this issue, and reached out to @gastonponti for assistance. Thank you, @gastonponti, for your support! Here are the results:

Issue Description

The error in question is often associated with the way the proxy manages messages when it retains both old and new enodes in its table.

Recommended workaround

Reboot the proxy. Rebooting usually resolves the problem and eliminates the error message.

FAQ: Can I disable the warning messages?

If the error message persists and becomes bothersome, you can modify the system settings by setting the verbosity to level 1. This change will decrease the frequency of error notifications, making them less obtrusive. Setting verbosity to level 1 should be effective, but please note that this may affect the tracking of warnings for monitoring purposes.

Error message example:

WARN [05-04|19:21:01.261] Error in sending message func=AsyncMulticastCeloMsg msgCode=17 peer="Peer 062535bfaec8eb63 10.128.0.6:58134" ethMsgCode=17 err="shutting down"