Linux

5050 readers

18 users here now

Shit, just linux.

Use this community for anything related to linux for now, if it gets too huge maybe there will be some sort of meme/gaming/shitpost spinoff. Currently though… go nuts

founded 2 years ago

MODERATORS

carrot@sh.itjust.works

Can't figure out what systemd service is failing. (sh.itjust.works)

submitted 1 day ago* (last edited 1 day ago) by Whooping_Seal@sh.itjust.works to c/linux@sh.itjust.works

3 comments fedilink hide all child comments

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

top 3 comments

sorted by: hot top controversial new old

[–] dustbin@thelemmy.club 7 points 1 day ago (1 children)

The naming convention looks suspiciously like an autogenerated (dynamic) unit; one typically sees these from /etc/fstab being parsed at boot by systemd-fstab-generator into /run/systemd/.

Try perusing https://www.freedesktop.org/software/systemd/man/latest/systemd.generator.html and /run/systemd/ on your system, see if anything catches your eye...

[–] kaki@sh.itjust.works 3 points 1 day ago (1 children)

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

[–] dustbin@thelemmy.club 2 points 1 day ago

It's probably most effective at this point to add systemd.log_level=debug systemd.log_target=kmsg to the kernel boot options to ferret out what's creating it then go from there