Hi Gabriel, thanks for getting back to me - the timing was good, because the issue has just recurred on my system.
You are of course correct in what _should_ have happened based on the contents of the unit file. I just jumped to the wrong conclusion based on the error message, and that my redundant change seemed to have worked at the time. My system (this is at home) is on a Xen VM (x86_64), all Debian 10, which should be up to date on stable. I am not running slave mode. smokeping is 2.7.3-2 systemd is 241-7~deb10u3 I get a problem like this about every second reboot, and it is not always smokeping. I am beginning to suspect something wrong with the systemd sequencing. The most recent time I booted: 1. smokeping said /run/smokeping did not exist. 2. bind9 was running, however any requests for external domains timed out. This would have caused problems for smokeping, except that it died before getting that far. 3. another USB data logger could not find its device, but lsusb could. (not sure if udev missed something) I was able to simply "systemctl restart" each of smokeping and bind9 and they worked. The only thing I can think that could relate to some of these is that the network config is still based on the old ifup/down style. I know, from the occasional problem starting my openvpn server at boot, that the "after=network-online" does nothing and the openvpn server sometimes fails to bind to a specific address that has yet to be created. I can't say for sure if that was only on Debian 9 or on 10 also. And I can't see how that would crash smokeping. So, in summary, I don't think my issue is really a smokeping problem, it is just the poor victim. Cheers, Cameron.
