[Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

Charles Lepple clepple at gmail.com
Thu Oct 22 01:57:53 BST 2020

On Oct 21, 2020, at 3:27 PM, Robert Stocker <kneadtoknow at gmail.com> wrote:
> Operating System:	 Raspbian GNU/Linux 10 (buster)
> Kernel name & release:	 Linux 5.4.51-v7l+
> Kernel version:		 #1333 SMP Mon Aug 10 16:51:40 BST 2020
> exact NUT version:
> Network UPS Tools 2.7.3, according to the last line of man ups

Hmm, either that's a typo, or something didn't get rebuilt correctly. The debug output shows that the package is based on NUT 2.7.4.

For Raspbian (Debian) packages, the canonical version number (that also specifies how many patch releases have been built by the packagers) is shown by e.g. "dpkg -l nut-server"

That said, I don't think this is version-specific (but we do appreciate the info). See below.
> NUT installation method: from source tarball, package or Subversion,
> installed from package with apt-get install, using a scripted install from the Raspberry Pi forums (found here: https://www.raspberrypi.org/forums/viewtopic.php?t=240651&p=1508882#p1508882 <https://www.raspberrypi.org/forums/viewtopic.php?t=240651&p=1508882#p1508882>)
> exact device name and related information (manufacturing date, web pointers, …)
> lsusb reports: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
> Actual model number is CST135LXU according to the device's labeling. Here's the web page: https://www.cyberpowersystems.com/product/ups/battery-backup/cst135xlu/ <https://www.cyberpowersystems.com/product/ups/battery-backup/cst135xlu/>
> complete problem description, with any relevant traces, like system log excerpts, and driver debug output. You can obtain the latter using the following command, as root and after having stopped NUT:
> /path/to/driver -DD -a <upsname>
> After installing and rebooting, running ups-info returns:
> Unable to retrieve UPS information
> All attempts to use commands like upsc, upscmd, upsrw result in:
> Error: Connection failure: Connection refused
Parallel init systems like systemd have broken a lot of the assumptions about what is running at any given time, and we're always playing catch-up. Distributions should be starting NUT after the network interfaces are fully up. However, that doesn't always seem to be the case, and that script includes the following:

  cat <<EOF >> /etc/nut/upsd.conf


Unless you have multiple network interfaces, both the LISTEN addresses should be replaced with a single "LISTEN 3493". Even if you have multiple network interfaces, firewall rules are probably a better place to exclude one or more of the interfaces.

Note also that the CyberPower UPSes have a number of mostly cosmetic errors in the output: https://github.com/networkupstools/nut/issues?q=is%3Aissue+is%3Aopen+label%3A%22CyberPower+%28CPS%29%22 <https://github.com/networkupstools/nut/issues?q=is:issue+is:open+label:%22CyberPower+(CPS)%22>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20201021/b76fd0cb/attachment.html>

More information about the Nut-upsuser mailing list