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).
Comment on Can't figure out what systemd service is failing.
kaki@sh.itjust.works 1 month agoOP mentionned containers, and Podman/Quadlet generates such services for health-checking a container service, so it might be that.
Whooping_Seal@sh.itjust.works 5 weeks ago
dustbin@thelemmy.club 1 month 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 5 weeks 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.