Hello everyone,

I recently set up a drop-in systemd unit file that adds an "on failure" command to all user-level services on a home server. Specifically the on failure command sends a notification to ntfy.sh detailing the service that has failed. E.g. if my miniflux container fails, it will send a notification such as Le service miniflux.service a échoué. Vérifier : journalctl --user -u miniflux.service

However, particularly on server startup, I have been getting some weird failure notifications for services I cannot find.

Any ideas on what I can do to troubleshoot this? An example is provided bellow.

Title: ⚠️ ❌ 303a3d11aa5781aaca14faa1e36fbe4465466f74e49821fee252d01227f8fdfb-73342cf5eacdadbd.service a échoué

Body: Le service 303a3d11aa5781aaca14faa1e36fbe4465466f74e49821fee252d01227f8fdfb-73342cf5eacdadbd.service a échoué. Vérifier : journalctl --user -u 303a3d11aa5781aaca14faa1e36fbe4465466f74e49821fee252d01227f8fdfb-73342cf5eacdadbd.service

all 6 comments

sorted by: hot top controversial new old
[+] 5 points 7 months ago (4 children)
  • [–] 3 points 7 months ago (3 children)

    OP mentionned containers, and Podman/Quadlet generates such services for health-checking a container service, so it might be that.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 0 points 6 months ago

    @Whooping_Seal Can't figure out what systemd service is failing.over 2 million lines of slop coding, 2000 plus bugs open.systemd is a fail

  • source