similar to: "upsmon -c fsd" cause system shutdown

hi: when testing nut in our environment, we found something that nut maybe tune for "stale/dead ups" situation. currently the "dead ups" are assume alive(eg: host shutdown unnecessary), unless it is in the "OB" state before going to stale. our environment (ServerA + ServerB forms a cluster): ServerA-> usb to UPSA -> two PS power by UPSA and UPSB

[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

Hello all, I'm having problems with what I'm told should be a straightforward issue. The message in /var/log/daemon is: <quote> Feb 13 10:37:57 lupin upsmon[31324]: Master privileges unavailable on UPS [lupin1500AVR@localhost]

upsmon.conf using NOTIFCMD and NOTIFYFLG is working well, it is calling my script "notify" on requested events (ONBATTERY,LOWBATTERY and ONLINE). Command #upsmon -c fsd -u monmaster myups at localhost gracefully shutdown my box and after several seconds switch off the ups's load. Two problems: - notify script is called and executed as user "nut" (as it used to be

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Cheers, > > One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 > > The gist of it is that "battery.voltage" and "battery.charge" were not always reported

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Cheers, > > One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 > > The gist of it is that "battery.voltage" and "battery.charge" were not always reported

Dear list, Can't make upssched notify me on event occured. OS: Debian, 2.6.26-1-amd64 Nut: 2.4.3-1.1squeeze1 UPS: Ippon Smart Winner 3000 connected via COM On event ( plug out the cord from UPS ) upsmon detect's status change to OB and gives WALL and syslog notify, but no script starting. In syslog no errors and no upssched process occured, just upsmon. There're no PIPE and LOCK

Hi, I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified

Hi all, We have recently bought an APC UPS and are in the process of setting up the NUT software to make use of it. We are experiencing a problem with the behaviour of the slave systems when the master system goes off line. Although the failure of our master system will (hopefully) be a rare event, and we hope not to experience too many power outages, it is possible (if unlikely) that both

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

THIS IS systemctl list-units | grep UPS nut-driver at back-ups.service

Thanks for suggetions and keep me indumb about making of Debian packages:D I will try this package "nut_2.2.0-2_i386.deb" One little questionm, shoud I use newmge-shut driver? - my ups is quite old - more then 3 years, connected through serial cable. >> PS: Arjen de Korte suspected something was wrong around my "heater" load, >> for now I have used two 150W lamps

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

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

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

Hi! I'm trying to setup a small mobile server rack with key switch to power on/off the whole system. Used USP is an APC Smart-UPS 1500 SMT1500RMI2U with extra AP9613 IO card [1] to get the key switch "connected" to the UPS. The IO card has several inputs which can trigger actions like power on and "gracefully" shutdown. On key switch OFF this SMT ups model changes ups

[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

I've googled and RTFM'ed, but still can't solve this one. I hope you folks can. This affects my entire computer cluster, but let's start simple: I've got a computer running NUT; OS is Scientific Linux 5.5; kernel 2.6.18-274.12.1.el5xen. It connects to an APC SMART-UPS via an APC SmartCard using the snmp-ups driver. It generally works: upsmon will detect if the battery is low

Hi, I cant seem to get my upssched to get called by upsmon. Upsmon -c fsd just shuts down without the message I set or the one in upssched-cmd /etc/ups/upsmon.conf: MONITOR ups6 at localhost 1 <user> <pass> master MONITOR ups8 at localhost 1 <user> <pass> master SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/sbin/upssched NOTIFYMSG

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