[systemd-devel] is such a 'failed' state?

[lejeczek]

Hi guys.

I have a service (which for some reason, I suspect SELinux, 
does not start at boot) which reports as:

-> $ systemctl status -l lsyncd | cat
● lsyncd.service - Live Syncing (Mirror) Daemon
    Loaded: loaded (/usr/lib/systemd/system/lsyncd.service; 
enabled; vendor preset: disabled)
   Drop-In: /etc/systemd/system/lsyncd.service.d
            └─override.conf
    Active: inactive (dead) since Sun 2021-03-28 15:01:16 
EDT; 8min ago
  Main PID: 922 (code=exited, status=0/SUCCESS)

Mar 28 15:01:16 c8kubernode2.private.pawel systemd[1]: 
Started Live Syncing (Mirror) Daemon.
Mar 28 15:01:16 c8kubernode2.private.pawel lsyncd[922]: 
15:01:16 Normal: --- Startup, daemonizing ---
Mar 28 15:01:16 c8kubernode2.private.pawel lsyncd[922]: 
15:01:16 Normal: --- Startup, daemonizing ---
Mar 28 15:01:16 c8kubernode2.private.pawel lsyncd[981]: 
Normal, --- TERM signal, fading ---
Mar 28 15:01:16 c8kubernode2.private.pawel systemd[1]: 
lsyncd.service: Succeeded.

and the service has:
[Service]
Restart=on-failure
RestartSec=30
TimeoutSec=30

I expected systemd to restart the service but that does not 
happen. Services restarts okey with manual intervention.
Is it because service, even though it's not running, is not 
really in 'failed' state or root cause is something else?

many thanks, L.