<div dir="ltr"><div>Roger, just to make sure that I understand what you're asking, let me start by describing how I access the NUT server:</div><div><br></div><div>1. As the NUT server is already powered on it has completed its start up sequence.<br></div><div>2. On my Mint20 linux I start PuTTy in SSH and attach to the server which is at 192.168.1.100.</div><div>3. Then on the terminal session that PuTTy starts I log on to the RPi: username, password.</div><div>4. At that point I'm ready to start issuing commands. This is where and when I'd issue the script command that you have offered.<br></div><div><br></div><div>I guess I'm not understanding what "your server setup command" should be. I looked at the manpage for script - I'm still learning all this - and understand what the script command is to do in capturing terminal activity. The -c argument is looking for "your server setup command"; that's where I am stumped.</div><div><br></div><div>Thanks much.</div><div>Bill Cole<br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 3, 2022 at 7:00 AM <<a href="mailto:nut-upsuser-request@alioth-lists.debian.net">nut-upsuser-request@alioth-lists.debian.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send Nut-upsuser mailing list submissions to<br>
<a href="mailto:nut-upsuser@alioth-lists.debian.net" target="_blank">nut-upsuser@alioth-lists.debian.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:nut-upsuser-request@alioth-lists.debian.net" target="_blank">nut-upsuser-request@alioth-lists.debian.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:nut-upsuser-owner@alioth-lists.debian.net" target="_blank">nut-upsuser-owner@alioth-lists.debian.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Nut-upsuser digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: NUT Client Not Working, Server OK (William Cole)<br>
2. Re: NUT Client Not Working, Server OK (Roger Price)<br>
3. Re: NUT Client Not Working, Server OK (Matus UHLAR - fantomas)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 2 Feb 2022 10:28:36 -0500<br>
From: William Cole <<a href="mailto:bga.cole@gmail.com" target="_blank">bga.cole@gmail.com</a>><br>
To: Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net" target="_blank">nut-upsuser@alioth-lists.debian.net</a>><br>
Subject: Re: [Nut-upsuser] NUT Client Not Working, Server OK<br>
Message-ID:<br>
<CAO_ENGii4KsMpkq+iVMxSab8xLbm7Rz5PnPt4CNU=-<a href="mailto:MYUDutDQ@mail.gmail.com" target="_blank">MYUDutDQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thank you very much for the advice.<br>
<br>
My upsd.conf [located on the server] is set to listen as follows:<br>
<br>
LISTEN 192.168.1.100 3493<br>
LISTEN 192.168.1.101 3493<br>
LISTEN 0.0.0.0 3493<br>
LISTEN 127.0.0.1 3493<br>
<br>
After making these changes I shut both the server and client down [sudo<br>
shutdown now].<br>
On restart I began getting messages to the effect that the server was not<br>
available. The messages appeared on both the server and client terminal<br>
displays.<br>
<br>
I commented out the 127.0.0.1 LISTEN line on the server's upsd.conf script<br>
and then shutdown and restarted both server and client.<br>
The "server not available" message did not appear, however in both<br>
instances I am still getting the "connection refused" message on the client<br>
[after running sudo service nut-client status].<br>
<br>
I'm now casting about for my next move. Clearly I've got something<br>
configured wrong, but what I don't yet know.<br>
<br>
On Sun, Jan 30, 2022 at 10:29 PM Charles Lepple <<a href="mailto:clepple@gmail.com" target="_blank">clepple@gmail.com</a>> wrote:<br>
<br>
> [please keep the list CC'd - probably easiest via Reply-All]<br>
><br>
> On Jan 28, 2022, at 10:20 AM, William Cole wrote:<br>
> > However, when executing sudo service nut-client on the Client PC, still<br>
> getting a Connection refused message:<br>
> ><br>
> > upsmon[491] UPS [<a href="mailto:APCES750Client@192.168.1.101" target="_blank">APCES750Client@192.168.1.101</a>]:connect failed:<br>
> Connection failure: Connection refused<br>
> > (repeated 9 times)<br>
><br>
> "Connection refused" is a standard network error message that says that<br>
> either a firewall is blocking the port, or no daemon is currently listening<br>
> on that port. Since both ends of this connection are on the same host, a<br>
> firewall is not particularly likely to be blocking this, but you could<br>
> always change it to use 127.0.0.1 (localhost) if there is a firewall that<br>
> can't easily be changed.<br>
><br>
> In the case of the client Pi, you mentioned that ups.conf was originally<br>
> empty. You may need to restart upsd (sudo "service nut-server restart", I<br>
> think) now that it has an entry for the locally connected UPS. upsd listens<br>
> on the port that NUT clients like upsmon and upsc connect to.<br>
><br>
> - Charles<br>
<br>
<br>
<br>
-- <br>
Fredericksburg, VA<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220202/2315b809/attachment-0001.htm" rel="noreferrer" target="_blank">http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220202/2315b809/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 2 Feb 2022 16:48:52 +0100 (CET)<br>
From: Roger Price <<a href="mailto:roger@rogerprice.org" target="_blank">roger@rogerprice.org</a>><br>
To: William Cole via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net" target="_blank">nut-upsuser@alioth-lists.debian.net</a>><br>
Subject: Re: [Nut-upsuser] NUT Client Not Working, Server OK<br>
Message-ID: <<a href="mailto:alpine.DEB.2.20.2202021643090.4862@maria.rogerprice.org" target="_blank">alpine.DEB.2.20.2202021643090.4862@maria.rogerprice.org</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
On Wed, 2 Feb 2022, William Cole via Nut-upsuser wrote:<br>
<br>
> My upsd.conf [located on the server] is set to listen as follows:<br>
> <br>
> LISTEN 192.168.1.100 3493<br>
> LISTEN 192.168.1.101 3493<br>
> LISTEN 0.0.0.0 3493<br>
> LISTEN 127.0.0.1 3493<br>
> <br>
> After making these changes I shut both the server and client down [sudo shutdown now].<br>
> 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<br>
> displays.<br>
> <br>
> 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.<br>
> The "server not available" message did not appear, however in both instances I am still getting the "connection refused" message on the client [after<br>
> running sudo service nut-client status].?<br>
<br>
Could you show us the exact terminal transcript. E.g.<br>
<br>
script -a -c "your server setup command" NUT.script<br>
<br>
Once you have the server running, try commands such as upsc <ups_name> before <br>
attempting to start upsmon.<br>
<br>
Roger<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 2 Feb 2022 17:40:01 +0100<br>
From: Matus UHLAR - fantomas <<a href="mailto:uhlar@fantomas.sk" target="_blank">uhlar@fantomas.sk</a>><br>
To: <a href="mailto:nut-upsuser@alioth-lists.debian.net" target="_blank">nut-upsuser@alioth-lists.debian.net</a><br>
Subject: Re: [Nut-upsuser] NUT Client Not Working, Server OK<br>
Message-ID: <<a href="mailto:20220202164001.GA16350@fantomas.sk" target="_blank">20220202164001.GA16350@fantomas.sk</a>><br>
Content-Type: text/plain; charset=us-ascii; format=flowed<br>
<br>
On 02.02.22 10:28, William Cole via Nut-upsuser wrote:<br>
>LISTEN 192.168.1.100 3493<br>
>LISTEN 192.168.1.101 3493<br>
>LISTEN 0.0.0.0 3493<br>
>LISTEN 127.0.0.1 3493<br>
<br>
why? <br>
"LISTEN 0.0.0.0 3493" should cover all local IPs, that's what 0.0.0.0 means.<br>
<br>
either use this one or any of others.<br>
<br>
-- <br>
Matus UHLAR - fantomas, <a href="mailto:uhlar@fantomas.sk" target="_blank">uhlar@fantomas.sk</a> ; <a href="http://www.fantomas.sk/" rel="noreferrer" target="_blank">http://www.fantomas.sk/</a><br>
Warning: I wish NOT to receive e-mail advertising to this address.<br>
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.<br>
Eagles may soar, but weasels don't get sucked into jet engines.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Nut-upsuser Digest, Vol 200, Issue 2<br>
*******************************************<br>
</blockquote></div>