[systemd-devel] Antw: [EXT] I/O error on "systemctl kill -s HUP rsyslog.service"
Harald Dunkel
harald.dunkel at aixigo.com
Thu Aug 13 06:54:18 UTC 2020
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.
I will check on the LXC mailing list. Maybe somebody is able to
reproduce this problem.
I highly appreciate your support on this
Harri
More information about the systemd-devel
mailing list