Nut upsuser - Jan 2022 - NUT Client Not Working, Server OK

[please keep the list CC'd - probably easiest via Reply-All]

On Jan 28, 2022, at 10:20 AM, William Cole wrote:
> However, when executing sudo service nut-client on the Client PC, still
getting a Connection refused message:
> 
> upsmon[491] UPS [APCES750Client at 192.168.1.101]:connect failed:
Connection failure: Connection refused
> (repeated 9 times)
"Connection refused" is a standard network error message that says
that either a firewall is blocking the port, or no daemon is currently listening
on that port. Since both ends of this connection are on the same host, a
firewall is not particularly likely to be blocking this, but you could always
change it to use 127.0.0.1 (localhost) if there is a firewall that can't
easily be changed.

In the case of the client Pi, you mentioned that ups.conf was originally empty.
You may need to restart upsd (sudo "service nut-server restart", I
think) now that it has an entry for the locally connected UPS. upsd listens on
the port that NUT clients like upsmon and upsc connect to.

- Charles

Thank you very much for the advice.

My upsd.conf [located on the server] is set to listen as follows:

LISTEN 192.168.1.100 3493
LISTEN 192.168.1.101 3493
LISTEN 0.0.0.0 3493
LISTEN 127.0.0.1 3493

After making these changes I shut both the server and client down [sudo
shutdown now].
On restart I began getting messages to the effect that the server was not
available.  The messages appeared on both the server and client terminal
displays.

I commented out the 127.0.0.1 LISTEN line on the server's upsd.conf script
and then shutdown and restarted both server and client.
The "server not available" message did not appear, however in both
instances I am still getting the "connection refused" message on the
client
[after running sudo service nut-client status].

I'm now casting about for my next move.  Clearly I've got something
configured wrong, but what I don't yet know.

On Sun, Jan 30, 2022 at 10:29 PM Charles Lepple <clepple at gmail.com>
wrote:
> [please keep the list CC'd - probably easiest via Reply-All]
>
> On Jan 28, 2022, at 10:20 AM, William Cole wrote:
> > However, when executing sudo service nut-client on the Client PC,
still
> getting a Connection refused message:
> >
> > upsmon[491] UPS [APCES750Client at 192.168.1.101]:connect failed:
> Connection failure: Connection refused
> > (repeated 9 times)
>
> "Connection refused" is a standard network error message that
says that
> either a firewall is blocking the port, or no daemon is currently listening
> on that port. Since both ends of this connection are on the same host, a
> firewall is not particularly likely to be blocking this, but you could
> always change it to use 127.0.0.1 (localhost) if there is a firewall that
> can't easily be changed.
>
> In the case of the client Pi, you mentioned that ups.conf was originally
> empty. You may need to restart upsd (sudo "service nut-server
restart", I
> think) now that it has an entry for the locally connected UPS. upsd listens
> on the port that NUT clients like upsmon and upsc connect to.
>
> - Charles


-- 
Fredericksburg, VA
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220202/2315b809/attachment.htm>