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

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.

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/20200812/030a740e/attachment.html>

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>