I set up NUT on my server to monitor the status of 2 UPS’s connected via USB, an eaton and a cyberpower. Nut fires up fine when I tell systemd to run all the pieces, but when I reboot, they are active but dead. they dont wake up and work until I manually load them again.
Theres no error anywhere. it just wont load itself on boot. why?
You must log in or register to comment.
Its common, it’s called the refractory period. Younger men can sometimes go a couple minutes after a “reboot” but as you get older it takes longer and longer.
ETA: maybe I should read past the topic…
- You need to enable debug logging for NUT
- Run
systemctl --failedand see if you get anything there - Make sure you run the journal back all the way through boot and see if anything during boot time is obvious
- Post your systems units here
fixed it! its a weird fedora thing… https://discussion.fedoraproject.org/t/nut-server-documentation/83708/14
Checked your journal?
sean@hooty:~$ systemctl status nut-driver@printerUPS.service ○ nut-driver@printerUPS.service - Network UPS Tools - device driver for NUT device 'printerUPS' Loaded: loaded (/usr/lib/systemd/system/nut-driver@.service; enabled; preset: disabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf /etc/systemd/system/nut-driver@printerUPS.service.d └─nut-driver-enumerator-generated-checksum.conf, nut-driver-enumerator-generated-devicename.conf, nut-driver-enumerator-genera> /etc/systemd/system/nut-driver@.service.d └─override.conf Active: inactive (dead) Docs: man:upsdrvsvcctl(8) https://www.networkupstools.org/historic/v2.8.4/docs/man/upsdrvsvcctl.html man:ups.conf(5) https://www.networkupstools.org/historic/v2.8.4/docs/man/ups.conf.html man:nut.conf(5) https://www.networkupstools.org/historic/v2.8.4/docs/man/nut.conf.html man:usbhid-ups(8) https://www.networkupstools.org/historic/v2.8.4/docs/man/usbhid-ups.html


