Thanks Lennart for replying.
If I get you correctly we can hit this issue for both of the below cases
1. Reloading unit file via daemon-reload while the services are executing and
2. Services are active and we try to disable or mask a service without
stopping it?
I apologize if I sound too
On Di, 19.05.20 20:47, Debraj Manna (subharaj.ma...@gmail.com) wrote:
> 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
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
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
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
Hi
I am using systemd 229 on Ubuntu 16.04.6.
ubuntu@platform1:~$ systemctl --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS
+KMOD -IDN
But sometimes when I am trying to mask a service. I am
