similar to: How to stop nut broadcast messages?

Hi all, I've not been able to find the answer to my timer problem in the faq or the archives. (or google) Basically, I can't get timers to fire. They fire ignoring the timer value, as if the timer was set to 0. I'm using the OpenFiler distribution, patched to the latest and greatest. upsmon 2.2.2 When I pull the power plug, I see the text "Im In Battery" instantly, instead

On Thu, 8 Jun 2017, Robbie van der Walle wrote: > After the first test and the NAS is restarted I had to change the > setting battery.charge.low again to 80? Does the NAS DSM reset battery.charge.low to 10 or is it internal to the UPS? You will have to experiment by disconnecting the UPS control lead from the NAS and connecting it (if possible) to the Mac. After setting to 80 and a

Hello dear all, I try to use NUT for windows (not WinNUT), and stuck with launching NOTIFYCMD. On any event marked as SYSLOG+WALL+EXEC syslog entry appears, popup window appears, but NOTIFYCMD script doesn't run. If I run upsmon.exe in cmd (i. e. not as a service) everything works fine. Here is my upsmon.conf: MONITOR central at 10.35.0.180 1 user password slave MINSUPPLIES 1 SHUTDOWNCMD

hello, i've got a problem with the notifycmd here is a part of my upsmon.conf : NOTIFYCMD /usr/local/ups/bin/nut_notify NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "UPS %s is on battery" NOTIFYMSG REPLBATT "The UPS %s battery is bad and needs to be replaced" NOTIFYMSG LOWBATT "UPS %s is being shutdown by the master" NOTIFYMSG FSD

Hi All, I'm using a recent post 2.6.1 build provided by Fred (executables have modified date of 9th August) I have configured upsmon.conf with :- NOTIFYCMD C:\NUT\etc\NotifyCmd.bat and :- NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG LOWBATT SYSLOG+EXEC NOTIFYFLAG FSD SYSLOG+EXEC NOTIFYFLAG COMMOK SYSLOG+EXEC NOTIFYFLAG COMMBAD SYSLOG+EXEC

Hi everyone, new to the list but a long time nut user. I've tried a couple of times to set up a timer to avoid getting annoying messages when the system goes on battery for only a few seconds. in uppsched.conf I added this at the bottom: AT ONBATT * START-TIMER onbattwarn 60 AT ONLINE * CANCEL-TIMER onbattwarn What am I missing? it still doesn't wait before alerting me.

Hi, I'm attempting to use the UPS network tools. I'm sure I got the configurations worked out as I get notified when the ups goes on battery and back online. I am having problems with upssched. I have the following in my upssched.conf: CMDSCRIPT /usr/local/ups/sbin/upssched-cmd AT ONBATT * EXECUTE onbatt The problem I have is that is seems like the script in CMDSCRIPT never gets

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>

On Fri, 9 Jun 2017, Robbie van der Walle wrote: > ... and also still open is the notification on the Mac. If notify-send is available on the Mac, then perhaps this will work: In upsmon.conf on the Mac you need NOTIFYCMD /usr/sbin/upssched (or wherever this goes on a Mac) NOTIFYFLAG ONBATT SYSLOG+EXEC In upssched.conf you need CMDSCRIPT /usr/sbin/upssched-cmd (or wherever this

Ok, I am running NUT in dummy mode. I have added a new ups in ups.conf [dummy] driver = dummy-ups port = upsc.dev desc = "dummy ups for testing purposes" upsc.dev has been generated by exporting the Elit configuration. I have added the monitor line in upsmon.conf and the "exec" flags (all the events) MONITOR dummy at artu 1 user pass master SHUTDOWNCMD

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120104/34be491b/attachment.html>

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

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

Ah! So I can detect the source UPS in the upssched.conf and pass it as a distinct event to the shell script. That sounds like an excellent approach. Thanks! GMH From: O'Shaughnessy, Mike [mailto:Mike.OShaughnessy at gd-ms.com] Sent: Tuesday, October 31, 2017 12:46 PM To: Garrett Michael Hayes <Garrett at VerbalImaging.com>; nut-upsuser at lists.alioth.debian.org Subject: RE: Email

On Feb 9, 2015, at 6:48 AM, PERE (yahoo.es) <pererivers at yahoo.es> wrote: > 0.028188 Can't set USB configuration: could not set config 1: Device or resource busy > 0.029246 detached kernel driver from USB device... > 0.030559 USB device [0001:0000] opened > 0.866216 read: (8 bytes) => 03 00 00 00 00 00 00 00 > 0.866413 reply[0] = 0x03

I have only RS-232 on the box (meanwhile, it was manufactured on march of 2011) Here is my configs: nut.conf: * * MODE = netserver ups.conf: * * [KIN1500] driver = powercom port = notUsed desc = "Powercom KING PRO KIN-1500AP RM" upsd.conf: * * LISTEN 192.168.1.2 3493 upsd.users: * * [monuser] password = xxxxxxxx upsmon master

On Jun 29, 2017, at 6:52 AM, Andrea de Lutti wrote: >>> Anyway I still not receive any email on any test (power cord disconnected and/or reconnected for example) >> >> Oh, I misinterpreted "working script" as a script that was sending email, rather than work-in-progress. Does that same command work from the command line? Can you add something like "logger"

Hello. I've tried to configure Windows (complete port, Beta): Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port but have no luck. Here is my config files: *nut.conf:* MODE = netserver *ups.conf:* [PW5115] driver = bcmxcp_usb port = notUsed desc = "PowerWare 5115" *upsd.conf:* LISTEN 192.168.1.12 3493 *upsd.users:* [monuser]

Greetings Gentlebeings, I have started deploying a number of NUT instances on Raspberry Pi machines (Raspbian Jessie) across my network. The purpose of these "nutcases" as we refer to them is to monitor the status of the UPSs supporting our network switching infrastructure and notify us of power and battery events via email. No shutdown or other actions are required. Everything is