Nut upsuser - Aug 2020 - Synology NAS is shutting down Ubuntu servers after very brief power outage (fwd)

So I finally got a test in after I changed my RPi to the master and everything
else (including my Synology) to slaves.  Before I did that though, I timed the
shutdown of my Synology since it is the slowest slave to shutdown.  It took 40
seconds to shutdown, so I changed HOSTSYNC in upsmon.conf on the master
(“Proton”) to 60.  I then did a test ("sudo upsmon -c fsd”). The slaves
shutdown, then eventually the master, but the Synology never powered down and
the UPS powered off which cut the power to it while it was still on.  Anyone
know what the heck is going on?  I’m feeling a bit cursed, haha.

--
Todd Benivegna // todd at benivegna.com
On Aug 12, 2020, 7:07 PM -0400, Todd Benivegna <todd at benivegna.com>,
wrote:
> This fixed everything! Everything appears to be working ok now and all
clients are connected. Thank you!
>
> Going to test everything out now.
>
> --
> Todd Benivegna // todd at benivegna.com
> On Aug 12, 2020, 6:16 PM -0400, Charles Lepple <clepple at
gmail.com>, wrote:
> > On Aug 12, 2020, at 5:32 PM, Todd Benivegna <todd at
benivegna.com> wrote:
> > >
> > > > Those LISTEN lines were appropriate pre-systemd when
NUT's startup script was launched after networking was fully enabled. I
would recommend "LISTEN 0.0.0.0 3493" instead, and use firewall rules
if you are trying to exclude an interface (which is likely not the case on a
Pi).
> >
> > > Ok, so replace both with that or just one of the lines? I
suspected one of the lines may be the problem because when I took out the second
line, nut-server service wouldn’t fail, but then clients couldn’t connect.
> >
> > Recommend replacing both. Binding to 0.0.0.0 will allow connections
to/from 127.0.0.1. The error handling is not ideal, but upsd logs messages as it
parses. You can stop the service (if systemd is still trying to restart it), and
then try "sudo upsd -D" to see what it is doing. It should respond to
Ctrl-C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200813/5e748ce5/attachment.html>

On August 14, 2020 3:46:05 AM GMT+03:00, Todd Benivegna <todd at
benivegna.com> wrote:
>So I finally got a test in after I changed my RPi to the master and
>everything else (including my Synology) to slaves.  Before I did that
>though, I timed the shutdown of my Synology since it is the slowest
>slave to shutdown.  It took 40 seconds to shutdown, so I changed
>HOSTSYNC in upsmon.conf on the master (“Proton”) to 60.  I then did a
>test ("sudo upsmon -c fsd”). The slaves shutdown, then eventually the
>master, but the Synology never powered down and the UPS powered off
>which cut the power to it while it was still on.  Anyone know what the
>heck is going on?  
Beside the ups mngmnt software ( after Roger's analysis I refuse to call it
"nut" any more) on the Synology being a POS ?
Assuming you did configure correctly the client on the Synology, I guess that
probably they reimplemented the slave part just as well as the server..

I wonder how difficult it would be to rip off their modifications and revert to
a.standard, functional nut.

Not much in the way of configuration…. I’m pretty sure I’ve got it correct.


--
Todd Benivegna // todd at benivegna.com
On Aug 13, 2020, 8:54 PM -0400, Manuel Wolfshant <wolfy at
nobugconsulting.ro>, wrote:
> On August 14, 2020 3:46:05 AM GMT+03:00, Todd Benivegna <todd at
benivegna.com> wrote:
> > So I finally got a test in after I changed my RPi to the master and
> > everything else (including my Synology) to slaves.  Before I did that
> > though, I timed the shutdown of my Synology since it is the slowest
> > slave to shutdown.  It took 40 seconds to shutdown, so I changed
> > HOSTSYNC in upsmon.conf on the master (“Proton”) to 60.  I then did a
> > test ("sudo upsmon -c fsd”). The slaves shutdown, then eventually
the
> > master, but the Synology never powered down and the UPS powered off
> > which cut the power to it while it was still on.  Anyone know what the
> > heck is going on?
> Beside the ups mngmnt software ( after Roger's analysis I refuse to
call it "nut" any more) on the Synology being a POS ?
> Assuming you did configure correctly the client on the Synology, I guess
that probably they reimplemented the slave part just as well as the server..
>
> I wonder how difficult it would be to rip off their modifications and
revert to a.standard, functional nut.
>
> _______________________________________________
> 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/20200813/25180b63/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2020-08-13 at 8.56.22 PM.png
Type: image/png
Size: 81506 bytes
Desc: not available
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200813/25180b63/attachment-0001.png>

On Thu, 13 Aug 2020, Todd Benivegna wrote:
> So I finally got a test in after I changed my RPi to the master and
everything
> else (including my Synology) to slaves.  Before I did that though, I timed
the
> shutdown of my Synology since it is the slowest slave to shutdown.  It took
40
> seconds to shutdown, so I changed HOSTSYNC in upsmon.conf on the master 
> (“Proton”) to 60.  I then did a test ("sudo upsmon -c fsd”). The
slaves
> shutdown, then eventually the master, but the Synology never powered down
and
> the UPS powered off which cut the power to it while it was still on.
In Synology's upsmon.conf, they have SHUTDOWNCMD "".  Perhaps for
correct slave
operation this should be SHUTDOWNCMD "shutdown -h +0" or maybe one of
the
variants which also displays the UPS status and charge such as

  SHUTDOWNCMD "logger -t upsmon.conf \"UPS status at shutdown [$( upsc
<myups> ups.status )]:$( upsc <myups> battery.charge )\" ;
/sbin/shutdown -h +0"

Roger

Fortunately, several messages earlier there was an explanation how Synology has
implemented UPS management.
So SHUTDOWN CMD "" is a normal behaviour. It is managed by scripts
outside of NUT.

Alex

On Thu, Aug 13, 2020 at 7:46 PM Todd Benivegna <todd at benivegna.com>
wrote:
> So I finally got a test in after I changed my RPi to the master and
> everything else (including my Synology) to slaves.  Before I did that
> though, I timed the shutdown of my Synology since it is the slowest slave
> to shutdown.  It took 40 seconds to shutdown, so I changed HOSTSYNC in
> upsmon.conf on the master (“Proton”) to 60.  I then did a test ("sudo
> upsmon -c fsd”). The slaves shutdown, then eventually the master, but the
> Synology never powered down and the UPS powered off which cut the power to
> it while it was still on.  Anyone know what the heck is going on?  I’m
> feeling a bit cursed, haha.
>
I wonder if as a result of the tinkering and testing something has gotten
mucked up in your Synology's config...perhaps in the config files you were
editing? I wonder this because with a stock Synology UPS configuration as a
NUT client to my RaspberryPi NUT server, my Synology does power off
properly. I do not know if there is a way to restore the Synology's UPS
config files to the default configuration, though that might be a
worthwhile endeavor for your NAS.

--Larry

-- 
Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com
           Minneapolis, Minnesota       www.FahnoeTech.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200814/2c278c1a/attachment.html>

On Fri, 14 Aug 2020, Larry Fahnoe wrote:
> I wonder if as a result of the tinkering and testing something has gotten
mucked up in your Synology's config...perhaps in the config files you were
> editing? I wonder this because with a stock Synology UPS configuration as a
NUT client to my RaspberryPi NUT server, my Synology does power off properly.
> I do not know if there is a way to restore the Synology's UPS config
files to the default configuration, though that might be a worthwhile endeavor
for
> your NAS.
The Synology config files that I read from Todd's hastebin are at

  http://rogerprice.org/NUT/Synology-config

I assume that these are the originals.

Roger

>I wonder how difficult it would be to rip off their modifications and revert
to a.standard, functional nut.
I think it should be preatty simple. just rename Synology files and replacewith
what you think is the best there... it's just a banch of scripts nothing
more...

Larry,

I have not edited a single file, including anything to do with NUT, on the
Synology via ssh.... ever. How is yours configured in the UI? Do you have it set
to go into safe mode after a certain number minutes?

Earlier, I was just copying and pasting the contents of some files to Roger but
did not change anything.

--
Todd Benivegna // todd at benivegna.com
On Aug 14, 2020, 8:16 AM -0400, Larry Fahnoe <fahnoe at fahnoetech.com>,
wrote:
> On Thu, Aug 13, 2020 at 7:46 PM Todd Benivegna <todd at
benivegna.com> wrote:
> > > So I finally got a test in after I changed my RPi to the master
and everything else (including my Synology) to slaves.  Before I did that
though, I timed the shutdown of my Synology since it is the slowest slave to
shutdown.  It took 40 seconds to shutdown, so I changed HOSTSYNC in upsmon.conf
on the master (“Proton”) to 60.  I then did a test ("sudo upsmon -c fsd”).
The slaves shutdown, then eventually the master, but the Synology never powered
down and the UPS powered off which cut the power to it while it was still
on.  Anyone know what the heck is going on?  I’m feeling a bit cursed, haha.
>
> I wonder if as a result of the tinkering and testing something has gotten
mucked up in your Synology's config...perhaps in the config files you were
editing? I wonder this because with a stock Synology UPS configuration as a NUT
client to my RaspberryPi NUT server, my Synology does power off properly. I do
not know if there is a way to restore the Synology's UPS config files to the
default configuration, though that might be a worthwhile endeavor for your NAS.
>
> --Larry
>
> --
> Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com
>            Minneapolis, Minnesota       www.FahnoeTech.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200814/31001956/attachment-0001.html>