search for: onbattery

...lems: - driver not starts every time (about 2 times failed from 5 tries), some where I found that the solution could be a 5 time retry in the start script (/etc/init.d/nut); - if I use POLLFREQ 5 (recommended default) I have been "staled" about 2-3 times in an hour. But on ONBATTERY situation it could could be more frequent!? - I think this is the core of the problem. - the UPS switchdown early, and after 5-10 seconds the boxes follow him:( I'm trying to set lobatt=70, offdelay=20, ondelay=60 (10 minutes), notification=3 - but the situation still remain, and UPS swi...

...ut the "online" and "onbatt" NOTIFYFLAG messages. I then did a reload of upsmon...but found I was still getting the messages. Long story short, my upsmon.conf file now consists of a single entry: MONITOR rtdups at localhost 1 upsmaster sekret master I'm still getting the onbattery, online, comm good, comm bad, etc system messages. Clearly there is some default behavior going on. How do I keep these system messages from happening? Thanks Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-...

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 defined in nut package for Debian...

...;mailer.tovis at freemail.hu>: > newmge-shut ??? > Shutdown, switch of ups does not work. Using command > #upsmon -c fsd -u monmaster > shutdown the boxes but the ups leave untached - I plugged back online > manually. > > Using ups-cgi (old version found in etch) not reports ONBATTERY. > No message to all connected users ONBATTERY > No changes in battery charge level > > After reboot web status show "LOWBATTERY" as low as 26% (I doesnt check > upsc)!!! > I do not recognize "stale" situation - but I do not know that I should be > happy or...

...ironment only if *both* UPSes are on battery. I've created the 2 "MONITOR" entries, giving 1 power supply each, and I've set MINSUPPLIES to 1. But since I want early shutdown, I also need to configure the count-down timer for upssched. I tried the usual: AT ONBATT * START-TIMER onbattery 60 But of course, this triggers even if only one of them goes on battery. How can I create a timer that only starts if *both* UPSes are on battery at the same time? That timer should also be cancelled as soon as *one of them* comes back on-line, like this I suppose: AT ONLINE * CANCEL-TIMER onb...

On Sep 11, 2014, at 10:38 AM, Rob Groner <rgroner at RTD.com> wrote: > I?m still getting the onbattery, online, comm good, comm bad, etc system messages. Clearly there is some default behavior going on. How do I keep these system messages from happening? From http://www.networkupstools.org/docs/man/upsmon.conf.html: "NOTIFYFLAG type flag[+flag][+flag]? By default, upsmon sends walls globa...

...anism)? So I thought the NUT devs would likely have this for a long time ;) A cursory google search found no relevant hits, so I guess this fake UPS driver is not published - or I used wrong keywords... So: is there any ready-to-use tool/technique to fool NUT clients into believing they are OnLine/OnBattery/Critical and must shutdown, so that I can test and debug the OS-side shutdown procedures without really toggling power on hardware systems? Thanks, //Jim Klimov

...uestionm, 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 and it cause load 52% in case >> "ONBATTERY". When battery is charged over 95% the nut is working as >> suspected, but after first shutdown - switch up cycle the charge is about >> 86% and sequence does not work (usp shutdown early). > well, this is a know behavior of the old Pulsar Ellipse. When > restarting after a...

> If you set lowbatt=70 then the behaviour you are seeing is normal. Don't > set lowbatt and you'll get the default manufacturer settings which is > LOWBATTERY at 30% charge level. > > Philippe Thanks for quick response! I realized this and forget this setting! For now I think that my box does not recognize signal about low battery - I'm only started to read SHUT

Anyone else around using apcupsd? I seem to be seeing a problem, and I'd like someone to check me on it: I edit /etc/apcupsd/apccontrol to replace the value of SHUTDOWN from /sbin/shutdown to /bin/false (we don't want 3 or 6 servers shutting down over a 2 second or so blip, which it really wants to do). What's happened is that a machine shut down the other day, and looking at it, I

