[systemd-devel] Failed to add PIDs to scope's control group: No such process
Gena Makhomed
gmm at csdoc.com
Mon Feb 7 14:10:32 UTC 2022
On 03.02.2022 18:39, Gena Makhomed wrote:
> Periodically I see in /var/log/messages error message about
>
> Failed to add PIDs to scope's control group: No such process
> Failed with result 'resources'.
>
> How I can resolve or workaround this error?
>
> # rpm -q systemd
> systemd-239-51.el8_5.3.x86_64
>
> # cat /var/log/messages
> Feb 3 18:13:36 server systemd-logind[2981]: New session 14287 of user
> root.
> Feb 3 18:14:26 server systemd[1]: Started User runtime directory
> /run/user/0.
> Feb 3 18:14:26 server systemd[1]: Starting User Manager for UID 0...
> Feb 3 18:14:28 server systemd[1]: Started User Manager for UID 0.
> Feb 3 18:14:28 server systemd[1]: session-14287.scope: Failed to add
> PIDs to scope's control group: No such process
> Feb 3 18:14:28 server systemd[1]: session-14287.scope: Failed with
> result 'resources'.
I found workaround for this issue:
# loginctl show-user root | grep Linger
Linger=no
# loginctl enable-linger root
# loginctl show-user root | grep Linger
Linger=yes
After enabling linger - no more such errors in /var/log/messages
--
Best regards,
Gena
More information about the systemd-devel
mailing list