similar to: Issue with slave FSD notification on Windows port of NUT

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

I have pfsense set as the NUT master and my Synology NAS as a slave client. I tried recreating a shutdown sequence by issuing a /usr/local/sbin/upsmon -c fsd command in pfsense (so as to preserve battery lifetime while testing all these) but the weird thing is that my Syno doesn't seem to get a hold of the FSD event. My pfsense master and UPS shuts down properly though. As soon as I issue the

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

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

OS name and version: MacOS 10.9.5 on 2011 Mac mini NUT version: 2.7.4-1 NUT installation method: Package installed via FINK and FinkCommander Exact device name: APC Back-UPS NS 650M1 (brand new) Issue: I have the NUT client installed and running properly; two processes running as root and the other as regular user processes. The NUT server is my Synology NAS (DS416). Client is

> 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

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

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

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

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

hello, i have an apc smt750i with 3 debian computers connected to it. i want one of them act as a master to notify the other two in case the battery is about to exhaust. upsmon in the slaves gets notified when the system changes from main to battery and viceversa. the problem i have is that the slaves are not notified and shutdown because of losing the connection to the master, but not for

hi: my testing server has two power supply and attach to two ups. one of the ups is connect to the server with usb. my upsmon.conf like below: # for two ups MONITOR ftups at localhost 1 monmaster nutmaster master MONITOR ftups at 10.1.1.2 1 monslave nutslave slave MINSUPPLIES 1 # for early shutdown NOTIFYFLAG ONBATT EXEC+WALL+SYSLOG NOTIFYFLAG ONLINE EXEC+WALL+SYSLOG NOTIFYCMD

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,

I found something interesting that I think may apply here. Check this out... 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

Sorry, I guess it is */usr/syno/bin/synoups* On Fri, Aug 14, 2020 at 2:27 PM Todd Benivegna <todd at benivegna.com> wrote: > I found something interesting that I think may apply here. Check this > out... > > > > 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

Hi I'm having a problem with the bcmxcp_usb driver FSD command: everything seems to work apart from: upsmon -c fsd Environment: Ubuntu 7.04, nut 2.0.5-1, nut-usb 2.0.5-1, Powerware 3105 UPS. upsd appears to send the FSD command to the UPS, upsmon then runs my NOTIFYCMD (which halts my PC) but the UPS just doesn't turn off. Here are the /var/log/daemon.log entries: Jul 24 23:13:16

[please keep the list cc'd - thanks] On Mar 22, 2015, at 6:20 AM, cinowell <cinowell at gmail.com> wrote: > I may use the 'mc' in terminal. But I am not sure how to find the exact bit of FSD? I am totally newbie in this topic. > Could you please elaborate the hex editing of FSD bit? I haven't used 'mc' before, but assuming it has a hex editor, you would just

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.

>> I am running NUT on a Synology NAS with attached a USB APC UPS. > > Do you have upsd and upsmon running as daemons on the Synology DSM? > Yes I have them both running on the Synology DSM: root 7236 1 0 Jun01 ? 00:00:16 /usr/sbin/upsd root 7741 1 0 Jun01 ? 00:00:00 /usr/sbin/upsmon root 7744 7741 0 Jun01 ? 00:00:12

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: