On Thu, 28.07.16 13:44, Chip (jeffsch...@gmail.com) wrote: > Ubuntu 16.04 > > With no changes to software or anything, on reboot, systemd *sometimes* will > start dnscrypt-proxy.service while other times just ignores it and it fails > to start. There is no rhyme or reason as to why sometimes it starts and > other times fails to start. > > All files in /etc/systemd/system/multi-user.target.wants look correct. > > I need help troubleshooting this problem. > > Following is a successful journalctl -xru dnscrypt-proxy.service, otherwise > when it fails, it simply shows "no results":
My educated guess is that some cyclic dependency or so caused it to not be considered for activation at boot. To check that, look at the full boot-up process with "journalctl -b", and see if your service is mentioned there, in particularly by PID 1. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel