search for: upsnotify

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 Status ge?ndert!\n\nAktueller Status: '$NOT...

...nected [root at mythtv rules.d]# upsdrvctl start Network UPS Tools - UPS driver controller 2.8.2 Network UPS Tools - Generic HID driver 0.53 (2.8.2) USB communication driver (libusb 1.0) 0.47 libusb1: Could not open any HID devices: insufficient permissions on everything No matching HID UPS found upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it Driver failed to start (exit status=1) [root at mythtv ~]# nut-scanner Cannot load USB library (libusb-1.0.so) : file not found. USB search disabled. Cannot load SNMP library (libnetsnmp.so) : file not fou...

...rules.d]# upsdrvctl start >Network UPS Tools - UPS driver controller 2.8.2 >Network UPS Tools - Generic HID driver 0.53 (2.8.2) >USB communication driver (libusb 1.0) 0.47 >libusb1: Could not open any HID devices: insufficient permissions on everything >No matching HID UPS found >upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it >Driver failed to start (exit status=1) > >[root at mythtv ~]# nut-scanner >Cannot load USB library (libusb-1.0.so) : file not found. USB search disabled. >Cannot load SNMP library (libnetsnmp....

On 11/15/24 15:57, Orion Poplawski wrote: > This is on EL9 with 2.8.2: > > nut-monitor[150988]: upsnotify: failed to notify about state 2: no > notification tech defined, will not spam more about it > > I have no idea what this really means. I think it has something to do about > systemd startup notification, but I'm not really sure. Can someone enlighten me? > > Is this somet...

...river (libusb 1.0) 0.47 Nov 9 12:18:00 mythtv nut-driver at cyberpower[18885]: libusb1: Could not open any HID devices: insufficient permissions on everything Nov 9 12:18:00 mythtv nut-driver at cyberpower[18885]: No matching HID UPS found Nov 9 12:18:00 mythtv nut-driver at cyberpower[18885]: upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it Nov 9 12:18:00 mythtv nut-driver at cyberpower[18861]: Driver failed to start (exit status=1) Nov 9 12:18:00 mythtv nut-driver at cyberpower[18861]: Network UPS Tools - UPS driver controller 2.8.2 Nov...

...An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240308/8535cf65/attachment.htm> -------------- next part -------------- Mar 08 07:48:59 WiringCloset usbhid-ups[6529]: Startup successful Mar 08 07:48:59 WiringCloset usbhid-ups[6529]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it Mar 08 07:49:00 WiringCloset dummy-ups[6531]: Startup successful Mar 08 07:49:00 WiringCloset dummy-ups[6531]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about...

This is on EL9 with 2.8.2: nut-monitor[150988]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it I have no idea what this really means. I think it has something to do about systemd startup notification, but I'm not really sure. Can someone enlighten me? Is this something that anyone should care a...

...usb 1.0) 0.47 >Nov 9 12:18:00 mythtv nut-driver at cyberpower[18885]: libusb1: Could not open any HID devices: insufficient permissions on everything >Nov 9 12:18:00 mythtv nut-driver at cyberpower[18885]: No matching HID UPS found >Nov 9 12:18:00 mythtv nut-driver at cyberpower[18885]: upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it >Nov 9 12:18:00 mythtv nut-driver at cyberpower[18861]: Driver failed to start (exit status=1) >Nov 9 12:18:00 mythtv nut-driver at cyberpower[18861]: Network UPS Tools - UPS driver controller 2.8.2 &...

...driver controller 2.8.2 Network UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2) select with socket: Invalid argument Detected Smart-UPS 3000 RM on host 192.5.37.78 (mib: apcc 1.60) Initiating UPS shutdown [upstop] nut_snmp_set: can't set .1.3.6.1.4.1.318.1.1.1.6.1.1.0: Timeout Shutdown failed! upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it Driver failed to start (exit status=1) Network UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2) select with socket: Invalid argument Detected Smart-UPS 3000 RM on host 192.5.37.79 (mib: apcc 1.60) Initiating...

...k UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2) > select with socket: Invalid argument > Detected Smart-UPS 3000 RM on host 192.5.37.78 (mib: apcc 1.60) > Initiating UPS shutdown > [upstop] nut_snmp_set: can't set .1.3.6.1.4.1.318.1.1.1.6.1.1.0: Timeout > Shutdown failed! > upsnotify: failed to notify about state 4: no notification tech defined, > will not spam more about it > Driver failed to start (exit status=1) > Network UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2) > select with socket: Invalid argument > Detected Smart-UPS 3000 RM on host 192.5.37.79 (mi...

