> The hint about non-empty cgroup + gap in PID sequence [1] suggest that
> the parent and child are not the only two processes of the service.
The gap in PIDs can be explained by a lot of processes starting at
that moment. In that particular case:
```
May 09 17:52:47 cb6d1c84f84e systemd[106]:
On Di, 10.05.22 08:44, Yuri Kanivetsky (yuri.kanivet...@gmail.com) wrote:
> The one that produces the messages is 249.11 (that is running in a
> docker container):
>
> https://packages.ubuntu.com/jammy/systemd
>
> The one running on the host is 215-17 (Debian 8).
that's ancient... i figure this
On Mo, 09.05.22 23:43, Yuri Kanivetsky (yuri.kanivet...@gmail.com) 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:
On Do, 05.05.22 04:41, Yuri Kanivetsky (yuri.kanivet...@gmail.com) wrote:
> Hi,
>
> This might be not a systemd issue. But the behavior is weird, and I'm not
> sure.
>
> I'm trying to run GNOME in a docker container. And gnome-keyring
> fails to start:
To my knowledge Docker is not capable of
On Tue, 10 May 2022 at 08:44:27 +0300, Yuri Kanivetsky wrote:
> The one running on the host is 215-17 (Debian 8).
That's very old. As far as most of the Debian project is concerned,
Debian 8 reached EOL in mid 2018. There is a separate Debian LTS team
which picks up security support when the main
The one that produces the messages is 249.11 (that is running in a
docker container):
https://packages.ubuntu.com/jammy/systemd
The one running on the host is 215-17 (Debian 8).
> But it sounds like systemd issue in one specific version you are using.
On hosts with newer Debians the issue
On 09.05.2022 23:43, Yuri Kanivetsky wrote:
> Hi Andrei,
>
> Thanks for the suggestion. It becomes more verbose, but it still seems
> like `systemd` fails to notice that `gnome-keyring` exited:
>
Probably
...
>
> The child exits:
>
> May 09 17:52:47 cb6d1c84f84e
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]:
On 05.05.2022 04:41, Yuri Kanivetsky wrote:
> Hi,
>
> This might be not a systemd issue. But the behavior is weird, and I'm not
> sure.
>
> I'm trying to run GNOME in a docker container. And gnome-keyring fails to
> start:
>
> https://gist.github.com/x-yuri/c3c715ea6355633de4546ae957a66410
>
Hi,
This might be not a systemd issue. But the behavior is weird, and I'm not sure.
I'm trying to run GNOME in a docker container. And gnome-keyring fails to start:
https://gist.github.com/x-yuri/c3c715ea6355633de4546ae957a66410
I added debug statements, and in the log I see:
May 02
10 matches
Mail list logo
