Nut upsuser - Mar 2020 - NUT-Server will not start at boot with Cyberpower PR1500

Hi Charles,
Thanks for your response. No, I only put 192.168.1.64 as an extra option as I
want to allow Slave access from another computer. Otherwise, access will
normally only be from localhost. There is only one network interface on this
machine.
I will try it out with "LISTEN 0.0.0.0 3493" and see what happens. I
must confess I usually run without a firewall as I'm only running a home
network, but I suppose I really should start using it!
I will report back.
Paul N.
________________________________
From: Charles Lepple <clepple at gmail.com>
Sent: 07 March 2020 15:50
To: Paul Newbery <newberype at hotmail.co.uk>
Cc: nut-upsuser at alioth-lists.debian.net <nut-upsuser at
alioth-lists.debian.net>
Subject: Re: [Nut-upsuser] NUT-Server will not start at boot with Cyberpower
PR1500

On Mar 6, 2020, at 2:02 PM, Paul Newbery <newberype at hotmail.co.uk>
wrote:
>
> I have since been trying to get them working with the NUT software, which I
can do, but I simply cannot get them to start at system start up. It can be seen
from the "Syslog Nut Extract" that upsdrvctl successfully loads the
driver, but nut-server fails to start and the driver then stops as it is no
longer required. However, upsmon continues to load successfully and proceeds to
fill up the syslog with error messages.
>
Mar  6 14:05:02 paul-desktop upsd[947]: fopen /var/run/nut/upsd.pid: No such
file or directory
Mar  6 14:05:02 paul-desktop upsd[947]: /etc/nut/upsd.conf is world readable
Mar  6 14:05:02 paul-desktop upsd[947]: /etc/nut/upsd.conf is world readable
Mar  6 14:05:02 paul-desktop upsd[947]: not listening on 192.168.1.64 port 3493
Mar  6 14:05:02 paul-desktop upsd[947]: listening on ::1 port 3493
Mar  6 14:05:02 paul-desktop upsd[947]: listening on 127.0.0.1 port 3493
Mar  6 14:05:02 paul-desktop upsd[947]: no listening interface available
Mar  6 14:05:02 paul-desktop upsd[947]: not listening on 192.168.1.64 port 3493

^ At this point, the 192.168.1.64 network interface may not be up. Are you
intending to allow NUT to only listen on localhost and one specific network
interface? Or is there only one physical network interface total?

If the latter, I recommend "LISTEN 0.0.0.0" to listen on all local
addresses. If the former, I would use a firewall that does filtering well before
the packets touch NUT code, and that can also block packets destined to other
interfaces until the one allowed interface is up.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200307/7a14bc6c/attachment.html>

On Saturday 07 March 2020 12:38:07 Paul Newbery wrote:
> Hi Charles,
> Thanks for your response. No, I only put 192.168.1.64 as an extra
> option as I want to allow Slave access from another computer.
> Otherwise, access will normally only be from localhost. There is only
> one network interface on this machine. I will try it out with "LISTEN
> 0.0.0.0 3493" and see what happens. I must confess I usually run
> without a firewall as I'm only running a home network, but I suppose I
> really should start using it! I will report back.
> Paul N.
> ________________________________
> From: Charles Lepple <clepple at gmail.com>
> Sent: 07 March 2020 15:50
> To: Paul Newbery <newberype at hotmail.co.uk>
> Cc: nut-upsuser at alioth-lists.debian.net
> <nut-upsuser at alioth-lists.debian.net> Subject: Re: [Nut-upsuser]
> NUT-Server will not start at boot with Cyberpower PR1500
>
> On Mar 6, 2020, at 2:02 PM, Paul Newbery <newberype at hotmail.co.uk>
wrote:
> > I have since been trying to get them working with the NUT software,
> > which I can do, but I simply cannot get them to start at system
> > start up. It can be seen from the "Syslog Nut Extract" that
> > upsdrvctl successfully loads the driver, but nut-server fails to
> > start and the driver then stops as it is no longer required.
> > However, upsmon continues to load successfully and proceeds to fill
> > up the syslog with error messages.
>
> Mar  6 14:05:02 paul-desktop upsd[947]: fopen /var/run/nut/upsd.pid:
> No such file or directory Mar  6 14:05:02 paul-desktop upsd[947]:
> /etc/nut/upsd.conf is world readable Mar  6 14:05:02 paul-desktop
> upsd[947]: /etc/nut/upsd.conf is world readable Mar  6 14:05:02
> paul-desktop upsd[947]: not listening on 192.168.1.64 port 3493 Mar  6
> 14:05:02 paul-desktop upsd[947]: listening on ::1 port 3493 Mar  6
> 14:05:02 paul-desktop upsd[947]: listening on 127.0.0.1 port 3493 Mar 
> 6 14:05:02 paul-desktop upsd[947]: no listening interface available
> Mar  6 14:05:02 paul-desktop upsd[947]: not listening on 192.168.1.64
> port 3493
>
> ^ At this point, the 192.168.1.64 network interface may not be up. Are
> you intending to allow NUT to only listen on localhost and one
> specific network interface? Or is there only one physical network
> interface total?
>
> If the latter, I recommend "LISTEN 0.0.0.0" to listen on all
local
> addresses. If the former, I would use a firewall that does filtering
> well before the packets touch NUT code, and that can also block
> packets destined to other interfaces until the one allowed interface
> is up.
I would add that the best place for the firewall is in your router, by 
reflashing it with dd-wrt. In 2 decades of running it that way here, no 
one has come thru it to gain nefarious access has managed to do so.  By 
putting your switch on the local side of your router, you have the run 
of your local network, with no firewalls to have to putz with but 
dd-wrt's sharp teeth are keeping the black hats out.  Not to mention it 
has no TLA back doors.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

