search for: fsd

...o 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 /usr/sbin/upssched the early shutdown script use "upsmon -c fsd" to set FSD to master ups. but when testing, the "upsmon -c fsd" not only set FSD to ups, it also create /etc/killpower and run SHUTDOWNCMD and terminate itself, although I have a live second ups connection. I wonder if there are other commands to set ups FSD? I can not find an...

...values successfully >> retrieved repeatedly until something like: >> .... >> Quick update... >> send: QS >> read: (247.9 239.1 248.0 005 50.0 27.5 --.- 00001001 >> update_status: OL >> update_status: !LB >> update_status: !CAL >> update_status: !FSD >> upsdrv_updateinfo... >> Quick update... >> send: QS >> (driver hangs here) >> >> I'm using Generic Q* USB/Serial driver 0.06 (2.7.2) with USB >> communication driver 0.32. Playing with pollinterval didn't help - Is there >> anything further...

...send: QS". The debug logs show values successfully > retrieved repeatedly until something like: > .... > Quick update... > send: QS > read: (247.9 239.1 248.0 005 50.0 27.5 --.- 00001001 > update_status: OL > update_status: !LB > update_status: !CAL > update_status: !FSD > upsdrv_updateinfo... > Quick update... > send: QS > (driver hangs here) > > I'm using Generic Q* USB/Serial driver 0.06 (2.7.2) with USB communication > driver 0.32. Playing with pollinterval didn't help - Is there anything > further I can do to help troubleshoot t...

...30 % with about > 15 minutes run time. And the UPS did hold for another full 10 minutes > before powering off. These are the relevant lines from /var/log/ups: > > 20200124 201318 32 0.0 12 [OB] NA 0.0 > 20200124 201323 30 0.0 13 [ALARM OB LB] NA 0.0 > 20200124 201328 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > 20200124 201333 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > 20200124 201338 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > 20200124 201340 30 0.0 13 [FSD ALARM OB LB] NA 0.0 that looks perfectly fine > > The server was shutdown properly, but for some reason it did not power...

...talled 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 be...

...tus via a special serial cable to the Windows machine. > > 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 > Synology slave is configured to immediately go into "safe mode" whenever an FSD (system shutdown message) or OB+LB (On-Battery and Low Battery) > 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...

On January 24, 2020 6:13:31 PM GMT+02:00, "Georgi D. Sotirov" <gdsotirov at gmail.com> wrote: >OK, my UPS turned out to be older that I thought. I apparently bought >and installed it in September 2016 (not 2017 as I initially wrote). >That >makes for over 3 years of work, which is over the life expectancy of >the >batteries, Good batteries can last 4-5 years.

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/l...

...l.com>: >> On Feb 28, 2012, at 3:44 AM, Arnaud Quette wrote: >> >>> Hi Billy, >>> >>> switching back this thread to -upsdev >>> >>> 2012/2/27 William R. Elliot <bill at wreassoc.com>: >>>> I have been able to set the 'FSD' from the driver and it is picked up by >>>> upsmon. ?That gives me the functionality that I was asked to put in the >>>> driver. ?If that is against the rules then I'll make an adjustment when the >>>> allowed method is defined. ?:-) >>> >&gt...

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

[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 search for the string 'FSD' (46 53 44) and replace it with 'OFF' (4F 46 46), write the file, and...

[please keep the list CC'd - use "Reply All".] On Sep 14, 2015, at 10:29 PM, d tbsky <tbskyd at gmail.com> wrote: > > 2015-09-14 20:28 GMT+08:00 Charles Lepple <clepple at gmail.com>: >> "upsmon -c fsd" sets the FSD flag on all of the UPSes attached to upsd. > > my nut version is 2.7.3. as I said, "upsmon -c fsd" not only set > the FSD flag, it will also > > 1. create /etc/killpower > 2. run SHUTDOWNCMD > 3. terminate upsmon itself Right, that is what upsm...

2015-03-17 0:24 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 16, 2015, at 12:26 PM, cinowell <cinowell at gmail.com> wrote: > >> I've done all the steps. However FSD indication did NOT disappear. So it seems UPS always send the FSD flag. One thing more. Can you launch the driver with a debug level of 3 and then report back the log (gzipped) of the same procedure suggested by Charles (extended a bit as follows)? i.e.: 1) Power down, and disconnect the UPS US...

...gt; > time. And the UPS did hold for another full 10 minutes before powering > off. > > These are the relevant lines from /var/log/ups: > > > > 20200124 201318 32 0.0 12 [OB] NA 0.0 > > 20200124 201323 30 0.0 13 [ALARM OB LB] NA 0.0 > > 20200124 201328 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > > 20200124 201333 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > > 20200124 201338 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > > 20200124 201340 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > > > > that looks perfectly fine > > > > > > > > The server...

On Mar 16, 2015, at 12:26 PM, cinowell <cinowell at gmail.com> wrote: > I've done all the steps. However FSD indication did NOT disappear. So it seems UPS always send the FSD flag. I know this sounds kind of ridiculous, but you could use a hex editor to change 'FSD' to 'OFF' in blazer_usb (it only seems to occur once), which would restore the behavior of megatec_usb. Added an issue to r...

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 FSD, the /var/log/messages in my Syno says this: 2019-12...

...as 30 % with about 15 minutes run > time. And the UPS did hold for another full 10 minutes before powering off. > These are the relevant lines from /var/log/ups: > > 20200124 201318 32 0.0 12 [OB] NA 0.0 > 20200124 201323 30 0.0 13 [ALARM OB LB] NA 0.0 > 20200124 201328 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > 20200124 201333 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > 20200124 201338 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > 20200124 201340 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > > that looks perfectly fine > > > > The server was shutdown properly, but for some reason i...

...ould still hold as charge was 30 % with about 15 minutes run time. And the UPS did hold for another full 10 minutes before powering off. These are the relevant lines from /var/log/ups: 20200124 201318 32 0.0 12 [OB] NA 0.0 20200124 201323 30 0.0 13 [ALARM OB LB] NA 0.0 20200124 201328 30 0.0 13 [FSD ALARM OB LB] NA 0.0 20200124 201333 30 0.0 13 [FSD ALARM OB LB] NA 0.0 20200124 201338 30 0.0 13 [FSD ALARM OB LB] NA 0.0 20200124 201340 30 0.0 13 [FSD ALARM OB LB] NA 0.0 The server was shutdown properly, but for some reason it did not power off. I saw an error from umount about busy file syste...

...that is executed at an ups.status="OB" event, is: echo `date` >> /root/upsLog echo " No power, shutting down the system!" >> /root/upsLog sleep 30 control=`/usr/local/ups/bin/upsc Inform@localhost ups.status` if [ $control != OL ] then /usr/local/ups/sbin/upsmon -c fsd fi I changed "telinit 0 " to "upsmon -c fsd", following the advice of Mr Selinger from the mailing list. Besides, I added "shutdownArguments={{1,0},y}" to ups.conf, as you advised me. With this configuration, if the system works correctly, according to me things shoul...

Hi Billy, switching back this thread to -upsdev 2012/2/27 William R. Elliot <bill at wreassoc.com>: > I have been able to set the 'FSD' from the driver and it is picked up by > upsmon.? That gives me the functionality that I was asked to put in the > driver.? If that is against the rules then I'll make an adjustment when the > allowed method is defined.? :-) yup, that's against the tables of the law ;-p more...