search for: upsdrvctl

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@s...

Hi, I have problems starting NUT 2.6.5-7.fc18 in Fedora 18 (now running kernel 3.8.3-201.fc18.x86_64), some details here: http://forums.fedoraforum.org/showthread.php?t=289724 The problem is, nut-driver.service automatic startup in boot fails with this: Mar 17 11:48:19 mybox upsdrvctl[1054]: Fatal error: unusable configuration Mar 17 11:48:19 mybox upsdrvctl[1054]: Network UPS Tools - BCMXCP UPS driver 0.26 (2.6.5) Mar 17 11:48:19 mybox upsdrvctl[1054]: RS-232 communication subdriver 0.19 Mar 17 11:48:19 mybox upsdrvctl[1054]: Unable to open /dev/ttyS6: Device or resource busy M...

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 exectuable by anyone. Doe...

...tus nut-driver ? nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/usr/lib/systemd/system/nut-driver.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since vie 2016-06-03 12:10:05 ART; 7s ago Process: 7511 ExecStop=/usr/sbin/upsdrvctl stop (code=exited, status=0/SUCCESS) Process: 9246 ExecStart=/usr/sbin/upsdrvctl start (code=exited, status=1/FAILURE) Process: 9245 ExecStartPre=/usr/bin/systemd-tmpfiles --create /etc/tmpfiles.d/nut-run.conf (code=exited, status=1/FAILURE) jun 03 12:10:03 nut-vm.infoestructura.local upsdrvct...

...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 note: I use "upsdrvctl start/stop" to start and stop the driver. Thank you, David Zomaya Tripp Lite ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 12:55 PM To: David Zomaya Cc: nut-upsuser Subject: Re: [POSSIBLE FRAUD] Re: [Nut-upsuser] [EXTERNAL...

...ut-upsuser] [EXTERNAL] Re: Help with Tripp Lite Internet600U David, I appreciate the quick feedback! If I didn't fat finger any of the parameters you sent me, it's still not working. Here's the output from the attempt to start. (BTW - nothing appears in the daemon.log when I use the upsdrvctl command.) pi at elmer:/home/macbackup $ sudo vi /etc/nut/nut.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/ups.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/upsd.conf pi at elmer:/home/macbackup $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools -...

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 upsl@localhost is unavailable"). I wonder whether this communication error message may be related to the howto assuming that a user 'upsl' exists, while 'nut' only config...

Hi, I've found that upsdrvctl crashes when there is not ports= specified ups.conf #0 __strrchr_sse2 () at ../sysdeps/x86_64/strrchr.S:33 #1 xbasename (file=0x0) at common.c:266 #2 stop_driver (ups=0x1e163e0) at upsdrvctl.c:135 #3 send_all_drivers (command=0x4020f0 <stop_driver>) at upsdrvctl.c:446 #4 main (argc=1, a...

...d because the control process exited with error code. See "systemctl status nut-driver.service" and "journalctl -xe" for details. >From the log file: May 20 13:51:47 elmer systemd[1]: Starting Network UPS Tools - power device driver controller... May 20 13:51:47 elmer upsdrvctl[2658]: This TrippLite device (09ae:3024) is not (or perhaps not yet) supported May 20 13:51:47 elmer upsdrvctl[2658]: by usbhid-ups. Please make sure you have an up-to-date version of NUT. If May 20 13:51:47 elmer upsdrvctl[2658]: this does not fix the problem, try running the driver with the Ma...

...er] [EXTERNAL] Re: Help with Tripp Lite Internet600U   David, I appreciate the quick feedback! If I didn't fat finger any of the parameters you sent me, it's still not working. Here's the output from the attempt to start.  (BTW - nothing appears in the daemon.log when I use the upsdrvctl command.) pi at elmer:/home/macbackup $ sudo vi /etc/nut/nut.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/ups.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/upsd.conf pi at elmer:/home/macbackup $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS...

David, I appreciate the quick feedback! If I didn't fat finger any of the parameters you sent me, it's still not working. Here's the output from the attempt to start.  (BTW - nothing appears in the daemon.log when I use the upsdrvctl command.) pi at elmer:/home/macbackup $ sudo vi /etc/nut/nut.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/ups.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/upsd.conf pi at elmer:/home/macbackup $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS...

