Weird errors during shutdown of VM

[msimkunas]

I'm seeing these weird errors when shutting down a VZ VM:

accept tcp 127.0.0.1:60022: use of closed network connection

and

dhcp: unhandled message type: RELEASE

They don't seem to be causing issues. Why are they reported to the user?

[afbjorklund]

The dhcp log message is from gvisor-tap-vsock, it is reported in the log - and the log is shown to the user.

https://github.com/containers/gvisor-tap-vsock/blob/v0.8.6/pkg/services/dhcp/dhcp.go#L64

I'm not sure what a DHCP server is supposed to be doing with a RELEASE message, but it ain't doing it...

If it is important to avoid this log message, open an issue about it? (As in #1381 (comment))

---

• vz: dismiss [hostagent] r.CreateEndpoint() = connection was refused #1160

• Move several log messages to the debug level containers/gvisor-tap-vsock#408

Ideally libraries should not log, or at least be configurable...

But this one is using the default logrus, so it gets mixed in.

[msimkunas]

Thanks for the explanation. Those log messages don't cause any issues for me, I just wanted to know if they're expected and do not indicate some kind of issue.

[afbjorklund]

It probably should have been a Warning rather than an Error, but most likely a debug or trace... (and not even shown)

INFO[0000] [hostagent] Shutting down VZ                 
ERRO[0000] [hostagent] dhcp: unhandled message type: RELEASE 
INFO[0000] [hostagent] [VZ] - vm state change: stopped  

[jandubois]

The problem is that the error comes from gvisor-tap-vsock, so we cannot easily change the log level: https://github.com/containers/gvisor-tap-vsock/blob/34913e9021f676d6cbdb0d19282db677b04b9c42/pkg/services/dhcp/dhcp.go#L71

[afbjorklund]

Created an issue for it: #3778

The code change is just one line, but getting it accepted upstream is another story (but worked before)

[afbjorklund]

Why are they reported to the user?

There could be more options about what kind of log output you want to see, like minikube --alsologtostderr

• Show more user-friendly output, from the start command #1311

Most of it belongs in a log file, and not on the console

$ limactl start
Starting "default"
READY.