Re: Antw: [EXT] I/O error on "systemctl kill -s HUP rsyslog.service"

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Do, 13.08.20 08:54, Harald Dunkel (harald.dunkel@xxxxxxxxxx) wrote:

> On 8/12/20 2:16 PM, Andrei Borzenkov wrote:
> > 12.08.2020 14:03, Harald Dunkel пишет:
> > > See attachment. Hope this helps
> > > Harri
> >
> >
> > > 1     openat(AT_FDCWD, "/sys/fs/cgroup/unified/system.slice/rsyslog.service/cgroup.procs", O_RDONLY|O_CLOEXEC) = 24
> > > 1     read(24, "0\n1544456\n", 4096)    = 10
> >
> >
> > kernel returns "0" as process number in this cgroup which results in EIO
> > returned by systemd.
>
> Indeed. This is kernel 4.19.132-1, as provided by Debian 10. Upgrading
> to kernel 5.6.14-2~bpo10+1 and lxc 4.0.4 doesn't help, same problem.
>
> And now its getting weird: I found a few ghost services in some LXC
> containers with *just* zeros, e.g. the zabbix-agent:
>
> # cat /sys/fs/cgroup/unified/system.slice/zabbix-agent.service/cgroup.procs
> 0
> 0
> 0
> 0
> 0
> 0
>
> Zabbix-agent isn't even installed in the container. Its installed on
> the host system only.

Is it possible the container and the host run in the very same cgroup
hierarchy?

If that's the case (and it looks like it): this is not
supported. Please file a bug against LXC, it's very clearly broken.

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel