similar to: Detect ups.status on battery seems a little delay

On Tue, 4 Apr 2017, Arnaud Quette wrote: > Hi Jon, Stuart and the list > > 2017-04-04 1:09 GMT+02:00 Stuart Gathman <stuart at gathman.org>: > Which NOTIFYCMD is run when there is an ALARM? > Have you specified that in your upsmon.conf? > > And that is the question of the hour.? How do you specify that?? Note > that this is not the REPLBATT

> What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines when to shut down. > > Also, if you don't want to wait for both UPSes to drain to the low battery state, you can set up a pair of dummy-ups drivers. I'm

On Jan 21, 2014, at 3:16 AM, Rafa? Oleszek wrote: > I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines

On 04/04/17 14.10, Roger Price wrote: > On Tue, 4 Apr 2017, Arnaud Quette wrote: > [cuuuuut] > Hi Arnaud, It seems to me that, looking out into the future, there are three > things upsmon needs: > > 1. A fall-through <notify type> of "UNKNOWN" so that all status changes, no > matter how wierd, can be caught. Such a catch-all <notify type> would also

On 04/03/2017 07:03 PM, Gene Heskett wrote: > > But it does that because you have tried to get 12 years out of a gell > cell battery that is doing really really well if you get 4 years out of > it. I am not saying you should do that _now_, without first replacing > that thoroughly boiled dry battery, but as something you should set it > up to do once you have a serviceable

I've recently moved from installing NUT from source to installing NUT from the FreeBSD package (FreeBSD 9.1). One would think that I might have learned not to change anything, but I made the change. And here is my tale of woe..... My first question is: is it possible to simulate a "UPS is on battery" state? Some background: UPS comm port is connected to and monitored by

Hi! Some systems I have take some time to shut down, so I would like them to shut down if the UPS have been on battery for 2 minutes. Internet has told me that SHUTDOWNCMD ?/sbin/shutdown -h +0? in /etc/nut/upsmon.conf will execute when the UPS is both OB (on battery) and LB (Low battery). Like in wiki.ipfire.org - Detailed NUT Configuration<https://wiki.ipfire.org/addons/nut/detailed>

Hi, I tried to do the minimum configuration for Nut. When I stop the on-line power i get terminal message that I'm on battery power and when I plug on-line power back in I get a message that I'm back to on-line power. So things are working/communicating. What I want is: if it's been on battery power for over 5 minutes the PC will shutdown. If powers comes on-line again before the 5

Hi! Using this guide: http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/ and systematically testing the usb capable driver on your site I managed to get my FSP EP650 (by http://www.fspgroupusa.com/ ) working (after reboot). Im running Ubuntu 9.10 desktop x64 standard install. This is the output from running "upsc ups1" ----- battery.voltage: 13.50

2017-04-04 14:18 GMT+02:00 Jon Bendtsen <jon.bendtsen at jonix.dk>: > On 04/04/17 14.10, Roger Price wrote: > >> On Tue, 4 Apr 2017, Arnaud Quette wrote: >> >> > [cuuuuut] > > Hi Arnaud, It seems to me that, looking out into the future, there are >> three >> things upsmon needs: >> >> 1. A fall-through <notify type> of

Now I have this in /etc/nut/upsmon.conf (my QNAP NAS wants admin and 123456 or not working) RUN_AS_USER root MONITOR qnapups at localhost 1 admin 123456 master MONITOR qnapups at 192.168.222.252 3493 admin 123456 slave MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC

On Monday 03 April 2017 14:13:08 Stuart D. Gathman wrote: Back on the mailing list, where such belongs. > On Mon, 3 Apr 2017, Gene Heskett wrote: > > Nut, IIRC, can do a periodic battery test by putting it offline, > > using the battery, for a predetermined length of time, weekly, > > monthly etc, > > We definitely don't want that in this instance either! Why not?

I'm using nut-2.8.2 on FreeBSD 14.2 with an Eaton 5PX2200RT Five minutes after starting nut, I get this message within my ssh session: UPS heartbeat on battery It is not clear to me why it reports that. Here is the full output of a restart: [18:12 gw01 dvl ~] % sudo service nut restart Stopping nut. Waiting for PIDS: 2553. Network UPS

On Mon, 3 Apr 2017, Gene Heskett wrote: >> > Nut, IIRC, can do a periodic battery test by putting it offline, using > the battery, for a predetermined length of time, weekly, monthly etc, We definitely don't want that in this instance either! (Unless it is a dual PS server.) We want the ALARM that the nut driver is generating, and upsd is passing on - to be acted on in some

The problem with computers - they do what you tell them to, not what you might want them to. Here your heartbeat.dev literally tells the emulation driver to set ups.status=OL, wait 300s, set it to OB, wait 300s, repeat. So NUT reporting that the heartbeat UPS became on-battery 5 minutes after start means these pieces are doing their job correctly and talking to each other well. Jim On Sat, Mar

Hello, I set up a FreeBSD 8.2 system with nut 2.6.1 and a Powerware 5115 connected by RS-232. I expected this setup to shut down before running out of battery power, but I either missed some important configuration or something else went wrong: The syslog says: Jan 9 05:03:42 b1 upsmon[67752]: UPS upsb1 at localhost on battery Jan 9 05:04:42 b1 upsmon[67752]: UPS upsb1 at localhost on line

On 03/04/17 22.11, Gene Heskett wrote: > On Monday 03 April 2017 14:13:08 Stuart D. Gathman wrote: > > Back on the mailing list, where such belongs. > [cuuut] >> We want the ALARM that the nut driver is >> generating, and upsd is passing on - to be acted on in some way by >> upsmon. Which NOTIFYCMD is run when there is an ALARM? [cuuut] I dont think any NOTIFYCMD

Hi all! I have a nut 2.4.1 on FreeBSD 7.1 i386. UPS model is IPPON smart smart power pro 2000. When i try to see battery charge, in output it have not such variable, and i can't control other servers (Win2k3 + WinNUT) because they not knows about current battery charge. How i can solve that problem? Thanks! upsc IPPON at localhost:54672 --------------------------- battery.voltage: 27.50

hello list, i add a new diguim card in my server i use asterisk 1.4 with zaptel .conf after that i can't receive the calls in my server with outbound calls there is no problem i have all time this error msg [Feb 20 18:15:48] WARNING[28582]: chan_zap.c:2404 pri_find_dchan: No D-channels available! Using Primary channel 140 as D-channel anyway! [Feb 20 18:15:52] WARNING[28582]:

Hi, I'm currently using a Belkin UPS ( http://www.belkin.com/au/IWCatProductPage.process?Product_Id=137904) with nut, and my notify script doesn't receive a low battery warning. I receive ONBATT and ONLINE, but not any battery low message. I've run upsmon -D and I've seen it polls the ups.status property. The problem seems to be that this UPS doesn't put LB (I guess that