Deep Joy, it worked!!!
Changing upsd.conf to only contain "LISTEN 0.0.0.0 3493" solved the
problem.
Syslog now looks like the attached Syslog Nut extract2 file.
Many thanks for your suggestion Charles.

Gene, I do use the firewall in my ISP supplied router, but I don't know how
that stacks up against DDWRT. I do have a flashable router in the cupboard, so I
might just give it a try.
Thanks all for your help.
One happy bunny signing off...
Paul N.

________________________________
From: Nut-upsuser <nut-upsuser-bounces+newberype=hotmail.co.uk at
alioth-lists.debian.net> on behalf of Gene Heskett <gheskett at
shentel.net>
Sent: 07 March 2020 17:53
To: nut-upsuser at alioth-lists.debian.net <nut-upsuser at
alioth-lists.debian.net>
Subject: Re: [Nut-upsuser] NUT-Server will not start at boot with Cyberpower
PR1500

On Saturday 07 March 2020 12:38:07 Paul Newbery wrote:
> Hi Charles,
> Thanks for your response. No, I only put 192.168.1.64 as an extra
> option as I want to allow Slave access from another computer.
> Otherwise, access will normally only be from localhost. There is only
> one network interface on this machine. I will try it out with "LISTEN
> 0.0.0.0 3493" and see what happens. I must confess I usually run
> without a firewall as I'm only running a home network, but I suppose I
> really should start using it! I will report back.
> Paul N.
> ________________________________
> From: Charles Lepple <clepple at gmail.com>
> Sent: 07 March 2020 15:50
> To: Paul Newbery <newberype at hotmail.co.uk>
> Cc: nut-upsuser at alioth-lists.debian.net
> <nut-upsuser at alioth-lists.debian.net> Subject: Re: [Nut-upsuser]
> NUT-Server will not start at boot with Cyberpower PR1500
>
> On Mar 6, 2020, at 2:02 PM, Paul Newbery <newberype at hotmail.co.uk>
wrote:
> > I have since been trying to get them working with the NUT software,
> > which I can do, but I simply cannot get them to start at system
> > start up. It can be seen from the "Syslog Nut Extract" that
> > upsdrvctl successfully loads the driver, but nut-server fails to
> > start and the driver then stops as it is no longer required.
> > However, upsmon continues to load successfully and proceeds to fill
> > up the syslog with error messages.
>
> Mar  6 14:05:02 paul-desktop upsd[947]: fopen /var/run/nut/upsd.pid:
> No such file or directory Mar  6 14:05:02 paul-desktop upsd[947]:
> /etc/nut/upsd.conf is world readable Mar  6 14:05:02 paul-desktop
> upsd[947]: /etc/nut/upsd.conf is world readable Mar  6 14:05:02
> paul-desktop upsd[947]: not listening on 192.168.1.64 port 3493 Mar  6
> 14:05:02 paul-desktop upsd[947]: listening on ::1 port 3493 Mar  6
> 14:05:02 paul-desktop upsd[947]: listening on 127.0.0.1 port 3493 Mar
> 6 14:05:02 paul-desktop upsd[947]: no listening interface available
> Mar  6 14:05:02 paul-desktop upsd[947]: not listening on 192.168.1.64
> port 3493
>
> ^ At this point, the 192.168.1.64 network interface may not be up. Are
> you intending to allow NUT to only listen on localhost and one
> specific network interface? Or is there only one physical network
> interface total?
>
> If the latter, I recommend "LISTEN 0.0.0.0" to listen on all
local
> addresses. If the former, I would use a firewall that does filtering
> well before the packets touch NUT code, and that can also block
> packets destined to other interfaces until the one allowed interface
> is up.
I would add that the best place for the firewall is in your router, by
reflashing it with dd-wrt. In 2 decades of running it that way here, no
one has come thru it to gain nefarious access has managed to do so.  By
putting your switch on the local side of your router, you have the run
of your local network, with no firewalls to have to putz with but
dd-wrt's sharp teeth are keeping the black hats out.  Not to mention it
has no TLA back doors.

Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200307/6fe72dba/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Syslog Nut extract2
Type: application/octet-stream
Size: 2236 bytes
Desc: Syslog Nut extract2
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200307/6fe72dba/attachment-0001.obj>