Comment on Can't figure out what systemd service is failing.
dustbin@thelemmy.club 3 weeks ago
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 www.freedesktop.org/…/systemd.generator.html and /run/systemd/ on your system, see if anything catches your eye…
kaki@sh.itjust.works 3 weeks ago
OP mentionned containers, and Podman/Quadlet generates such services for health-checking a container service, so it might be that.
Whooping_Seal@sh.itjust.works 2 weeks ago
I havent had the change to reboot with the parameters mentioned below, but I think it most definitely is the health check (which I have manually configured for everything but syncthing).
dustbin@thelemmy.club 3 weeks ago
It’s probably most effective at this point to add
systemd.log_level=debug systemd.log_target=kmsgto the kernel boot options to ferret out what’s creating it then go from thereKerplunk@mastodon.scot 1 week 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.