Re: Failed to activate service 'org.freedesktop.systemd1': timed out

[Debraj Manna <subharaj.manna@xxxxxxxxx>]

Thanks Michael for replying and giving me the issue details.

I am trying to understand in what scenarios we may hit this issue. I
checked the issue. It states that "This can happen when the
configuration is changed and reloaded while we are executing a
service.". Can you also please explain what does configuration changed
and reloaded mean?

Does it mean doing some changes in systemd unit file and then
re-loading (via daemon-reload) it while the services are executing or
the services are active and we are trying to disable or do a mask
operation?

On Tue, May 19, 2020 at 1:25 PM Michael Chapman <mike@xxxxxxxxxxxxxxxxx> wrote:
>
> On Mon, 18 May 2020, Debraj Manna wrote:
> > Around the same time I am seeing the below error in syslog
> >
> > May 18 08:49:24 platform3 systemd[1]: Removed slice User Slice of support.
> > May 18 08:49:27 platform3 systemd[1]: Assertion 's->type ==
> > SERVICE_ONESHOT' failed at ../src/core/service.c:1792, function
> > service_enter_start(). Aborting.
> > May 18 08:49:27 platform3 systemd[1]: Caught <ABRT>, dumped core as pid 15839.
> > May 18 08:49:27 platform3 systemd[1]: Freezing execution.
>
> This bug (https://github.com/systemd/systemd/issues/4444) was fixed in
> systemd v236.
>
> See if you can use a newer version of systemd.
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel