You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting spammed (and see issues on getting spammed with) error binary.Read: invalid type int32, i've been looking in the entire codebase for this single type, since i know that it has caused this problem, and this is the only instance in the netlink path.
For reference, i'm tracking down why enabling --enable_load_reader=true and then deploying cadvisor as a daemonset creates these log messages.
I've seen #3242 also refer to this, in their case it was simply disabling the load reader that worked for them, but I'd like to have the metrics that're associated with it.
The text was updated successfully, but these errors were encountered:
I am having the same issue, I am setting --enable_load_reader=true across different hosts, in most of them running Ubuntu I have no issues and I've been able to get the CPU load. But in two Debian hosts I get error binary.Read: invalid type int32 no data.
I've checked the structure of /sys/fs/cgroup in both types of hosts and coincidentally the Ubuntu ones have the cgroup v1 directory structure, but the Debian ones that are failing have the cgroup v2 structure.
The piece of code you linked corresponds to Netlink error handling, so I suspect this is hiding another error, maybe if the original error is fixed this entire piece of code can be avoided.
By the way, my intuition tells me this TODO is related, it is signed by @rjnagal
This has taken me ages to track down, but you probably have a binary.Read bug right here:
cadvisor/utils/cpuload/netlink/netlink.go
Line 210 in 2129e1c
I'm getting spammed (and see issues on getting spammed with)
error binary.Read: invalid type int32
, i've been looking in the entire codebase for this single type, since i know that it has caused this problem, and this is the only instance in the netlink path.For reference, i'm tracking down why enabling
--enable_load_reader=true
and then deploying cadvisor as a daemonset creates these log messages.I've seen #3242 also refer to this, in their case it was simply disabling the load reader that worked for them, but I'd like to have the metrics that're associated with it.
The text was updated successfully, but these errors were encountered: