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

[Michael Biebl <mbiebl@xxxxxxxxx>]

Am Do., 13. Aug. 2020 um 09:05 Uhr schrieb Andrei Borzenkov
<arvidjaar@xxxxxxxxx>:
>
> 13.08.2020 09:54, Harald Dunkel пишет:
> > 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.
> >
>
> systemd should really clearly log this (invalid PID and and in which
> cgroup it was). Returning generic error message without any indication
> what caused this error is not useful at all.

I agree. Could you file a github issue for this?
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel