/var/lib/kubelet/device-plugins/kubelet.sock Connection refused about kubernetes HOT 7 OPEN

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from kubernetes.

Ignoring errors is never a good option anyway. In this case Serve can return errors if listener.Accept fails, that means for any connection made we are not handling possible errors.

from kubernetes.

/sig node

from kubernetes.

/assign

from kubernetes.

This seems to be a kubelet issue, perhaps we can transfer it to the kubelet repo?

Edit: Please ignore, I'm mixing kubelet and kubectl 😆

from kubernetes.

/cc

from kubernetes.

I looked a bit into this, looks like the Go internal/poll implementation already retry Accept errors (Serve calls net.Listener.Accept):

https://github.com/golang/go/blob/5bf8c0c/src/internal/poll/fd_unix.go#L611-L632

This means that only fatal errors are returned by Serve, errors that must be handled and there is no way to retry them.

Given the message /var/lib/kubelet/device-plugins/kubelet.sock Connection refused my bet is that the server died, Serve returned an error that was not handled and the program continued running.

from kubernetes.