similar to: 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

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

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

I finally got this working, for the sake of anyone else who comes across this thread with a similar problem: Since NOTIFYCMD was working fine with bash scripts, I had it point to a bash script which I used to call my python script, and I set up the bash script to capture errors and write them to a log file: /etc/nut/ups-log.py > /home/pi/Documents/scripts/mylog 2>&1 I didn't realize

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

I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath. Is there something I am missing? Please see attached. Dan -------------- next part -------------- An HTML attachment was

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

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

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

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

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

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

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

https://bugs.freedesktop.org/show_bug.cgi?id=38984 Summary: xorg-nouveau: Segfault after gdm3 login, EQ overflowing, GeForce 8600 GT (backtrace attached) Product: xorg Version: 7.6 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component:

Thought I'd follow up in case someone else runs into this issue. In the end what worked for me was tweaking the udev rules. I have had no USB disconnects or stale data warnings so far. I only used one rule for my UPS: # /etc/udev/rules.d/62-nut-usbups.rules SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" # TrippLite # e.g. TrippLite SMART1500LCD - usbhid-ups

Hi there, Seeing an odd behaviour when running upsmon -c fsd to test my Raspberry Pi (running Jesse Lite) setup as a upsmon master, attached via USB to an APC Back-UPS XS1300. The Raspberry Pi is plugged into the Master outlet on the APC. The UPS clicks onto battery (and the fan spins up) for a few minutes, then resets, then repeats again, while finally remaining on AC power afterwards. The

Dear all, Do you have come acrross with this issue. My ss7 link get fluctuating. It use chan_ss7 version 1.0.95-beta. I have 8 E1s running on a DL380 server with Digium E1 cards ( 4 port cards). This enable to have calls from sip to ss7 and vice versa. However ss7 links are not stable. linkset siuc, link l1, schannel 1, sls 0, NOT_ALIGNED, rx: 1, tx: 2/4, sentseq/lastack: 127/127, total