Nut upsuser - Sep 2013 - Issue with slave FSD notification on Windows port of NUT

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.
?
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.
?
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"..
?
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.
?
Best regards,
?
Don
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130911/ce39927a/attachment.html>

I looked into the Synology NAS NUT configuration more closely.
?
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.
?
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.
?
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.
?
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.
?
The Windows port is working fine in this respect.
?
Best,
?
Don 

________________________________
 From: Donald Froula <dfroula at sbcglobal.net>
To: "nut-upsuser at lists.alioth.debian.org" <nut-upsuser at
lists.alioth.debian.org>
Sent: Wednesday, September 11, 2013 11:20 AM
Subject: [Nut-upsuser] Issue with slave FSD notification on Windows port of NUT
  


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.

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.

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"..

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.

Best regards,

Don
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130911/264be1bf/attachment.html>