...ut-upsuser] [EXTERNAL] Re: Help with Tripp Lite Internet600U David, I appreciate the quick feedback! If I didn't fat finger any of the parameters you sent me, it's still not working. Here's the output from the attempt to start. (BTW - nothing appears in the daemon.log when I use the upsdrvctl command.) pi at elmer:/home/macbackup $ sudo vi /etc/nut/nut.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/ups.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/upsd.conf pi at elmer:/home/macbackup $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools -...

Is there any reason why we couldn't pass the -D flags (counted by nut_debug_level) from upsdrvctl to the individual drivers? It seems a little strange to suggest to users that they should start the drivers with upsdrvctl normally, but then start them by hand for debugging. (If we want to debug upsdrvctl itself, we could use another flag for that, instead of -D.) -- - Charles Lepple

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:

...Lepple <clepple at gmail.com>: > On Apr 8, 2015, at 2:04 PM, Eric Cobb <Eric_Cobb at tripplite.com> wrote: > > Charles and list, > > If I leave the driver alone it does not eventually start. It continues to > report that it is unable to connect. I have to perform a upsdrvctl stop ; > upsdrvctl start (I actually just perform a init stop and start so that upsd > and upsmon both restart) for the driver to actually connect to the ups. > > I have attached an strace of the upsdrvctl start command when it is ran at > boot time via the init script. I'll let...

...r] [EXTERNAL] Re: Help with Tripp Lite Internet600U   David, I appreciate the quick feedback! If I didn't fat finger any of the parameters you sent me, it's still not working. Here's the output from the attempt to start.  (BTW - nothing appears in the daemon.log when I use the upsdrvctl command.) pi at elmer:/home/macbackup $ sudo vi /etc/nut/nut.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/ups.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/upsd.conf pi at elmer:/home/macbackup $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS...

...s remote shutdown commands to a set of network >> connected devices also living on this UPS (but sadly not able to run >> NUT). As its final step, it issues a command to shut the host machine >> down. >> >> It seems from what you say above, I need to issue "/sbin/upsdrvctl >> shutdown" in there somewhere - obviously before I shut the host machine >> down. I will have to test this to see exactly what that command does. >> When run w/out arguments, the usage says shutdown shuts down UPS >> drivers. I am not clear if this means that the UPS...

...051D:0002 so i tried: /etc/ups/ups.conf: [myups] driver = "usbhid-ups" port = /dev/usb/hiddev0 vendorid = "051D" productid = "0002" (also tried to comment vendor+product+port and set port=auto same problem) /lib/systemd/system/nut-driver.service ... ExecStart=-/sbin/upsdrvctl start myups -h ... with no difference, problem remains, cp /usr/lib/udev/rules.d/62-nut-usbups.rules /etc/udev/rules.d/62-nut-usbups.rules cp /usr/lib/tmpfiles.d/nut-run.conf /etc/tmpfiles.d/nut-run.conf edit /etc/udev/rules.d/52-nut-usbups.rules # APC - usbhid-ups ATTR{idVendor}=="051d&quo...

...051D:0002 so i tried: /etc/ups/ups.conf: [myups] driver = "usbhid-ups" port = /dev/usb/hiddev0 vendorid = "051D" productid = "0002" (also tried to comment vendor+product+port and set port=auto same problem) /lib/systemd/system/nut-driver.service ... ExecStart=-/sbin/upsdrvctl start myups -h ... with no difference, problem remains, cp /usr/lib/udev/rules.d/62-nut-usbups.rules /etc/udev/rules.d/62-nut-usbups.rules cp /usr/lib/tmpfiles.d/nut-run.conf /etc/tmpfiles.d/nut-run.conf edit /etc/udev/rules.d/52-nut-usbups.rules # APC - usbhid-ups ATTR{idVendor}=="051d&quo...

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 > 2015-09-04T11:43:38.825970-04:00 linux-5048 upsdrvctl[1887]: Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) > 2015-09-04T11:43:38.826243-04:00 linux-5048 upsdrvctl[1887]: USB communication driver 0.32 > 2...