Closed Gooberpatrol66 closed 2 years ago
I think there may be several issues in play here:
1) Early in the log, it says that "pfsense" hostname is not resolved - but it is later; probably a race between naming service startup and NUT components (maybe you should order the services predictably?) or just "pfsense" registers by DHCP or similar as it boots?
2) upsmon
starts with debug enabled, this keeps it foregrounded (not sure quickly if it also forgoes the split of unprivileged monitoring child process vs root
parent able to shutdown) - so a "Forking" service type is probably not applicable, and "Simple" or some such might be better (assuming systemd kills it by timeout since the child process never appears).
There are several discussions and PRs to separate foreground/background behavior from debug enablement, such as #123, #349 and #683, so this may change in later NUT master
branch iterations and eventually releases.
I figured out this happened because I broke a symlink from /var/run -> /run, so systemd would look for a PID file in a different place than the daemon wrote it. So, this is invalid. My bad.
The systemd service fails even though the output seems to indicate that nut-monitor is communicating successfully with the UPS.
Gentoo Linux
Nut v2.7.4-r7 (installed from distro package)
UPS: Tripplite SU1500RTXLCD2U (controlled by pfsense)
Here's the unit file:
journalctl output: