Re: systemd tries to terminate a process that seems to have exited

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Mo, 09.05.22 23:43, Yuri Kanivetsky (yuri.kanivetsky@xxxxxxxxx) wrote:

> Hi Andrei,
>
> Thanks for the suggestion. It becomes more verbose, but it still seems
> like `systemd` fails to notice that `gnome-keyring` exited:
>
>     May 09 17:52:47 cb6d1c84f84e systemd[106]: gnome-keyring.service:
> Passing 0 fds to service
>     May 09 17:52:47 cb6d1c84f84e systemd[106]: gnome-keyring.service:
> About to execute /usr/local/bin/gnome-keyring-daemon --start
> --components pkcs11,secrets
>     May 09 17:52:47 cb6d1c84f84e systemd[106]: gnome-keyring.service:
> Forked /usr/local/bin/gnome-keyring-daemon as 310
>     May 09 17:52:47 cb6d1c84f84e systemd[106]: gnome-keyring.service:
> Changed dead -> start
>     May 09 17:52:47 cb6d1c84f84e systemd[106]: Starting Start
> gnome-keyring for the Secrets Service, and PKCS #11...
>     May 09 17:52:47 cb6d1c84f84e systemd[310]: Skipping PR_SET_MM, as
> we don't have privileges.
>     May 09 17:52:47 cb6d1c84f84e systemd[310]: gnome-keyring.service:
> Executing: /usr/local/bin/gnome-keyring-daemon --start --components
> pkcs11,secrets

My educated guess: you are running in cgroupsv1 mode. cgroup empty
notifications do not work reliably in containers on cgroupsv1.

Use cgroupsv2.

(but i think docker doesn't support that)

Lennart

--
Lennart Poettering, Berlin