9
submitted 5 months ago* (last edited 5 months ago) by Whooping_Seal@sh.itjust.works to c/linux@sh.itjust.works

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

you are viewing a single comment's thread
view the rest of the comments
[-] dustbin@thelemmy.club 2 points 5 months 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

[-] Kerplunk@mastodon.scot 1 points 4 months ago

@dustbin @kaki

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

It is 100% more effective to move to a nosystemd distribution.

this post was submitted on 31 Mar 2026
9 points (100.0% liked)

Linux

5506 readers
3 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 3 years ago
MODERATORS