Home > computers > linux > systemd | About

Systemd says service is active, but it is not running

[09:32] <grawity> you can check the system logs and/or `systemctl status servicename`
[09:32] <grawity> (make sure to run it as root so that it could print the log messages as well)
[09:33] <ychaouche> grawity: it says : Active:active(exited) since <date>
[09:33] <ychaouche> but I can't find it with pgrep
[09:33] <ychaouche> So active doesn't mean it's running, right ?
[09:34] <grawity> it means systemd thinks it should be active
[09:34] <grawity> but,
[09:34] <grawity> IIRC, Debian had to set RemainAfterExit=yes in their auto-generated .services
[09:34] <grawity> because *some* odd initscripts wouldn't work otherwise
[09:35] <grawity> so, well
[09:35] <grawity> my first recommendation is to rewrite it entirely as a native systemd .service
[09:36] <grawity> from experience, this usually takes a lot less time than actually making init.d work



contact : @ychaouche yacinechaouche at yahoocom


QR Code
QR Code Systemd says service is active, but it is not running (generated for current page)