Setting up nut-client on a RPi 3B+ and a RPi 4B.
admin@nut-clientns1080:~ $ upsc nut-clientns1080@localhost
Error: Connection failure: Connection refused
admin@nut-clientns1080:~ $ upsc nut-server...@192.168.xxx.xxx
Init SSL without certificate database
battery.charge: 100
battery.charge.low: 10
##############################
####### snipped for brevity #######
##############################
ups.model: Back-UPS ES 550
ups.productid: 0002
ups.serial: 3B0743X46110
ups.status: OL
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d
admin@nut-clientns1080:~ $ sudo systemctl status nut-client
● nut-monitor.service - Network UPS Tools - power device monitor and
shutdown controller
Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled;
vendor preset: enabled)
Active: active (running) since Mon 2023-09-25 08:25:22 EDT; 23h ago
Process: 899 ExecStart=/sbin/upsmon (code=exited, status=0/SUCCESS)
Main PID: 901 (upsmon)
Tasks: 2 (limit: 1599)
CPU: 9.925s
CGroup: /system.slice/nut-monitor.service
├─900 /lib/nut/upsmon
└─901 /lib/nut/upsmon
Sep 25 08:25:22 nut-clientns1080 systemd[1]: Starting Network UPS Tools -
power device monitor and shutdown controller...
Sep 25 08:25:22 nut-clientns1080 upsmon[899]: fopen /run/nut/upsmon.pid: No
such file or directory
Sep 25 08:25:22 nut-clientns1080 upsmon[899]: UPS:
nut-server...@192.168.xxx.xxx (slave) (power value 1)
Sep 25 08:25:22 nut-clientns1080 upsmon[899]: Using power down flag file
/etc/killpower
Sep 25 08:25:22 nut-clientns1080 upsmon[900]: Startup successful
Sep 25 08:25:22 nut-clientns1080 systemd[1]: nut-monitor.service: Can't
open PID file /run/nut/upsmon.pid (yet?) after start: Operation not
permitted
Sep 25 08:25:22 nut-clientns1080 systemd[1]: nut-monitor.service:
Supervising process 901 which is not our child. We'll most likely not
notice when it exits.
Sep 25 08:25:22 nut-clientns1080 upsmon[901]: Init SSL without certificate
database
Sep 25 08:25:22 nut-clientns1080 systemd[1]: Started Network UPS Tools -
power device monitor and shutdown controller.
Sep 25 08:25:22 nut-clientns1080 upsmon[901]: Login on UPS
[nut-server...@192.168.xxx.xxx] failed - got [ERR ACCESS-DENIED]
Output of /var/log/syslog
Sep 26 07:51:41 nut-clientns1080 upsmon[901]: Signal 15: exiting
Sep 26 07:51:41 nut-clientns1080 systemd[1]: Stopping Network UPS Tools -
power device monitor and shutdown controller...
Sep 26 07:51:41 nut-clientns1080 systemd[1]: nut-monitor.service: Succeeded.
Sep 26 07:51:41 nut-clientns1080 systemd[1]: Stopped Network UPS Tools -
power device monitor and shutdown controller.
Sep 26 07:51:41 nut-clientns1080 systemd[1]: nut-monitor.service: Consumed
10.030s CPU time.
Sep 26 07:51:41 nut-clientns1080 systemd[1]: Starting Network UPS Tools -
power device monitor and shutdown controller...
Sep 26 07:51:41 nut-clientns1080 upsmon[12471]: fopen /run/nut/upsmon.pid:
No such file or directory
Sep 26 07:51:41 nut-clientns1080 upsmon[12471]: UPS:
nut-server...@192.168.xxx.xxx (slave) (power value 1)
Sep 26 07:51:41 nut-clientns1080 upsmon[12471]: Using power down flag file
/etc/killpower
Sep 26 07:51:41 nut-clientns1080 upsmon[12473]: Startup successful
Sep 26 07:51:41 nut-clientns1080 systemd[1]: nut-monitor.service: Can't
open PID file /run/nut/upsmon.pid (yet?) after start: Operation not
permitted
Sep 26 07:51:41 nut-clientns1080 systemd[1]: nut-monitor.service:
Supervising process 12474 which is not our child. We'll most likely not
notice when it exits.
Sep 26 07:51:41 nut-clientns1080 systemd[1]: Started Network UPS Tools -
power device monitor and shutdown controller.
Sep 26 07:51:41 nut-clientns1080 upsmon[12474]: Init SSL without
certificate database
Sep 26 07:51:41 nut-clientns1080 upsmon[12474]: Login on UPS
[nut-server...@192.168.xxx.xxx] failed - got [ERR ACCESS-DENIED]
Hardware in use:
RPi 4B configuration:
admin@nut-clientns1080:~ $ pinout
Revision : b03112
SoC : BCM2711
RAM : 2GB
Storage : MicroSD
RPi 3B+ configuration:
admin@nut-clientes550:~ $ pinout
Revision : a020d3
SoC : BCM2837
RAM : 1GB
Storage : MicroSD
Both RPi's are running Raspbian 11 Lite 64-bit OS with current version of
NUT.
admin@nut-client550:~ $ sudo apt list nut
Listing... Done
nut/oldstable,oldstable,now 2.7.4-13 all [installed]
While searching web for a solution I found Debian bug #962800.
Is there a workaround available?
--
---
*Bob Wooden*
