How can an existing systemd service become unknown again?

Unix & Linux Asked by Kolja on December 6, 2020

I have a custom system service running on a server, let’s call it xyz.service. It has been running for months without problems and is also enabled to run on reboot (

When I last checked on it however, it was neither running nor known to systemd:

$ systemctl status xyz
Unit xyz.service could not be found.
$ systemctl list-units | grep xyz

The file in /etc/systemd/system and the symlink in /etc/systemd/system/ still exist. After a systemctl daemon-reload, the service is available again and (after starting) running fine.

I can see (via journalctl -u xyz) that the service was stopped yesterday.

What could cause this, and is there a way to find out when that happened?

Add your own answers!

Ask a Question

Get help from others!

© 2024 All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP