-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Open
Description
The debugging options
--v=0: log level for V logs
--vmodule=: comma-separated list of pattern=N settings for file-filtered logging
only apply to cadvisor, but not to the other go modules.
These are all however unnecessarily verbose.
W0725 08:54:49.697305 1 info.go:53] Couldn't collect info from any of the files in "/etc/machine-id,/var/lib/dbus/machine-id"
I0725 08:54:49.715219 1 factory.go:221] Registration of the docker container factory successfully
I0725 08:54:49.715735 1 factory.go:219] Registration of the podman container factory failed: failed to validate Podman info: response not present: Get "http://d/v1.0.0/info": dial unix /var/run/podman/podman.sock: connect: no such file or directory
I0725 08:54:49.718124 1 factory.go:221] Registration of the containerd container factory successfully
I0725 08:54:49.718147 1 factory.go:221] Registration of the systemd container factory successfully
I0725 08:54:49.718437 1 factory.go:219] Registration of the crio container factory failed: Get "http://%2Fvar%2Frun%2Fcrio%2Fcrio.sock/info": dial unix /var/run/crio/crio.sock: connect: no such file or directory
I0725 08:54:49.719606 1 factory.go:219] Registration of the mesos container factory failed: unable to create mesos agent client: failed to get version
W0725 08:54:49.719707 1 manager.go:306] Could not configure a source for OOM detection, disabling OOM events: open /dev/kmsg: no such file or directory
W0725 08:54:49.727161 1 handler.go:426] Cannot read smaps files for any PID from CONTAINER
W0725 08:54:49.796716 1 handler.go:426] Cannot read smaps files for any PID from CONTAINER
Fun fact: Increasing v=3 will make info.go, container.go, manager.go, factory.go much more verbose. But v=0 has no impact on them.
-- Expected behavior:
v=0 should affect all modules.
vmodule=handler*=0 should affect the handler module
Possible root cause:
handler.go uses klog, not glog.
Metadata
Metadata
Assignees
Labels
No labels