-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
We see in cnv.engineering that the log "failed to connect to cmd client socket during resync" is recurring.
We need to understand if the log is correct and consider if an alert is required or if we already have one.
Looking at the code, looks like this issue is not an error as commented:
// Ignore failure to connect to client. // These are all local connections via unix socket. // A failure to connect means there's nothing on the other // end listening.
So maybe the log severity should be changed to info/debug.
To see the logs in cnv.engineering go to the Observe->Logs and run query:
{ log_type="infrastructure", kubernetes_namespace_name="openshift-cnv" } |= `failed to connect to cmd client socket during resync` | json | level=~"error|err|eror"