Incus/LXD/LXC: failed to read proc cgroup: unknown container

[tomposmiko]

There is an Incus hypervisor server (LXD or pure LXC would probably produce the same).
There are a bunch of these messages in the syslog:

Jun 19 13:11:54 v103 coroot-node-agent[524089]: W0619 13:11:54.582031  524089 registry.go:323] failed to read proc cgroup: unknown container: /lxc.payload.samba19/system.slice/smbd.service
Jun 19 13:11:54 v103 coroot-node-agent[524089]: W0619 13:11:54.582031  524089 registry.go:323] failed to read proc cgroup: unknown container: /lxc.payload.samba19/system.slice/smbd.service
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.852879  524089 registry.go:348] calculated container id 1767730 ->  ->
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.852950  524089 registry.go:353] "ignoring" cg="" pid=1767730
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.853028  524089 registry.go:348] calculated container id 1767731 ->  ->
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.853046  524089 registry.go:353] "ignoring" cg="" pid=1767731
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.853084  524089 registry.go:348] calculated container id 1767729 ->  ->
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.853094  524089 registry.go:353] "ignoring" cg="" pid=1767729
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.853129  524089 registry.go:348] calculated container id 1767732 ->  ->
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.853139  524089 registry.go:353] "ignoring" cg="" pid=1767732
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.952079  524089 registry.go:348] calculated container id 1767733 ->  ->
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.952145  524089 registry.go:353] "ignoring" cg="" pid=1767733
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.952258  524089 registry.go:348] calculated container id 1767734 ->  ->
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.952283  524089 registry.go:353] "ignoring" cg="" pid=1767734
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.952348  524089 registry.go:348] calculated container id 1767735 ->  ->
Jun 19 13:11:54 v103 coroot-node-agent[524089]: I0619 13:11:54.952368  524089 registry.go:353] "ignoring" cg="" pid=1767735
Jun 19 13:11:55 v103 coroot-node-agent[524089]: I0619 13:11:55.150522  524089 registry.go:348] calculated container id 1767736 ->  ->
Jun 19 13:11:55 v103 coroot-node-agent[524089]: I0619 13:11:55.150586  524089 registry.go:353] "ignoring" cg="" pid=1767736
Jun 19 13:11:57 v103 coroot-node-agent[524089]: W0619 13:11:57.358690  524089 registry.go:323] failed to read proc cgroup: unknown container: /lxc.payload.samba11/system.slice/smbd.service
Jun 19 13:11:57 v103 coroot-node-agent[524089]: W0619 13:11:57.358690  524089 registry.go:323] failed to read proc cgroup: unknown container: /lxc.payload.samba11/system.slice/smbd.service
Jun 19 13:11:57 v103 coroot-node-agent[524089]: W0619 13:11:57.358779  524089 registry.go:323] failed to read proc cgroup: unknown container: /lxc.payload.samba11/system.slice/smbd.service

[def]

@tomposmiko thanks for the report. You'll need to update the agent to v1.25.2 once the build is ready.