similar to: NOTIFYCMD and SHUTDOWNCMD do not work until Nut is restarted

Bonjour Openbsd 6.6 - NUT 2.7.4 from source - Eaton Ellipse Pro Installation OK upsc OK upsmon -c fsd OK (shutdown effective) I suppose mistake in upsmon config : # upsmon.conf MONITOR ellipse at localhost 1 upsmon pass master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -p -h now 'Sylvebarbe killed'" POLLFREQ 60 POLLFREQALERT 60 HOSTSYNC 120 DEADTIME 180 POWERDOWNFLAG

*** solved *** Using http://rogerprice.org/NUT/ConfigExamples.A5.pdf and upsrw, my BSD shutdown at low power of 80% Bye

Hi all! All was working fine with all my UPSs and Windows 10 machines, NUT will notify events to NOTIFYCMD (which point to a .bat script to show messages) and finally will shutdown the system via SHUTDOWNCMD, that is another .bat file that simply uses shutdown.exe to hibernate the system. Today I upgraded all my machines to the latest Creators Update, and now NOTIFYCMD works as I can see

I have the nut package installed and running - everything perfect (or so I thought). My syslog shows everything looks great, and pulling the UPS plug for a few seconds triggers a WALL event, but not my notifycmd (which should write a test message to syslog). Can someone offer insight/ideas as to why my NOTIFYCMD is not running? Thanks, Michelle ----------------------- Extract from messages

hi everybody I'm looking for pager.txt which upsmon.conf mentions of, but could not find it anywhere including the sources? I'd presume that via NOTIFYCMD I could get the stuff emailed, does anybody have more experience solving such problem? regards

I have been racking my brains on this and just can't figure it out. In upsmon.conf I defined NOTIFYCMD as /etc/nut/notifyme.sh I did CHMOD 755 /etc/nut/notifyme.sh I put a line in /etc/nut/notifyme.sh to echo a simple message when it is called and the message never shows on an open terminal whenever I pull the plug to the UPS. I do, however get a WALL broadcast message to that open

After some testing, I notice that my NOTIFYCMD script seems to work if I call it as user 'john' (that's me) but if I call it as 'root' it does not work. So is there a permissions issue ? I have permission on the file set to 755. I see there is a variable in upsmon.conf called RUN_AS_USER. I do not have this defined. Does this variable need to be defined ? I presume that if

Either I am missing something or I am really STUPID. 1. I have added a user, named nutmon, to the nut group. 2. In upsmon.conf I have set RUN_AS_USER nutmon . 3. I have NOTIFYCMD /etc/nut/notifyme.sh and it is set as 755, so should be executable by everyone. 4. I have the NOTIFYFLAG set as SYSLOG+WALL+EXEC, so the shell should execute. This is the shell script : #!/bin/bash # # NUT NOTIFYCMD

On Tue, Sep 22, 2015 at 9:56 AM, John Hart <jsamcr at gmail.com> wrote: > notify-send notify-send needs a DBUS_SESSION_BUS_ADRESS to work right. Look around for code snippets to get this. -- -- Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL:

This small patch makes the alert text generated by upsmon available in the environment of the CMDSCRIPT child of upssched. This is needed as the command line argument to upssched is not passed through when it calls CMDSCRIPT. --- upsmon.c 2016-04-25 20:17:44.392925130 -0600 +++ upsmon.c+ 2016-04-25 20:18:21.512871526 -0600 @@ -151,6 +151,7 @@

> On Oct 6, 2016, at 6:15 AM, Stefan Fr?chtenicht wrote: > > when i execute the upsnotify.sh as root, then it works great. eMails and SMS are incoming. > But when i for e.g. pull out the ups from power, then there will be only emails and NO SMS. Why? > NUT runs the notify script as the "nut" user on many systems, including Debian. Check to see if $PATH is set the same,

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

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, I'm setting up NUT on a raspberry pi 4, following the guide here: https://melgrubb.com/2016/12/11/rphs-v2-ups/ OS version: Raspian Buster NUT version: 2.7.4.8 Installed via: apt package install Device: Legrand Keor Multiplug connected via USB The problem I am experiencing is that *NOTIFYCMD* never runs. I can connect to the device via *upsc*, and I receive WALL messages when I connect

On Sep 22, 2015, at 11:27 AM, Thomas Charron <twaffle at gmail.com> wrote: > > On Tue, Sep 22, 2015 at 9:56 AM, John Hart <jsamcr at gmail.com> wrote: >> notify-send > > notify-send needs a DBUS_SESSION_BUS_ADRESS to work right. Look around for code snippets to get this. Ah, that notify-send. Another option is to launch the PyNUT app in your xsession (or

Hi there, i have a problem with the NOTIFYCMD in the upsmon.conf file. My line in the config looks like this: NOTIFYCMD "/etc/nut/upsnotify.sh" Now this ist my "/etc/nut/upsnotify.sh": #!/bin/bash EMAIL='mail at domain.de' SMS1='+49123456789' SMS2='+491987654231' #eMail versenden echo -e "Die USV mit dem Namen '$UPSNAME' hat seinen

Philippe Andersson I think tried to respond on this thread but all I see is your corporate email signature? I did some more troubleshooting tonight. TL;DR at the end. First, confirmed that NOTIFYCMD is in fact firing. So I changed it to: NOTIFYCMD logger "NOTIFYCMD FIRED!" followed by: sudo service nut-client restart and that message does show up in /var/log/messages when I pull the

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

I just went through the same issue. Take a look at my thread. Double check that upsmon.conf:NOTIFYCMD /sbin/upssched is not still commented. On Tue, Feb 11, 2020 at 7:00 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to > nut-upsuser at alioth-lists.debian.net > > To subscribe or unsubscribe via the World Wide