search for: upsnotifi

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

Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB. I updated the system yesterday with all the latest Fedora packages. Now NUT will not run. Chasing the issue through the layers, I come to this: ===================== [root at mythtv rules.d]# upsc cyberpower Error: Driver not connected [root at mythtv rules.d]#

Did the upgrade by chance install/alter any udev rules causing the UPS devices to now have incorrect permissions? And what user is nut running as? On November 9, 2024 9:58:57 AM EST, Bill Gee <bgee at campercaver.net> wrote: >Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB. > >I updated the system yesterday

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

Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS seeing the UPS at a low level. I looked through /dev/ but did not see a device that jumps out as the UPS. ===================== [root at mythtv rules.d]# dmesg | grep -i 0764 [ 2.021485] usb 1-1.8: New USB device found, idVendor=0764, idProduct=0501, bcdDevice= 0.01 [ 2.049515]

I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit (Debian 12) with success. When I take that same configuration to a PI 3B running bookworm 32 bit, compile from source, use the same files from /etc/nut, I get a 'nut-monitor ups at localhost Connection refused. usbhid-ups and dummy-ups are running at the time. What should I be looking for? Dan -------------- next

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 about? -- Orion Poplawski he/him/his -

Check /dev/hidraw6, as noted in your dmesg output (and any other *hid* devices under /dev). User nut has almost zero privs to devices unless a udev rule changes the perms on the dev for nut . . . On November 9, 2024 1:25:29 PM EST, Bill Gee <bgee at campercaver.net> wrote: >Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS

I'm still digging into this but thought I'd post what I have so far in case there's a known issue that's easily fixed. I'm using the version of NUT that's in the ports tree (see the info at the bottom). Using the SNMP drivers to talk with two ACP SmartUPSs. NUT is functional about monitoring and initiating host shutdown. However, when it comes time to shut down the UPSs

Hello, Thanks for the report and sorry about any complications. A few first questions: * is this setup known to have been working with earlier NUT releases (e.g. same OS and devices, older NUT - can try with a custom build of older tags)? Is this a regression, or we never knew the correct mappings for timeouts and/or shutdown commands used by this model? * is there the `select` error when

Hi Team While i;m searching on the internet about UPS SNMP monitoring , I found this NUT server. Thank God, But sad news is that my UPS is not listed in the compatibility list. But I download NUT server on my ubuntu node and just discover it sudo /lib/nut/snmp-ups -DD -a ups unfortunately got the below error message. 228.253598 [D2] Testing ups.model using OID 1.3.6.1.2.1.33.1.1.2.0

Hi, I'm trying to get NUT running. I've installed it with pkg_add nut I can see my UPS as follows: # nut-scanner Cannot load SNMP library (libnetsnmp.so) : file not found. SNMP search disabled. Cannot load XML library (libneon.so) : file not found. XML search disabled. Cannot load AVAHI library (libavahi-client.so) : file not found. AVAHI search disabled. Scanning USB bus. No start

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

Hello, sorry and puzzled to hear about that. My guess would be permissions - while nut-scanner remains `root` (if started as one) and sees everything, drivers default to dropping privileges and may not see the devfs nodes (not sure OTOH which paths are involved on OpenBSD). One experimental workaround can be adding `user=root` to `ups.conf` entry for the device. But properly - tame whichever

Hi Jim, Thanks for your help. I'll respond in the same order as you did: 1. Unfortunately, I did "chown" stuff to these created users... Since the other three responses don't seem to be what you're looking for (but that's only my uninformed interpretation), I suppose the problem lies here? Is there a number of files/directories that I should

I'm trying to Compile/Package and then (on a different box) Config/Run 2.8.1. Both boxes are Raspberry Pi 4b on Bullseye with a generic USB UPS. -- I'm trying to get nut running on my Raspberry (bullseye/11). (I'd also love to share a working 2.8.1 for Raspberry with the world, but...) I compiled the latest code from git: version 2.8.1-774-g963abbd87 I compiled it on one system

Hello, I was thinking about what could be going wrong here, and a few ideas pop up: 1) If you installed NUT from packaging, there should have been no need to add OS groups/users manually. There is a valid use-case for running different daemons under different accounts, as long as they talk over network and access same files or UNIX sockets at best by sharing a group for that, but it does need

> 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, Yesterday, I bought a UPS for the first time in my life, and was eager to dive into NUT. But not all is working as expected... I saw a similar thread started on 18 October, but it didn't help me. (I also spent a handful of hours searching the web for solutions, and of course read the manual and FAQ - "queequeg".) I tried shutting my UPS (APC "Back-UPS BX750MI

Hello! I use online UPS MV-1000 LT http://www.230v.ru/catalogue/?id=production/ups-sm/master-vision for the power of my Linux server SLES 10 SP1. I downloaded, compiled and configured diver nut 2.4.1 from this link http://www.networkupstools.org/source/2.4/nut-2.4.1.tar.gz Here are my configuration files: --- srv:/usr/local/ups # cat etc/ups.conf [npower] driver = megatec port = /dev/ttyS0