• Services
• Club UPS Monitoring

We use NUT to communicate and get status information from our UPSes. We also try to run upsmon on the machines that are plugged into a UPS, so that they can cleanly shutdown in the event of an extended power outage.

Topology

This information was updated as of 2022-05-07.

Hosts in italics have not had NUT fully configured.

Setup

The cclub-hardware-configuration package will install the NUT packages required to monitor UPSes. However, monitoring is not automatically configured—this needs to be done manually, as the exact circumstances will depend on the particular machine.

Hosts that are directly connected to the UPS via USB/serial will run the NUT server as well as the NUT monitor. Hosts that are not directly connected will only run the NUT monitor and learn of UPS status by connecting to the server on a remote host.

Set up the NUT Server (upsd)

1. Add the nut user to the dialout group. This is needed so that the UPS driver process can open the serial port device and to communicate with the UPS.

   adduser nut dialout

2. Define the UPS in /etc/nut/ups.conf. E.g., to define a UPS named dilithium:

   [dilithium]
           driver = apcsmart
           port = /dev/ttyUSB0
           desc = "Lower APC Smart-UPS 1337 in rack 9"

3. Enable NUT in its main "environment" file, /etc/nut/nut.conf. Change the MODE variable to netserver.

4. Enable and start upsd.

   systemctl enable nut-server.service # assuming the host is running systemd
   service nut-server start

5. Verify NUT is successfully communicating with the UPS.

   upsc «upsname»@localhost

Set up the NUT Monitor (upsmon)

1. Add a MONITOR line to /etc/nut/upsmon.conf. It can take one two forms depending on whether the UPS monitoring interfaces is directly connected to the machine. For a directly connected machine (i.e., one that is also running upsd), this would look like:

   MONITOR «upsname»@localhost 1 localmon «password» primary

   For a machine contacting a remote upsd:

   MONITOR «upsname»@«remotehost» 1 remotemon «password» secondary

   The passwords for the localmon and remotemon users are available in /etc/nut/upsd.users on the directly connected machine.

2. Enable NUT in its main "environment" file, /etc/nut/nut.conf, if you did not already do so because the host is also running the NUT server. Change the MODE variable from none to netclient.

3. Enable and start upsmon.

   systemctl enable nut-monitor.service # assuming the host is running systemd
   service nut-monitor start

4. Check /var/log/daemon.log for a message indicating that upsmon was able to successfully connect to the UPS.
   You can also check that the server sees the client is connected by running

   upsc -c «upsname»@«upshost»

   And verifying that the IP address for the machine you are working on is in the list.

Other Notes

Configuration lives in /etc/nut.

• nut.conf—configuration type/environment file; specifies the proper MODE (none, standalone, netserver, or netclient)

• ups.conf—specifies the UPS name, driver (e.g., apcsmart), serial port (e.g., /dev/ttyUSB0), and a textual description

• upsd.conf—specifies configuration for upsd, the main NUT daemon

• upsd.users—user names, passwords, and privileges for access to upsd

• upsmon.conf—specifies which UPSes need to be monitored; gives information so upsmon can connect to some upsd

Some aspects of configuration changed in NUT 2.0 (ships with wheezy and newer). Namely:

• IP-based access control (via ACL in upsd.conf and allowfrom in upsd.users) was removed; we've set up firewall rules instead.

• The UPS driver runs as the NUT user. Easiest way to give him access to the appropriate device is to add the nut user to the dialout group.

Another thing to note, is that wheezy appears to install brltty for some reason or another. It is EVIL and disconnects FTDI devices thinking they're braille terminals. You need to remove the "brltty" package in order to use the serial converters we bought for UPS monitoring.

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 primary will wait for all of the secondaries to shut down, and then it will shut itself down, and power off the UPS.

CategoryServices CategoryClubServices