similar to: Synology NAS is shutting down Ubuntu servers after very brief power outage

How would I capture with Wireshark when it seemingly happens at random?  Whenever I test, everything appears to work normally.  I wish I could somehow replicate it.  Maybe I need to test manually and see if it’ll happen in front of me; I’ve never actually seen it happen… always happens when I’m away. -- Todd Benivegna // todd at benivegna.com On Aug 2, 2020, 12:12 PM -0400, Manuel Wolfshant

On Fri, 7 Aug 2020, Todd Benivegna wrote: > APC Back-UPS NS 650M1 UPS ---USB---> Synology NAS (DS416 - Master?) > ---Ethernet---> Netgear Managed Switch w/ uplink to router <---Ethernet--- > Servers (Ubuntu 20.04 - Plex, Pulsar, Proton - All three set as slaves) I'm guessing that the UPS supplies only the NAS, not the 3 Ubuntu machines. Do they have their own UPS's?

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

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

On Thu, 6 Aug 2020, Todd Benivegna wrote: > ... I grep’d the syslog and here’s the results: Could you also grep for upsd and upsmon in the NAS log? Is this possible? > proton at proton:~$ sudo grep upsmon /var/log/syslog > Aug  6 19:19:09 proton upsmon[1552]: UPS ups at 192.168.1.70 on battery > Aug  6 19:19:14 proton upsmon[1552]: UPS ups at 192.168.1.70 on line

Roger, I just ran a manual test, killing power and see what happens.  I set the Synology “Time before DiskStation goes into Safe mode” to 5 minutes so I didn’t have to wait like an hour until it powered down.  Here is the log: https://hastebin.com/ovuwilufeb.sql Everything appeared to be normal; the servers powered off and the Synology went into safe mode.  Power was then cut to the Synology

upsmon.conf on server:  https://pastebin.com/z4CrUTxb nut.conf on server:  https://pastebin.com/540ShZH7 Permissions for /etc/nut:  https://hastebin.com/qecolodapi.diff On the Synology (I didn’t edit any of these files): ups.conf:  https://hastebin.com/dedereqizi.shell upsd.conf:  https://hastebin.com/pupeseweda.css upsd.users:  https://hastebin.com/ocenamecex.cs I don’t think I am able to run

> grep nut /etc/passwd nut:x:129:134::/var/lib/nut:/usr/sbin/nologin > In your manual test do you restore utility power after 3-5 seconds? Yes, I have tried that.  I have also tried less than one second.  I’ve tried for 1-2 minutes, for 3-5 minutes, I’ve tried just about every length of time and all appears Ok when I manually test. -- Todd Benivegna // todd at benivegna.com On Aug 5,

On 8/1/20 11:25 PM, Todd Benivegna wrote: > I'm hoping that someone can shed some light on this… I have a Synology > NAS (DS416) that has a feature where you can enable a “Network UPS > Server” which is a NUT server.  I have been trying to get the Synology > to shut down three Ubuntu 20.04 servers that I have. While it does > work when I test it out manually, sometimes when

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.

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

> Since it's NUT in the NAS which is deciding to order the shutdown, it would be > useful to see upsmon.conf, upssched.conf and upssched-cmd (or whatever Synology > use if anything) from the NAS to see what criteria they use. upsmon.conf (on Synology): RUN_AS_USER root MONITOR ups at localhost 1 monuser secret master MINSUPPLIES 1 SHUTDOWNCMD "" NOTIFYCMD /usr/sbin/upssched

Thanks Larry, no problem. I appreciate the input. Whenever you get a chance I’d really like to compare notes with someone who has NUT and a Synology to see why the heck mine doesn’t work! ;). I’m also using my Pi as the master like you. Thanks. Todd -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 11:55 AM -0400, Larry Fahnoe <fahnoe at fahnoetech.com>, wrote: > On Fri, Aug

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

On Fri, 14 Aug 2020, Todd Benivegna wrote: > https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave  > > I have the latest version of the Windows port of NUT (A UPS management package) installed on my Windows 7 machine. The UPS I am using is a > very old APC BK650M which is controlled and sends its status via a special serial cable to the Windows

Roger, Ok, so how does this look... Updated upsmon.conf:  https://hastebin.com/jisinaquso.pl > I'm guessing that the UPS supplies only the NAS, not the 3 Ubuntu machines. Do > they have their own UPS's? No, the Synology and the three servers are all on the one UPS (also my switch and spare monitor). All these are super low power devices (two Intel NUCs and a Raspberry Pi) so at

Thanks Manuel.  I’m following that guide but am now stuck when checking to make sure the nut-sever and nut-client are up and working.  I got this: proton at proton:~$ service nut-server status nut-server.service - Network UPS Tools - power devices information server      Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)      Active: failed (Result:

Hi Roger, I am not home, but when I do get home I will check out everything you've mentioned. I do have some time where I can give you a breakdown of my topology though. I have a feeling all of this is probably due to a configuration error somewhere on my part. Here's what I have done so far. *APC Back-UPS NS 650M1 UPS* ---USB---> *Synology NAS (DS416 - Master?)*

Right, but I don't know what NUT script is actually calling it. I don't know how else I would check. On Tue, Aug 4, 2020 at 10:21 AM Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > On 8/4/20 4:16 PM, Todd Benivegna wrote: > > Ok, so now that I think of it, that might not actually work when it is > > not run by me. I guess that it all confirms that it works

> Sorry. I've lost the thread here, what is the "it" you refer to? I’m not an linux expert so you’ll have to bear with me, but I guess the it I was referring to whatever NUT is using since what we’re editing is a config file, not a script; it doesn’t have a shebang at the top. > If you run the command > > grep nut /etc/password I got:  grep: /etc/password: No such file