[systemd-devel] Failed to add PIDs to scope's control group: No such process
Hello, All! 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? # cat /etc/redhat-release Rocky Linux release 8.5 (Green Obsidian) # 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-logind[2981]: New session 14289 of user root. Feb 3 18:14:28 server systemd[2460863]: Starting D-Bus User Message Bus Socket. Feb 3 18:14:28 server systemd[2460863]: Reached target Timers. Feb 3 18:14:28 server systemd[2460863]: Reached target Paths. Feb 3 18:14:28 server systemd[2460863]: Listening on D-Bus User Message Bus Socket. Feb 3 18:14:28 server systemd[2460863]: Reached target Sockets. Feb 3 18:14:28 server systemd[2460863]: Reached target Basic System. Feb 3 18:14:28 server systemd[2460863]: Reached target Default. Feb 3 18:14:28 server systemd[2460863]: Startup finished in 2.526s. 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'. Feb 3 18:14:28 server systemd[1]: Failed to start Session 14287 of user root. Feb 3 18:14:28 server systemd[1]: Started Session 14289 of user root. Feb 3 18:14:28 server systemd-logind[2981]: Session 14287 logged out. Waiting for processes to exit. Feb 3 18:14:28 server systemd-logind[2981]: Removed session 14287. -- Best regards, Gena
Re: [systemd-devel] Configuring wakeup-online at runtime with networkctl
On Thu, Feb 3, 2022 at 9:45 AM Francis Moreau wrote: > Hello, > > I would like to know if it's possible to configure an interface at > runtime to enable wol without rebooting my machine. > > I tried to create a link file that has WakeOnLan=magic and did > 'networkctl reconfigure ens0' but it doesn't work. > I don't think networkd ever looks at .link files – they are generally processed only through udev rules, when the interface is created. Try `udevadm trigger [-c add] /sys/class/net/ens0` though. If that doesn't help, do it manually via `ethtool -s wol g ens0`. Also is it possible to display the status of wakeup online with > 'networkctl status' ? > I'd say open a RFE on GitHub issues, although personally I think `networkctl status` is already a bit overloaded... -- Mantas Mikulėnas
