similar to: Restarting service issues

On Jun 3, 2016, at 11:13 AM, Sergio Belkin <sebelk at gmail.com> wrote: > > jun 03 12:10:05 nut-vm.infoestructura.local upsdrvctl[9246]: No supported device detected > jun 03 12:10:05 nut-vm.infoestructura.local upsdrvctl[9246]: Network UPS Tools - Generic SNMP UPS driver 0.72 (2.7.2) > jun 03 12:10:05 nut-vm.infoestructura.local systemd[1]: nut-driver.service: control process

New NUT install dealing with three APC Smart-UPS 5000s, two of which have AP9617 and the third has a AP9619 card. The SNMPv3 configurations on all three are exactly the same. This is confirmed by snmpget calls that work just fine: snmpget -Cf -v3 -u [...] -l authPriv -A '[...]' -X '[...]' -a MD5 -x DES [upsname] .1.3.6.1.4.1.318.1.1.1.1.1.1.0 snmp-ups can query all three

Hi all - I'm new to both UPS setup and SNMP on linux - so I'd appreciate any help I can get....I'm stuck! I'm running fedora core 5, and have installed net-snmp and nut. I'm trying to get my network connected UPS to this linux machine. My /etc/ups/ups.conf looks like this: [upsnetwork] driver = snmp-ups port = 172.31.254.7 community = public desc="Network

Hi, one user found problem with restarting nut. upsdrvctl does not wait for drivers being really terminated. In init scripts we have following: killproc upsmon killproc upsd upsdrvctl stop and then upsdrvctl start upsd upsmon problem is upsdrvctl stop only sends terminating signals but does not wait for driver termination. This makes driver fail to start sometimes when old driver is still

hello.. is it possible to shut down APC Smart UPS with SNMP protocol? I got a message that is not possible with current driver... *monk:/etc/nut# upsdrvctl shutdown rm700 Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools - Multi-MIBS SNMP UPS driver 0.421 (2.2.2) Warning: This is an experimental driver. Some features may not function correctly. Detected Smart-UPS 700 RM on host

On 4/28/20 1:58 PM, David Zomaya wrote: > snmpwalk -l authpriv -v 3 -u user -a MD5 -x DES -A authpassphrase -X > privpassphrase Evidently, even with argument identifiers order matters. That worked just fine and dandy. Now I guess I need to play with the order of the nut-scanner arguments to see if I get a similar result. thanks, nomad

Hi, In Red Hat /etc/init.d/halt script, it expects upsdrvctl to be in /sbin rather than /bin which sounds normal considering the power of that command. If I move this file to sbin, this is what I get when invoking it: [root@serveur1.sassine.eu nut-2.0.5]# mv /bin/upsdrvctl /sbin/ [root@serveur1.sassine.eu nut-2.0.5]# which upsdrvctl /sbin/upsdrvctl [root@serveur1.sassine.eu nut-2.0.5]#

Hi, I've installed the debian package of these ups tools and everything looks good. debian:/var/log# upsdrvctl -h Network UPS Tools - UPS driver controller 2.0.1 (Though I'll have to wait for a quieter time to pull the plug and test it.) debian:/var/log# ls -l `which upsdrvctl` -rwxr-xr-x 1 root root 18232 Sep 22 2005 /sbin/upsdrvctl I notice that upsdrvctl is

Tested a Ubuntu 18.04 LTS virtual machine with NUT 2.7.4 and a 3024 protocol Tripp Lite UPS (mine is a INTERNET550U, but same protocol) :/etc/nut$ lsusb | grep Tripp Bus 002 Device 004: ID 09ae:3024 Tripp Lite I it got generally working (outputting reasonable responses to upsc, although there are some issues with variables like frequency) by adding productid=3024 to my ups.conf. Like this:

"Can't claim USB device [09ae:3024]: could not detach kernel driver from interface 0: Operation not permitted" Is probably an issue with NUT grabbing the UPS... can you disconnect and reconnect the USB cable and try again? If that fails, maybe a udev rule will help. Thank you, David Zomaya Tripp Lite <http://www.tripplite.com/> ________________________________ From:

My thoughts for a test: * Just have MODE=standalone in nut.conf * Put [tripplite] driver = usbhid-ups port = auto productid=3024 desc = "Tripp Lite Internet600U" In ups.conf * Put LISTEN 127.0.0.1 3493 LISTEN ::1 3493 [tripplite] driver = usbhid-ups port = auto in upsd.conf That may be suboptimal but will probably work for a test. Side

Wow - you're doing all the work for me! Thanks for the rule set.  I can't easily reboot that box just now, so I'm working on reloading the rules. When I try  udevadm control --reload-rules && udevadm trigger May 20 15:19:01 elmer systemd-udevd[3413]: Process '/sbin/crda' failed with exit code 234. May 20 15:19:01 elmer systemd-udevd[3413]: Using default

That worked out just fine. What I am currently running into are conditions where I am getting the following error that I figured I would share. Error: libusb_get_interrupt() returned 0 instead of 8 while sending 3a 4d b2 0d 00 00 00 00 '.M......' Conditions: upsdrvctl start via Init Script at Boottime. If I run the init script after boot, I do not receive this error. Eric Cobb ekcobb

Borrowing from our friends at Ask Ubuntu ( https://askubuntu.com/a/276637 ) there is. I've modified it for use with a Tripp Lite UPS and 3024 protocol below. Try disconnect/reconnect after and see what happens. :/etc/nut$ cat /etc/udev/rules.d/90-nut-ups.rules # /etc/udev/rules.d/90-nut-ups.rules ACTION=="add", \ SUBSYSTEM=="usb", \ ATTR{idVendor}=="09ae",

On 1/1/20 9:56 PM, David White wrote: > > > On 1/1/2020 11:49 AM, David White wrote: >> >> Hi Roger and, as always, thanks! >> >> I really do not want to wait very long before shutting down things on >> this UPS. What I think I am doing (or at least trying to do) is to >> execute a script on the host machine when the UPS is detected by NUT to >>

Hello Bob, > I had preferred the shutdown script method because it was a little more > straight-forward, and possibly more portable. This guide is meant to > help people get the UPS up and running, whatever their Linux distro. I > don't know how common the systemd implementation is across various Linux > distros. You will need to support Linux systems with and without

Using the HOWTO in http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ I installed nut on an Ubuntu Edgy LAMP Server with an Eaton Powerware 5110 attached to it via usb. But nut fails to start properly (see the error message "Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon" below). It then complains about communication with the UPS being lost ("UPS

On Fri, 4 Sep 2015, Rob Groner wrote: > Well, I tried the same script method with openSUSE 13.2, and it still did not execute. > > So I tried the system method, and it worked 1 time out of 3 attempts. I captured the last failure: > 2015-09-04T11:43:38.825317-04:00 linux-5048 upsdrvctl[1887]: Can't claim USB device [2a37:5110]: No such file or directory >

Glad to hear it's working, thanks Tom. Network UPS Tools team: is fixing this as simple as me telling you what new UPS protocols are HID-PDC compliant? Thank you, David Zomaya Tripp Lite<http://www.tripplite.com/> ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 2:42 PM To: David Zomaya Cc: nut-upsuser Subject: Re:

Hi Charles, thank you for your answer. This was indeed the core of the problem. I have amended the configuration files. It means now the communication works as required. Alas I now have another problem. Just for the record here is the configuration after the changes. The configuration is as follows. #nut.conf MODE=standalone #ups.conf [eaton] driver = usbhid-ups port = auto