...: trying classic sysOID matching method with 'ietf' mib 234.260031 [D2] Found entry, not a template 1.3.6.1.2.1.33.1.1.2.0 234.260033 [D2] Testing ups.model using OID 1.3.6.1.2.1.33.1.1.2.0 240.266446 No supported device detected at [myups] (host 10.186.29.30) 240.266779 upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it Can kindly someone help me to add my UPS. Model: *ABB PowerValue 11 RT G2 IEC * https://new.abb.com/ups/systems/single-phase-ups/powervalue-11-rt Thanks a lot MJ -------------- next part -------------- An H...

...to /etc/nut/ups.conf But get the following error: # upsdrvctl start Network UPS Tools - UPS driver controller 2.8.2 Network UPS Tools - Generic HID driver 0.53 (2.8.2) USB communication driver (libusb 1.0) 0.47 libusb1: Could not open any HID devices: no USB buses found No matching HID UPS found upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it Driver failed to start (exit status=1) Any ideas?

On Fri, 29 Mar 2024, Dan Grostick wrote: > It is consistently happening 14-15 minutes after starting. Please see attached > upssched-cmd and upssched.conf. I don't have a upssched.cmd. The binary > upssched is used. After the heartbeat failure, is upsd still running? Does the command "upsc -L" report the UPS's? If you use systemd, what does the command

...owing error: > > # upsdrvctl start > Network UPS Tools - UPS driver controller 2.8.2 > Network UPS Tools - Generic HID driver 0.53 (2.8.2) > USB communication driver (libusb 1.0) 0.47 > libusb1: Could not open any HID devices: no USB buses found > No matching HID UPS found > upsnotify: failed to notify about state 4: no notification tech defined, > will not spam more about it > Driver failed to start (exit status=1) > > Any ideas? > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > h...

...at apcupskelder[1068]: Network UPS Tools - Generic HID driver 0.52 (2.8.1) nov 01 01:26:40 MinipcLG2 nut-driver at apcupskelder[1068]: USB communication driver (libusb 1.0) 0.46 nov 01 01:26:41 MinipcLG2 usbhid-ups[1141]: Startup successful nov 01 01:26:41 MinipcLG2 usbhid-ups[1141]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it nov 01 01:26:41 MinipcLG2 nut-driver at apcupskelder[911]: Network UPS Tools - UPS driver controller 2.8.1 nov 01 01:26:41 MinipcLG2 systemd[1]: Started nut-driver at apcupskelder.service - Net...

...river (libusb 1.0) 0.46 Driver failed to start (exit status=1) journalctl -xe <<Results... x is the PID and I strripped before "usbhid-ups">> usbhid-ups[x]: No matching HID UPS found usbhid-ups[x]: [D5] send_to_all: SETINFO driver.state "cleanup.exit" usbhid-ups[x]: upsnotify: notify about state 4 with libsystemd: was requested, but not running as a service unit now, will not spam more about it usbhid-ups[x]: upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it [I then repeated from upsdrvsvcctl reconfigure but no differe...

...drvctl shutdown apcupskelder > Network UPS Tools - UPS driver controller 2.8.1 > Network UPS Tools - Generic HID driver 0.52 (2.8.1) > USB communication driver (libusb 1.0) 0.46 > select with socket: Invalid argument > Can't claim USB device [051d:0002]@0/0: Entity not found > upsnotify: failed to notify about state 4: no notification tech defined, > will not spam more about it > Driver failed to start (exit status=1) > ``` > > ``` > erik at MinipcLG2:/$ sudo nut-scanner -U > Scanning USB bus. > [nutdev1] > driver = "usbhid-ups" >...

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

...erik at MinipcLG2:/$ sudo upsdrvctl shutdown apcupskelder Network UPS Tools - UPS driver controller 2.8.1 Network UPS Tools - Generic HID driver 0.52 (2.8.1) USB communication driver (libusb 1.0) 0.46 select with socket: Invalid argument Can't claim USB device [051d:0002]@0/0: Entity not found upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it Driver failed to start (exit status=1) ``` ``` erik at MinipcLG2:/$ sudo nut-scanner -U Scanning USB bus. [nutdev1] driver = "usbhid-ups" port = "auto" vendorid =...

...r/local/ups # cat etc/upsd.conf LISTEN 127.0.0.1 LISTEN 192.168.0.10 srv:/usr/local/ups # --- srv:/usr/local/ups # cat etc/upsmon.conf # RUN_AS_USER ups MONITOR npower at localhost 1 admin karamba master MINSUPPLIES 1 SHUTDOWNCMD "/usr/local/ups/sbin/upsshut" NOTIFYCMD /usr/local/ups/bin/upsnotify POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG LOWBATT SYSLOG+EXEC NOTIFYFLAG FSD SYSLOG+EXEC NOTIFYFLAG COMMOK SYSLOG+EXEC NOTIFYFLAG COMMBAD SYSLOG+EXEC NOTIFYFLAG SHUTDOWN SYSLOG+EXEC NOTIFY...