...to have a system that: - - reads the state of an attached UPS frequently - - can be requested from a TCP Client using <ip-of-machine>:3493 - What needs to be modified to: - - have a local installation that would run local programs upon events from the UPS (like "onpower", "onbattery") - - have the machine respond (or allow to open) to clients using the <ip-of-machine>:3493 to connect - is there any way to run an exe locally to tell in which state the system is? I have: - sucessfully installed the msi - got the service to run (after first errors and finally change...

...y Start 40s Firmware 02 Load 23% Power Nominal 1200VA Status OL During a power outage it used to last for about 15 minutes and then initiate the shutdown. however reviewing the logs of my systems: Apr 19 12:04:23 - OnBattery Apr 19 12:10:21 - Power from UPS cut, all systems got suddenly powered off (no graceful shutdown) Apr 19 12:16:46 - Power restored, UPS feeds power again to the systems and they boot up. So this indicated the UPS only lasted about 6 minutes. Also I have 2 UPS: - UPSdevice, which is the real UPS -...

...efine APCC_OID_POWER_STATUS ".1.3.6.1.4.1.318.1.1.1.4.1.1.0" /* Defines for APCC_OID_POWER_STATUS */ info_lkp_t apcc_pwr_info[] = { { 1, "" }, /* unknown */ { 2, "OL" }, /* onLine */ { 3, "OB" }, /* onBattery */ { 4, "BOOST" }, /* onSmartBoost */ { 5, "OFF" }, /* timedSleeping */ { 6, "OFF" }, /* softwareBypass */ { 7, "OFF" }, /* off */ { 8, "" }, /* rebooting */ { 9,...

....2 input.voltage.fault: 235.2 input.voltage.nominal: 230 output.voltage: 234.7 ups.beeper.status: enabled ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 5 ups.productid: 0000 ups.status: OL ups.type: offline / line interactive ups.vendorid: 0001 NUT version 2.7.1 Shutdown sequence working, onbattery nofity too. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150918/cb348d4d/attachment.html>

...> not tested > test.battery.start - Start a battery test >> not working > test.battery.start.deep - Start a deep battery test >> not working > test.battery.stop - Stop the battery test >> not working > > > UPS succesfully returns OnBoost/OnBuck/OnBattery/OnLine information to > megatec driver, as well as LowBattery/BatteryCritical alerts. This is a > line interactive unit with sinus wave AC output at all times. More > information regarding this cheap unit can be retrieved via > http://www.informups.com/informer_compact.html (EN, user gu...

.... PWRFAILDIR /etc/apcupsd # NOLOGINDIR <path to nologin directory> # Directory in which to write the nologin file. The existence # of this flag file tells the OS to disallow new logins. NOLOGINDIR /etc # # ======== Configuration parameters used during power failures ========== # # The ONBATTERYDELAY is the time in seconds from when a power failure # is detected until we react to it with an onbattery event. # # This means that, apccontrol will be called with the powerout argument # immediately when a power failure is detected. However, the # onbattery argument is passed to apccont...

...restart helped, so they were not a VM/host hardware problems. As suggested everywhere, I tried to change timeouts. Pollfreq made no changes. But changing the driver pollinterval to 10 (instead of default 2) has helped. No more timeouts were received. But suddenly I found that now NUT does not see OnBattery events at all. If I pull the power cord from UPS, it immediately reports input voltage = 0, but still "is" OnLine. I found that very weird but started to play with timeouts again. I tried different values as well as set the pollonly flag - no luck. Setting any pollinterval value above def...

Hey all, I found a pinout of powercom's Kingpro UPSes in their manual. http://www.powercom-ups.com/manuals/kingpro.pdf Page 11. Unfortunately, this doesn't give PROTOCOL details. Does anyone have a "first step" at how to decode that? (for example, how to gauge line speed, how to "snoop" the serial port under windows? (for which the only software exists right

So, a while back I got around to ordering replacement batteries for my CyberPower PR3000LCDRTXL2U. When they arrived, I went to swap them in. I was horrified at the flimsiness of CyberPower's battery "trays". I've seen heavier gauge plastic on "blister" packages in the store. I ALSO discovered that the expansion unit had been shipped to me with one of its two

...02 > Load 23% > Power Nominal 1200VA > Status OL > > During a power outage it used to last for about 15 minutes and then > initiate the shutdown. however reviewing the logs of my systems: > > Apr 19 12:04:23 - OnBattery > Apr 19 12:10:21 - Power from UPS cut, all systems got suddenly powered off > (no graceful shutdown) > Apr 19 12:16:46 - Power restored, UPS feeds power again to the systems and > they boot up. > > So this indicated the UPS only lasted about 6 minutes. > > Also I have 2 UPS...