system service remains active if daemon fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cachefilesd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Attempting to start the cachefiles service when /etc/default/
systemctl start cachefilesd.service
Leaves service "active" even though the daemon fails:
systemctl status cachefilesd.service
● cachefilesd.service - LSB: CacheFiles daemon
Loaded: loaded (/etc/init.
Active: active (exited) since Tue 2021-02-23 13:24:57 EST; 1min 15s ago
Docs: man:systemd-
Process: 26346 ExecStop=
Process: 26360 ExecStart=
Feb 23 13:24:57 gerarddaily systemd[1]: Starting LSB: CacheFiles daemon...
Feb 23 13:24:57 gerarddaily cachefilesd[26360]: * cachefilesd disabled, please set RUN=yes in /etc/default/
Feb 23 13:24:57 gerarddaily systemd[1]: Started LSB: CacheFiles daemon.
Feb 23 13:25:53 gerarddaily cachefilesd[26273]: Daemon Terminated
This leads systemd to ignore future "start" commands even after then problem is fixed. Systemd services typically report a failure, not "Success" when their daemon fails to start.
Work around: manually stopping and then starting service, or systemctl restart cachefilesd restarts the service.
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
apt-cache policy cachefilesd
cachefilesd:
Installed: 0.10.10-
Candidate: 0.10.10-
Version table:
*** 0.10.10-
500 http://
100 /var/lib/
0.10.10-0.1 500
500 http://