Nut upsuser - Mar 2024 - NUT 2.8.1 (source build) Pi OS bookworm 32 bit - nut-monitor trying to connect to UPS - Connection Refused

I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit (Debian
12) with success.

When I take that same configuration to a PI 3B running bookworm 32 bit, compile
from source, use the same files from /etc/nut, I get a 'nut-monitor  ups at
localhost  Connection refused.
usbhid-ups and dummy-ups are running at the time.

What should I be looking for?

Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240308/8535cf65/attachment.htm>
-------------- next part --------------
Mar 08 07:48:59 WiringCloset usbhid-ups[6529]: Startup successful
Mar 08 07:48:59 WiringCloset usbhid-ups[6529]: upsnotify: failed to notify about
state 2: no notification tech defined, will not spam more about it
Mar 08 07:49:00 WiringCloset dummy-ups[6531]: Startup successful
Mar 08 07:49:00 WiringCloset dummy-ups[6531]: upsnotify: failed to notify about
state 2: no notification tech defined, will not spam more about it
Mar 08 07:49:05 WiringCloset systemd[1]: Starting nut-server.service - Network
UPS Tools - power devices information server...
Mar 08 07:49:05 WiringCloset systemd[1]: Started nut-server.service - Network
UPS Tools - power devices information server.
Mar 08 07:49:05 WiringCloset nut-server[6536]: fopen /var/state/ups/upsd.pid: No
such file or directory
Mar 08 07:49:05 WiringCloset nut-server[6536]: Could not find PID file
'/var/state/ups/upsd.pid' to see if previous upsd instance is already
running!
Mar 08 07:49:05 WiringCloset nut-server[6536]: /etc/nut/upsd.conf is world
readable
Mar 08 07:49:05 WiringCloset upsd[6536]: /etc/nut/upsd.conf is world readable
Mar 08 07:49:05 WiringCloset nut-server[6536]: listening on 192.168.123.49 port
3493
Mar 08 07:49:05 WiringCloset nut-server[6536]: Connected to UPS [heartbeat]:
dummy-ups-heartbeat
Mar 08 07:49:05 WiringCloset nut-server[6536]: Connected to UPS [ups]:
usbhid-ups-ups
Mar 08 07:49:05 WiringCloset nut-server[6536]: Found 2 UPS defined in ups.conf
Mar 08 07:49:05 WiringCloset upsd[6536]: listening on 192.168.123.49 port 3493
Mar 08 07:49:05 WiringCloset upsd[6536]: Connected to UPS [heartbeat]:
dummy-ups-heartbeat
Mar 08 07:49:05 WiringCloset nut-server[6536]: /etc/nut/upsd.users is world
readable
Mar 08 07:49:05 WiringCloset upsd[6536]: Connected to UPS [ups]: usbhid-ups-ups
Mar 08 07:49:05 WiringCloset upsd[6536]: Found 2 UPS defined in ups.conf
Mar 08 07:49:05 WiringCloset dummy-ups[6531]: sock_connect: enabling
asynchronous mode (auto)
Mar 08 07:49:05 WiringCloset nut-server[6536]: Running as foreground process,
not saving a PID file
Mar 08 07:49:05 WiringCloset nut-server[6536]: upsnotify: failed to notify about
state 2: no notification tech defined, will not spam more about it
Mar 08 07:49:05 WiringCloset usbhid-ups[6529]: sock_connect: enabling
asynchronous mode (auto)
Mar 08 07:49:05 WiringCloset upsd[6536]: /etc/nut/upsd.users is world readable
Mar 08 07:49:05 WiringCloset upsd[6536]: Running as foreground process, not
saving a PID file
Mar 08 07:49:05 WiringCloset upsd[6536]: upsnotify: failed to notify about state
2: no notification tech defined, will not spam more about it
Mar 08 07:49:08 WiringCloset systemd[1]: Starting nut-monitor.service - Network
UPS Tools - power device monitor and shutdown controller...
Mar 08 07:49:08 WiringCloset systemd[1]: Started nut-monitor.service - Network
UPS Tools - power device monitor and shutdown controller.
Mar 08 07:49:08 WiringCloset nut-monitor[6541]:    0.000001        fopen
/run/upsmon.pid: No such file or directory
Mar 08 07:49:08 WiringCloset nut-monitor[6541]:    0.002027        Could not
find PID file to see if previous upsmon instance is already running!
Mar 08 07:49:08 WiringCloset nut-monitor[6541]:    0.007575        UPS: ups at
localhost (primary) (power value 1)
Mar 08 07:49:08 WiringCloset nut-monitor[6541]:    0.007687        UPS:
heartbeat at localhost (monitoring only)
Mar 08 07:49:08 WiringCloset nut-monitor[6541]:    0.007752        Using power
down flag file /etc/killpower
Mar 08 07:49:08 WiringCloset nut-monitor[6541]:    0.007984        [D1] debug
level is '2'
Mar 08 07:49:08 WiringCloset nut-monitor[6542]:    0.010116        [D1] Saving
PID 6542 into /run/upsmon.pid
Mar 08 07:49:08 WiringCloset nut-monitor[6542]:    0.011032        [D1]
Succeeded to become_user(root): now UID=0 GID=0
Mar 08 07:49:08 WiringCloset nut-monitor[6542]: upscli_init called but SSL
wasn't compiled in
Mar 08 07:49:08 WiringCloset nut-monitor[6542]:    0.011286        upsnotify:
failed to notify about state 2: no notification tech defined, will not spam more
about it
Mar 08 07:49:08 WiringCloset nut-monitor[6542]:    0.011311        [D1] Trying
to connect to UPS [ups at localhost]
Mar 08 07:49:09 WiringCloset nut-monitor[6542]:    0.319633        UPS [ups at
localhost]: connect failed: Connection failure: Connection refused
Mar 08 07:49:09 WiringCloset nut-monitor[6542]:    0.319693        [D2]
do_notify: ntype 0x0005 (COMMBAD)
Mar 08 07:49:09 WiringCloset nut-monitor[6542]:    0.319707        commbad
Mar 08 07:49:09 WiringCloset nut-monitor[6542]:    0.320094        [D1] Trying
to connect to UPS [heartbeat at localhost]
Mar 08 07:49:09 WiringCloset nut-monitor[6542]:    0.328471        UPS
[heartbeat at localhost]: connect failed: Connection failure: Connection refused
Mar 08 07:49:09 WiringCloset nut-monitor[6542]:    0.328545        [D2]
do_notify: ntype 0x0005 (COMMBAD)
Mar 08 07:49:09 WiringCloset nut-monitor[6542]:    0.328558        commbad
Mar 08 07:49:09 WiringCloset nut-monitor[6546]: Network UPS Tools upsmon 2.8.1
Mar 08 07:49:09 WiringCloset nut-monitor[6556]: Error: Connection failure:
Connection refused
Mar 08 07:49:09 WiringCloset nut-monitor[6557]: Error: Connection failure:
Connection refused
Mar 08 07:49:09 WiringCloset upssched-cmd:[6558]: upssched-cmd running 
(2024-03-08_07.49.09)
Mar 08 07:49:09 WiringCloset upssched-cmd:[6559]: commbad

On Mar 8, 2024, at 8:22?AM, Dan Grostick via Nut-upsuser <nut-upsuser at
alioth-lists.debian.net> wrote:
> 
> I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit
(Debian 12) with success.
> 
> When I take that same configuration to a PI 3B running bookworm 32 bit,
compile from source, use the same files from /etc/nut, I get a 'nut-monitor 
ups at localhost  Connection refused.
> usbhid-ups and dummy-ups are running at the time.
> 
> What should I be looking for?
> 
> Dan
If you only see:

nut-server[6536]: listening on 192.168.x.y

and no equivalent line for 127.0.0.1, then monitoring ups-name at localhost will
likely not work. You may want to listen on the wildcard 0.0.0.0 address instead
of a specific address (helps if the IP is dynamic), or just add "LISTEN
127.0.0.1".

-- 
Charles Lepple
clepple at gmail