similar to: Good Day NUT

On Mon, 15 May 2017, Dinow Hsieh wrote: > ==> I have tried this command "upsdrvctl shutdown" as below results (However the UPS still sustain the power) > > ??? Network UPS Tools - UPS driver controller 2.7.1 > ??? Network UPS Tools - Generic HID driver 0.38 (2.7.1) > ??? USB communication driver 0.32 > ??? Using subdriver : PowerCOM HID 0.4 > ??? Initiating UPS

Good Day Roger Price AA. Hi, Normally one would expect the UPS to disconnect it's power outlets after the default ups.delay.shutdown = 20 seconds. ==> I got it. I tried to command "upsdrvctl shutdown" on both line-mode and battery-mode ==> But ups do not disconnect its outlets power ----------------------------------------------------------------------------------- BB.

Good Day Roger AA. notice that during the test, you have little or no load, since despite being in state OB DISCHRG the battery.charge is still 100. It's best to perform such tests with a dummy load such as a table lamp and an old fashioned incandescent 100 watt bulb. ==> Yes. I got it and try to ascend load as below results dinow-All-Series:~# upsc pcmups Init SSL without

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

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

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

Good Day Roger AA. notice that during the test, you have little or no load, since despite being in state OB DISCHRG the battery.charge is still 100. It's best to perform such tests with a dummy load such as a table lamp and an old fashioned incandescent 100 watt bulb. ==> Yes. I got it and try to ascend load as below results dinow-All-Series:~# upsc pcmups Init SSL without

On Fri, 12 Jul 2019, David White wrote: > Hello, thanks, and sorry for the delay in getting back. I am running the > script and have move the comment from one D= line to the other. I am, > however, seeing some errors written to the console. They are from line > 64-65 of the script. > > Regarding line 64, I have no /usr/sbin/ups* and suspect the proper > location on my

I'm trying to better understand OffDelay and OnDelay: http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments My server requires ~3? minutes to shut itself down. Considering this I'm comfortable setting OffDelay to 300 (five minutes). How does this work in conjunction with the UPS hardware? Does NUT immediately send a command to the UPS to wait for 300 seconds and then shut

Well it is the season for storms and power outages here in the US PNW. I noticed that today when the power went out, NUT mostly did what I hoped/wanted. But it did not actually turn off the UPS at all. The UPS kept beeping and I had to turn it off manually. I thought that NUT would handle this. But perhaps it cannot for my unit? Or perhaps I have things improperly configured? Any suggestions?

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

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

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

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

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 Jul 9, 2019, at 12:22 PM, David White wrote: > > So I guess I am wondering if this is related to my problem. I have no idea how the blazer_usb driver works. For the most part, NUT drivers ending in “_usb” (including blazer_usb) do not need a serial device node in /dev. They use libusb to talk directly to the UPS. (If you can reliably read the UPS status with upsc, then the connectivity

> > > > MONITOR dummy at artu 1 user pass master >> SHUTDOWNCMD "/sbin/shutdown -h +0" >> NOTIFYCMD /usr/local/bin/upssched-script >> > > Hi, As far as I can see, what you are getting in syslog corresponds > correctly to what you have specified. You have specified that upsmon is to > call upssched-script _directly_. This means that the argument

Hello guys Yesterday i started do configure my Mustek Powermust650 with nut using the megatec_usb driver. Everything works fine except for the mailing when something happens. My upsmon looks like this: MONITOR powermust650 at localhost 1 local controller master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /root/upsmailer POLLFREQ 10 POLLFREQALERT 5 HOSTSYNC 15

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