<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span></span></div><div>I looked into the Synology NAS NUT configuration more closely.</div><div> </div><div>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 Synology's upssched.conf with an "fsd" argument.</div><div> </div><div>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", the script aborts any action for the received FSD notification. Since the UPS is actually on-line when the test FSD is sent from the Windows master, the Synology will not enter "safe mode" - it does nothing.</div><div> </div><div>If the device was in OB, LB, or OB+LB mode, the OL check would fail and the Synology would enter "safe mode", as
expected.</div><div> </div><div>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 the Windows master, as expected.</div><div> </div><div>The Windows port is working fine in this respect.</div><div> </div><div>Best,</div><div> </div><div>Don</div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <div class="hr" style="margin: 5px 0px; padding: 0px; border: 1px solid rgb(204, 204, 204); height: 0px; line-height: 0; font-size: 0px;" contenteditable="false" readonly="true"></div> <font face="Arial" size="2"> <b><span style="font-weight: bold;">From:</span></b> Donald Froula <dfroula@sbcglobal.net><br> <b><span style="font-weight: bold;">To:</span></b> "nut-upsuser@lists.alioth.debian.org"
<nut-upsuser@lists.alioth.debian.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Wednesday, September 11, 2013 11:20 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> [Nut-upsuser] Issue with slave FSD notification on Windows port of NUT<br> </font> </div> <div class="y_msg_container"><br>
<div id="yiv376086302"><div><div style="color: rgb(0, 0, 0); font-family: times new roman, new york, times, serif; font-size: 12pt; background-color: rgb(255, 255, 255);"><div>I have the latest version of the Windows port of NUT installed on my Windows 7 machine. The UPS is connected via serial cable to the Windows machine. I also have my Synology NAS (which uses NUT) connected over the local network as a slave to the Windows NUT master. The Synology slave is configured to immediately go into "safe mode" whenever an FSD or OB+LB indication is received from the Windows NUT master.</div><div> </div><div>The Windows master machine responds correctly to OB+LB events, correctly shutting down the master machine. The Synology box also responds to the OB+LB events from the master correctly and goes into "safe mode", the expected behavior.</div><div> </div><div>The problem comes when using "upsmon -c fsd" on the Windows NUT master to test
the system. The Windows master shuts down
correctly, but the Synology NAS slave does not receive the FSD notification from the Windows master and does not go into "safe mode"..</div><div> </div><div>I'm wondering if there is a bug in the Windows port such that the FSD notification is not sent to the slaves when "upsmon -c fsd" is executed.</div><div> </div><div>Best regards,</div><div> </div><div>Don</div></div></div></div><br>_______________________________________________<br>Nut-upsuser mailing list<br><a href="mailto:Nut-upsuser@lists.alioth.debian.org" ymailto="mailto:Nut-upsuser@lists.alioth.debian.org">Nut-upsuser@lists.alioth.debian.org</a><br><a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser</a><br><br></div> </div> </div> </div></body></html>