[Nut-upsuser] Nut-upsuser Digest, Vol 200, Issue 3
William Cole
wac1606 at gmail.com
Fri Feb 4 20:29:45 GMT 2022
Thanks for the clarification. Am learning much about NUT/Linux from this
forum, which is great.
The entry for *nut-server.servic*e on my machine was the same as the one
that you listed.
It took me a while to locate* nut-server.service*, hence the delay. Here's
the result of running *script -a -c"/sbin/upsd" NUT.script.* Before
running this I had to "kill" upsd.
[image: image.png]
Looks, at minimum, like I have to lock down upsd.users. Interestingly
despite the line that "Can't connect to UPS [1LRES850] ..." (which is the
server), I can connect. The .236 line is the client.
Hope this provides some clues.
Regards,
Bill Cole
On Fri, Feb 4, 2022 at 7:00 AM <nut-upsuser-request at alioth-lists.debian.net>
wrote:
> Send Nut-upsuser mailing list submissions to
> nut-upsuser at alioth-lists.debian.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
> or, via email, send a message with subject or body 'help' to
> nut-upsuser-request at alioth-lists.debian.net
>
> You can reach the person managing the list at
> nut-upsuser-owner at alioth-lists.debian.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Nut-upsuser digest..."
>
>
> Today's Topics:
>
> 1. Re: Nut-upsuser Digest, Vol 200, Issue 2 (William Cole)
> 2. Re: Nut-upsuser Digest, Vol 200, Issue 2 (Roger Price)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 3 Feb 2022 14:09:49 -0500
> From: William Cole <wac1606 at gmail.com>
> To: nut-upsuser at alioth-lists.debian.net
> Subject: Re: [Nut-upsuser] Nut-upsuser Digest, Vol 200, Issue 2
> Message-ID:
> <CAGJ8fTG2NWppnk=
> 9iX9vGfOBf2WCOwyFfWzLARvAQnbHU9HAiA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Roger, just to make sure that I understand what you're asking, let me start
> by describing how I access the NUT server:
>
> 1. As the NUT server is already powered on it has completed its start up
> sequence.
> 2. On my Mint20 linux I start PuTTy in SSH and attach to the server which
> is at 192.168.1.100.
> 3. Then on the terminal session that PuTTy starts I log on to the RPi:
> username, password.
> 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.
>
> 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.
>
> Thanks much.
> Bill Cole
>
>
>
> On Thu, Feb 3, 2022 at 7:00 AM <
> nut-upsuser-request at alioth-lists.debian.net>
> wrote:
>
> > Send Nut-upsuser mailing list submissions to
> > nut-upsuser at alioth-lists.debian.net
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
> > or, via email, send a message with subject or body 'help' to
> > nut-upsuser-request at alioth-lists.debian.net
> >
> > You can reach the person managing the list at
> > nut-upsuser-owner at alioth-lists.debian.net
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Nut-upsuser digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: NUT Client Not Working, Server OK (William Cole)
> > 2. Re: NUT Client Not Working, Server OK (Roger Price)
> > 3. Re: NUT Client Not Working, Server OK (Matus UHLAR - fantomas)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Wed, 2 Feb 2022 10:28:36 -0500
> > From: William Cole <bga.cole at gmail.com>
> > To: Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
> > Subject: Re: [Nut-upsuser] NUT Client Not Working, Server OK
> > Message-ID:
> > <CAO_ENGii4KsMpkq+iVMxSab8xLbm7Rz5PnPt4CNU=-
> > MYUDutDQ at mail.gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > 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-0001.htm
> > >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Wed, 2 Feb 2022 16:48:52 +0100 (CET)
> > From: Roger Price <roger at rogerprice.org>
> > To: William Cole via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
> > Subject: Re: [Nut-upsuser] NUT Client Not Working, Server OK
> > Message-ID: <alpine.DEB.2.20.2202021643090.4862 at maria.rogerprice.org>
> > Content-Type: text/plain; charset="utf-8"; Format="flowed"
> >
> > On Wed, 2 Feb 2022, William Cole via Nut-upsuser wrote:
> >
> > > 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].?
> >
> > Could you show us the exact terminal transcript. E.g.
> >
> > script -a -c "your server setup command" NUT.script
> >
> > Once you have the server running, try commands such as upsc <ups_name>
> > before
> > attempting to start upsmon.
> >
> > Roger
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Wed, 2 Feb 2022 17:40:01 +0100
> > From: Matus UHLAR - fantomas <uhlar at fantomas.sk>
> > To: nut-upsuser at alioth-lists.debian.net
> > Subject: Re: [Nut-upsuser] NUT Client Not Working, Server OK
> > Message-ID: <20220202164001.GA16350 at fantomas.sk>
> > Content-Type: text/plain; charset=us-ascii; format=flowed
> >
> > On 02.02.22 10:28, William Cole via Nut-upsuser wrote:
> > >LISTEN 192.168.1.100 3493
> > >LISTEN 192.168.1.101 3493
> > >LISTEN 0.0.0.0 3493
> > >LISTEN 127.0.0.1 3493
> >
> > why?
> > "LISTEN 0.0.0.0 3493" should cover all local IPs, that's what 0.0.0.0
> > means.
> >
> > either use this one or any of others.
> >
> > --
> > Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
> > Warning: I wish NOT to receive e-mail advertising to this address.
> > Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
> > Eagles may soar, but weasels don't get sucked into jet engines.
> >
> >
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > Nut-upsuser mailing list
> > Nut-upsuser at alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
> >
> >
> > ------------------------------
> >
> > End of Nut-upsuser Digest, Vol 200, Issue 2
> > *******************************************
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220203/8d1a4899/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 2
> Date: Thu, 3 Feb 2022 21:10:49 +0100 (CET)
> From: Roger Price <roger at rogerprice.org>
> To: nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org>
> Subject: Re: [Nut-upsuser] Nut-upsuser Digest, Vol 200, Issue 2
> Message-ID: <alpine.DEB.2.20.2202032103370.4862 at maria.rogerprice.org>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> On Thu, 3 Feb 2022, William Cole via Nut-upsuser wrote:
>
> > 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.
>
> It's the ExecStart line in nut-server.service. In my nut-server.service
> setup I
> have:
>
> [Service]
> ExecStart=/sbin/upsd
> Type=forking
>
> so the script command for me would be:
>
> ?script -a -c "/sbin/upsd" NUT.script
>
> Roger
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
>
> ------------------------------
>
> End of Nut-upsuser Digest, Vol 200, Issue 3
> *******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220204/b4d2f164/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 65640 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220204/b4d2f164/attachment-0001.png>
More information about the Nut-upsuser
mailing list