similar to: Another New User Question - Notify Script Not Running

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?

Hello All, I'm trying to establish a MASTER SLAVE configuration of UPS using NUT Driver. I'm able to shutdown the master after UPS is on BATTERY ( POWER BLACKOUT) .However I'm trying to shutdown the other SLAVE MACHINES BEFORE MASTER. But at the remote side ( Slaves ) shutdown after UPS blackout does not happen. My configuration in Master are /usr/etc/upsd.users

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

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

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 have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

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

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

Hello NUT Team! I am testing the early shutdowns in NUT 2.6.5-1 package for Windows (Windows 7 x64). My configuration files: upsmon.conf RUN_AS_USER upsmon MONITOR upsa at 192.168.10.200 1 upsmon pass master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD "upssched.exe" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG

Hi, I’ve posted my question on Superuser.com but not had any replies in 2 weeks, so I guess no-one there knows anything about NUT. https://superuser.com/questions/1441153/how-to-shutdown-macos-mac-osx-from-network-ups-tools-client-nut <https://superuser.com/questions/1441153/how-to-shutdown-macos-mac-osx-from-network-ups-tools-client-nut> I’m looking for help in shutting down my iMac on

Roger, Thanks for the idea to add additional items to the notifyflag. That proved the monitor was indeed working as expected and led me to find that my script had myriad issues when run under the nut user. All remedied now. As I progress, I may well end up migrating to the upssched. As a newbie I was simply following the documented "simple" way described here

On 2019-12-16 05:34, Roger Price wrote: > On Sun, 15 Dec 2019, Phil Stracchino wrote: > >> I switched a while back to a Cyberpower PR3000LCDRTXL2U UPS with an >> external battery chassis. We've lost power twice since I installed it, >> and both times, the UPS has killed power to everything while still >> indicating 80% capacity before NUT has even initiated

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

hello, I installed with NUT UPS MGE Pulsar Evolution 2200 all orders of arrest, interrogation etc etc ... UPS work well However, I have a problem with the order in NOTIFYCMD upsmon.conf that not run ... I created a script that generates a simply log I indicated in upsmon.conf NOTIFYCMD / home / nut / alert_ups.sh below my upsmon.conf RUN_AS_USER nut MONITOR pulsar at localhost 1 admin1

Hi Charles, Thanks for your help. Seems to be mostly ok except am getting error access denied. See below. I see from searching this is a common error but so far I can't find a fix. This is how I configured things before make and install. created group nut nut:x:103: created system user ups with group nut. ups:x:123:103::/home/ups:/bin/bash Create statepath directory. sudo mkdir -p

On Thu, 8 Jun 2017, Robbie van der Walle wrote: > The "upsrw" command contacts upsd, so it sounds like you should be able to add a user to upsd.users on the NAS, and then run something like > this on the Mac: > > ??upsrw -s battery.charge.low=80 -u upsmaster -s sekret UPS at synology > > Per?http://networkupstools.org/docs/man/upsd.users.html?,

Yes, that was the power off test. However the upssched-cmd script gave absolutely no signs of activity. Even it's logger lines don't show up in journalctl. No any permission error messages - nothing. Only the 2 messages from upsmon - on battery and then on line power. Here is the nut-report: http://www.filehosting.org/file/details/518300/NUT.report --- George Anchev On Tue, Oct 27,

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