Yeah I saw that. Makes no sense. I can Wireshark it, however even if I find the cause, I’d still have to go to Synology for resolution, which I doubt will ever get fixed. Even if they do, I doubt it’d be any time soon. Maybe that’s me being pessimistic, I don’t know, but I just don’t if I have the time or energy for all that!
-- Todd Benivegna // t...@benivegna.com On Aug 11, 2020, 8:57 PM -0400, Manuel Wolfshant <wo...@nobugconsulting.ro>, wrote: > 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@192.168.1.70 on battery > Aug 11 16:37:45 proton upsmon[1554]: UPS ups@192.168.1.70 on line power > Aug 11 16:38:10 proton upsmon[1554]: UPS ups@192.168.1.70: forced shutdown in > progress > > Aug 11 16:37:43 plex upsmon[974]: UPS ups@192.168.1.70 on battery > Aug 11 16:37:48 plex upsmon[974]: UPS ups@192.168.1.70 on line power > Aug 11 16:38:13 plex upsmon[974]: UPS ups@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 > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
