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

Hi everyone,

Well, we lost power here again.  I was not at home, but I guess a dump truck
smashed into some power poles and took out half the city; actually tripped most
of the breakers in the panel.  Anyways, the power was out for just a few seconds
and of course my servers shutdown on me after power being out for just a second
or two.  Here is my syslog from two different machines.  I included everything
just in case.

“Proton":  https://hastebin.com/uluqaqetuc.bash
"Plex”:  https://hastebin.com/apudatonun.sql

Let me know what you think.  I just tested everything over the weekend and it
all worked perfectly; cut power and machines stayed up until it was time to shut
them down (I temporarily configured them to shut down after 5 minutes so I
didn’t have to wait for the entire battery to drain).  I seriously at am a total
loss.  I guess HDD Hibernation was not the culprit either since I’m still
getting the same results.   Ugh.  Thanks everyone for all your help so far!!!!!

Regards,

Todd

--
Todd Benivegna // todd at benivegna.com
On Aug 11, 2020, 7:32 AM -0400, Larry Fahnoe <fahnoe at fahnoetech.com>,
wrote:
> On Tue, Aug 11, 2020 at 12:46 AM Roger Price <roger at
rogerprice.org> wrote:
> > > On Mon, 10 Aug 2020, Todd Benivegna wrote:
> > >
> > > > synoups: https://hastebin.com/xexafofiha.bash
> > >
> > > Wow! What a mess.  It looks as if Synology wanted to write their
own "NUT", but
> > > decided it would be easier to put their ideas in a script when
they saw they
> > > could use upssched.conf to call it.  NUT intends such a script
for timer
> > > management.  Synology use it for general system management.
>
> Roger's comment confirms my suspicion of NUT as provided by Synology.
They make a great NAS product, but then they bolt on all manner of other things.
In my opinion, best to leave the NAS as an appliance configured and managed by
their GUI tools, and let it just be a NUT client rather than trying to configure
it to be the NUT server. I use and find the RaspberryPi's to be very capable
NUT servers with the rest of my systems (including my Synology NAS) as NUT
clients. Much simpler to manage that way as you have complete control over a
fairly current NUT as provided by Raspbian (a Debian derivative). The only kink
I've run into is that the Synology NAS as a NUT client provides no means of
changing the NUT credentials, so you have to use default credentials for NUT
(another reason to make sure NUT is on a protected network).
>
> --Larry
>
> --
> Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com
>            Minneapolis, Minnesota       www.FahnoeTech.com
> _______________________________________________
> 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/20200811/d5728801/attachment.html>

On 8/12/20 3:20 AM, Todd Benivegna wrote:
> Hi everyone,
>
> Well, we lost power here again.  I was not at home, but I guess a dump 
> truck smashed into some power poles and took out half the city; 
> actually tripped most of the breakers in the panel.  Anyways, the 
> power was out for just a few seconds and of course my servers shutdown 
> on me after power being out for just a second or two.  Here is my 
> syslog from two different machines.  I included everything just in case.
>
> “Proton": https://hastebin.com/uluqaqetuc.bash
> "Plex”: https://hastebin.com/apudatonun.sql
>
> Let me know what you think.  I just tested everything over the weekend 
> and it all worked perfectly; cut power and machines stayed up until it 
> was time to shut them down (I temporarily configured them to shut down 
> after 5 minutes so I didn’t have to wait for the entire battery to 
> drain).  I seriously at am a total loss.  I guess HDD Hibernation was 
> not the culprit either since I’m still getting the same results.  
>  Ugh.  Thanks everyone for all your help so far!!!!!
>
> Regards,
>
> Todd
Todd, you fight against some stupid stuff happening in the Synology NAS. 
You will get your life back just setting one of the PIs as server and 
letting the NAS (and the other 2 computers ) be its slave(s). nut works 
perfectly fine on PIs for ages.

As a side note, I still believe that the NAS sends some stupid command 
and that you will not see it unless you sniff the conversation.

Manuel,

You are absolutely right.  I think this is all the Synology just being very
dumb.  I guess those are my only two options at this point.

I have no idea on how to set up the NUT server though on one of my NUCs or my
Pi.  Do you know any good guides out there?  I’m guessing it’s easy enough to
edit upsmon.conf on the Synology in order to get that to become a slave; I think
would be all that’s required for the Synology NAS.

Thanks,

Todd

--
Todd Benivegna // todd at benivegna.com
On Aug 11, 2020, 8:43 PM -0400, Manuel Wolfshant <wolfy at
nobugconsulting.ro>, wrote:
> On 8/12/20 3:20 AM, Todd Benivegna wrote:
> > Hi everyone,
> >
> > Well, we lost power here again.  I was not at home, but I guess a dump
> > truck smashed into some power poles and took out half the city;
> > actually tripped most of the breakers in the panel.  Anyways, the
> > power was out for just a few seconds and of course my servers shutdown
> > on me after power being out for just a second or two.  Here is my
> > syslog from two different machines.  I included everything just in
case.
> >
> > “Proton": https://hastebin.com/uluqaqetuc.bash
> > "Plex”: https://hastebin.com/apudatonun.sql
> >
> > Let me know what you think.  I just tested everything over the weekend
> > and it all worked perfectly; cut power and machines stayed up until it
> > was time to shut them down (I temporarily configured them to shut down
> > after 5 minutes so I didn’t have to wait for the entire battery to
> > drain).  I seriously at am a total loss.  I guess HDD Hibernation was
> > not the culprit either since I’m still getting the same results.
> >  Ugh.  Thanks everyone for all your help so far!!!!!
> >
> > Regards,
> >
> > Todd
>
> Todd, you fight against some stupid stuff happening in the Synology NAS.
> You will get your life back just setting one of the PIs as server and
> letting the NAS (and the other 2 computers ) be its slave(s). nut works
> perfectly fine on PIs for ages.
>
> As a side note, I still believe that the NAS sends some stupid command
> and that you will not see it unless you sniff the conversation.
>
>
>
>
>
> _______________________________________________
> 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/20200811/7f9a2b51/attachment.html>

On 8/12/20 3:42 AM, Manuel Wolfshant wrote:
> On 8/12/20 3:20 AM, Todd Benivegna wrote:
>> Hi everyone,
>>
>> Well, we lost power here again.  I was not at home, but I guess a 
>> dump truck smashed into some power poles and took out half the city; 
>> actually tripped most of the breakers in the panel.  Anyways, the 
>> power was out for just a few seconds and of course my servers 
>> shutdown on me after power being out for just a second or two.  Here 
>> is my syslog from two different machines.  I included everything just 
>> in case.
>>
>> “Proton": https://hastebin.com/uluqaqetuc.bash
>> "Plex”: https://hastebin.com/apudatonun.sql
>>
>> Let me know what you think.  I just tested everything over the 
>> weekend and it all worked perfectly; cut power and machines stayed up 
>> until it was time to shut them down (I temporarily configured them to 
>> shut down after 5 minutes so I didn’t have to wait for the entire 
>> battery to drain).  I seriously at am a total loss.  I guess HDD 
>> Hibernation was not the culprit either since I’m still getting the 
>> same results.   Ugh.  Thanks everyone for all your help so far!!!!!
>>
>> Regards,
>>
>> Todd
>
> Todd, you fight against some stupid stuff happening in the Synology NAS. 
I forgot to mention the reasoning. From your proton and plex logs:

|Aug 11 16:37:40 proton upsmon[1554]: UPS ups at 192.168.1.70 on battery 
Aug 11 16:37:45 proton upsmon[1554]: UPS ups at 192.168.1.70 on line power|
|Aug 11 16:38:10 proton upsmon[1554]: UPS ups at 192.168.1.70: forced 
shutdown in progress|
||
||Aug 11 16:37:43 plex upsmon[974]: UPS ups at 192.168.1.70 on battery Aug 
11 16:37:48 plex upsmon[974]: UPS ups at 192.168.1.70 on line power Aug 11 
16:38:13 plex upsmon[974]: UPS ups at 192.168.1.70: forced shutdown in 
progress||
||
|So nut on Synology believes that it is a good idea to trigger a FSD 30 
secs AFTER switching back to line power when in fact it should CANCEL 
any shutdown in progress. Unless you have the willingness to search & 
fix whatever stupidities they do in their unorthodox use of nut... just 
use a sane version |
||

|
|
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200812/284a42ce/attachment.html>