[Nut-upsuser] NUT 2.8.1 (source build) Pi OS bookworm 32 bit - nut-monitor trying to connect to UPS - Connection Refused
Dan Grostick
danpower2023 at outlook.com
Fri Mar 8 15:53:36 GMT 2024
Charles, thanks for the hint. It got me thinking about 'listening on'. Further investigation revealed that my hosts file was fubar. Correcting it resolved the issue.
Dan
________________________________
From: Charles Lepple <clepple at gmail.com>
Sent: Friday, March 8, 2024 9:04 AM
To: Dan Grostick <danpower2023 at outlook.com>
Cc: nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org>
Subject: Re: [Nut-upsuser] NUT 2.8.1 (source build) Pi OS bookworm 32 bit - nut-monitor trying to connect to UPS - Connection Refused
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240308/24f4114a/attachment.htm>
More information about the Nut-upsuser
mailing list