<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">Hey everyone,<br />
<br />
I did a manual test by physically disconnecting power to the ups and everything worked. I guess the Synology is dumb about doing it via the “upsmon -c fsd” command. All slaves shutdown, the Synology went into safe mode, then the master shut down, then two minutes later the ups powered off. Restored power and all machines powered up on their own and booted up. <br />
<br />
Thanks everyone for your help! Much appreciated. Hopefully this happens when the power goes out for real! ;)<br />
<br />
Regards,<br />
<br />
Todd </div>
</div>
<div name="messageSignatureSection"><br />
<p style="margin: 0px; font-stretch: normal; line-height: normal; font-family: "Helvetica Neue"; color: rgb(34, 34, 34);">--</p>
<p style="margin: 0px; font-stretch: normal; line-height: normal; font-family: "Helvetica Neue"; color: rgb(51, 51, 51);"><span style="color: #222222"><b>Todd Benivegna</b></span> <span style="color: #222222">//</span> <a href="mailto:todd@benivegna.com">todd@benivegna.com</a></p>
</div>
<div name="messageReplySection">On Aug 14, 2020, 4:52 PM -0400, Roger Price <roger@rogerprice.org>, wrote:<br />
<blockquote type="cite" style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left: 10px;">On Fri, 14 Aug 2020, Todd Benivegna wrote:<br />
<br />
<blockquote type="cite">https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave <br />
<br />
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<br />
very old APC BK650M which is controlled and sends its status via a special serial cable to the Windows machine.<br />
<br />
I also have my Synology NAS (which uses NUT for its UPS management) connected over the local network as a slave to the Windows NUT master. The<br />
Synology slave is configured to immediately go into "safe mode" whenever an FSD (system shutdown message) or OB+LB (On-Battery and Low Battery)<br />
indication is received from the Windows NUT master.<br />
<br />
The Windows master machine responds correctly to OB+LB events, correctly shutting down the master machine. The Synology box also responds to the<br />
OB+LB events from the master correctly and goes into "safe mode", the expected behavior.<br />
<br />
The problem comes when using the command "upsmon -c fsd" on the Windows NUT master to force a UPS system shutdown to test the system. The Windows<br />
master shuts down correctly, but the Synology NAS slave does not go into "safe mode" when it receives the FSD notification.<br />
<br />
I was wondering if there is a bug in the Windows port of NUT such that the FSD notification is not sent to the slaves when "upsmon -c fsd" is<br />
executed.<br />
<br />
I then looked into the Synology NAS NUT configuration more closely.<br />
<br />
When configured as a NUT slave device, the Synology responds to an FSD notification from the NUT master by calling a script defined in the<br />
Synology's /usr/syno/etc/ups/upssched.conf with an "fsd" argument. The script is /usr/syno/bin/synoups.<br />
<br />
Before causing the NAS to go into "safe mode", the script first retrieves the status of the NUT master with upsc. If the status is "OL" (on-line),<br />
the script aborts any action for the received FSD notification. Since the UPS is actually on-line and not in a low battery state when the test FSD<br />
is sent from the Windows master, the Synology will not enter "safe mode" - it does nothing.<br /></blockquote>
<br />
Not quite true.<br />
<br />
Script /usr/syno/bin/synoups calls command /usr/sbin/upsmon -c fsd and then<br />
calls function UPSSafeMode fsd. This function reads the UPS status ups.status<br />
into variable $St.<br />
<br />
If $St is exactly "OL" the function logs "UPS is On-Line" and exits.<br />
<br />
But if $St = "OL FSD" then the function goes into Safe Mode, stops all services<br />
and unmounts volumes.<br />
<br />
<blockquote type="cite">If the device was in OB (on battery), LB (low battery), or OB+LB mode, the OL check would fail and the Synology would enter "safe mode", as<br />
expected.<br />
<br />
I tried commenting out the OL status check in the Synology script. The Synology slave then enters "safe mode" when a "upsmon -c fsd" is issued from<br />
the Windows master, as expected.<br />
<br />
Interesting that Synology disables the test functionality on the NAS.<br />
<br />
Roger, do you know where in /usr/syno/etc/ups/upssched.conf the OL status check is as mentioned above? I'd like to comment that out and see if it works. <br />
I'd really like to test everything out without waiting for the battery to run out, but if not then I will do that; will just take about 45 minutes or so. <br />
I would never have guessed that it would do a check like that, which basically prevents the "upsmon -c fsd" test!<br /></blockquote>
<br />
In /usr/syno/bin/synoups function UPSSafeMode you need to change<br />
<br />
if [ "$St" = "OL" ]; then<br />
SYSLOG "WARNING: UPS is On-Line"<br />
return<br />
<br />
to something like<br />
<br />
if [[ "$St" =~ "OL" ]]; then<br />
SYSLOG "WARNING: UPS is On-Line"<br />
return<br />
<br />
This assumes that the NAS supports the =~ operator of Bash 4. To reduce the<br />
long wait: in the NAS you need to execute<br />
<br />
upsrw -s battery.charge.low=85 -u <upsuser> -p sekret <myups><br />
<br />
Better is to set this value in the NAS ups.conf.<br />
<br />
Roger<br />
_______________________________________________<br />
Nut-upsuser mailing list<br />
Nut-upsuser@alioth-lists.debian.net<br />
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</blockquote>
</div>
</body>
</html>