| Deletions are marked like this. | Additions are marked like this. |
| Line 16: | Line 16: |
|
Also one important thing to remember, is that you need a nut user. If you forget, you get the helpful error message "getpwnam(nut): Success" (at least in the sarge version). {{{ nut:x:50:104::/var/lib/nut:/bin/false }}} |
We use NUT. We are monitoring our UPS through the serial port on gallium. We also run upsmon on the machines that are plugged into the UPS.
Configuration
The NUT configuration files live in /etc/nut.
On gallium
- ups.conf - specifies the UPS name (upsium), driver (apcsmart), and serial port (/dev/ttyS1)
- upsd.conf - specifies access controls to upsd, the main NUT daemon; only allow club hosts to monitor the UPS
- upsd.users - user names, passwords, and privileges for access to upsd
- upsmon.conf - specifies that gallium is the master for monitoring; gives information so upsmon can connect to upsd
In /etc/default/nut, specify START_UPSD=yes and START_UPSMON=yes.
Also one important thing to remember, is that you need a nut user. If you forget, you get the helpful error message "getpwnam(nut): Success" (at least in the sarge version).
nut:x:50:104::/var/lib/nut:/bin/false
On others
- upsmon.conf - specifies that the upsd on gallium should be monitored; gives information so upsmon can connect to the upsd on gallium
In /etc/default/nut, specify START_UPSMON=yes.
How It Handles Issues
TODO: kbare - verify this is true.
When the battery level of the UPS becomes critical, the upsmon processes will notice, and initiate a system shutdown. The master will wait for all of the slaves to shut down, and then it will shut itsefl down, and power off the UPS.