Displaying 20 results from an estimated 20000 matches similar to: "NOTIFYCMD not running"
2020 Feb 11
1
NOTIFYCMD not running
> When you run that command, does "some text" appear in the system log?
When I run Documents/scripts/ups-log.py manually I do see the expected text
echo'ed to the command line. It actually appends to a Google Sheet, not
the internal log files.
When I would expect to see it triggered by NOTIFYCMD, I don't see any text
printed and nothing shows up at the google sheets. If
2020 Feb 12
1
NOTIFYCMD not running
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
2020 Feb 11
1
NOTIFYCMD not running
>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.
Thanks for the response, can you link to it? I'm not finding it in the
search. I'm not using /sbin/upssched, I have NOTIFYCMD set up as:
NOTIFYCMD /home/pi/Documents/scripts/ups-log.py
and it's not commented out.
On Tue, Feb 11, 2020
2020 Feb 11
1
NOTIFYCMD not running
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
2020 Feb 11
1
NOTIFYCMD not running
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
2014 Apr 07
0
snmp-ups sends status "OL OB" on HP R3000 UPS with AF465A management card [UPDATE]
Hello Arnaud,
On 05/04/14 22:01, Arnaud Quette wrote:
> Philippe, Ivan,
>
> please see https://github.com/networkupstools/nut/issues/118
> and send back your data.
I've pasted the requested files in github, but the auto-formatting may
have damaged them, so here they are.
Also, when I ran gen-snmp-subdriver.sh, it gave me the following message:
2014 May 21
0
upssched timer configuration with redundant UPSes ?
Hello list,
I have the following hardware setup:
- HP C7000 enclosure, with 4 blade servers
- two power supply modules in the enclosure (one is enough to sustain
the 4 blades)
- two UPSes, each one feeding one of the enclosure power supplies
I would like to configure NUT to initiate an early shutdown of that
environment only if *both* UPSes are on battery.
I've created the 2
2014 Jun 23
0
Multiple servers connected to the same UPS
On 23/06/14 04:32, Stan Gammons wrote:
> Can one have a single UPS powering multiple servers and have them all
> shutdown in an orderly fashion pending a power loss? It seems as
> though this is possible from what I gathered from the docs, but I've yet
> to make this work on an OpenBSD and FreeNAS machine that are powered
> from the same UPS. The master server that the UPS
2014 Mar 11
2
snmp-ups sends status "OL OB" on HP R3000 UPS with AF465A management card [UPDATE]
Further information on this issue, attn. Arnaud Quette:
Here is the result of a test I made a few days ago. I've pulled the
input plug on the UPS and watched the 3 critical OIDs through a MIB browser:
- 1.3.6.1.4.1.232.165.3.4.5.0 goes from 3 (OL) to 5 (OB)
(as expected => good)
- 1.3.6.1.4.1.232.165.3.7.3.0 stays at 1 (OB)
(=> seems meaningless)
- 1.3.6.1.4.1.232.165.3.7.4.0
2014 Feb 27
0
snmp-ups sends status "OL OB" on HP R3000 UPS with AF465A management card [UPDATE]
Additional question: I noticed on the HP Website that the latest version
of "CPQPOWER.MIB" (1.76, dated Sept. 19, 2013) was more recent than the
related file (./drivers/compaq-mib.c) in the NUT driver.
Is the MIB structure as implemented on the management card perhaps no
longer in line with the NUT driver ?
The latest MIB file can be downloaded from the following URL:
2011 Sep 02
2
NUT 2.6.1+ Windows 2008 R2 - NOTIFYCMD not being called
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
2007 Jan 17
1
NOTIFYCMD not running
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
2016 Oct 06
2
NOTIFYCMD doesn't work at all... not fully
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
2012 Apr 11
1
NOTIFYCMD doesn't work from Windows service
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
2020 Jan 28
1
Timer doesn't appear to start
The time and upssched-cmd are now working.
Here are the issues I had:
1) Did not define NOTIFYCMD in upsmon.conf Added NOTIFYCMD /sbin/upssched
2) Added +EXEC to NOTIFYMSG rules I am using
3) Change ownership of upssched.conf to my nut user nutmom. I had added
nutmon to the group nut but it didn't work.
Thanks again for all your guidance
On Tue, Jan 28, 2020 at 7:00 AM
2006 Jul 11
2
notifycmd problem
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
2016 Oct 06
0
NOTIFYCMD doesn't work at all... not fully
> 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,
2014 Apr 05
3
snmp-ups sends status "OL OB" on HP R3000 UPS with AF465A management card [UPDATE]
Philippe, Ivan,
please see https://github.com/networkupstools/nut/issues/118
and send back your data.
cheers
Arno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140405/682f10dd/attachment-0001.html>
2013 Apr 11
1
NOTIFYCMD and SHUTDOWNCMD do not work until Nut is restarted
Hi everybody,
I installed and configured Nut 2.4.3 on Debian Squeeze, using package.
It monitors an MGE Pulsar 1500 UPS in standalone mode.
Here are parts of upsmon.conf :
SHUTDOWNCMD "/bin/bash /root/extinction.sh >> /var/log/ups/ups.log 2>>&1"
NOTIFYCMD "/bin/bash /usr/sbin/alerte.sh"
[...]
NOTIFYFLAG ONBATT SYSLOG+EXEC
At startup, driver, upsd and upsmon
2015 Sep 22
2
NOTIFYCMD shell script problem driving me NUTS
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