similar to: Very long delay for shutdown.restart on usbhid-ups powercom

Hello. Not listed as supported, so here is some info, [root at vhost ~]# /usr/sbin/usbhid-ups -DD -a powercom Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 0.000000 debug level is '2' 0.001318 upsdrv_initups... 0.074753 Checking device (0529/0001) (003/002) 0.074835 Failed to open device, skipping. (Permission denied)

On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru> wrote: > However I was unable to shutdown.return it. Maybe protocol is not fully > compatible? > > 0.145757 Initiating UPS shutdown > 0.145760 upsdrv_shutdown... > 0.145763 instcmd(shutdown.return, [NULL]) > 0.145767 powercom_shutdown_nuf: value = (null), command = 5400 > 0.145770

My UPS is connected to a Raspberry Pi by USB. After a few hours of working, the service fails. Looking at kernel messages I noticed that the device is repeatedly disconnecting and reconnecting. I have tried using a different USB port and using a brand new USB cable. I have not had success by changing config parameters like pollfreq/pollinterval/etc. What is causing the UPS to keep disconnecting?

Thanks again for your patience. I'm still learning how to deal with systemctl myself (and starting from, I'm sure, a much lower level of understanding), so if I've neglected to restart or start something, please let me know. I made the change to /etc/nut/upsd.conf. I restarted upsdrvctl, which reported back: Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic

Charles, It starts out good, then goes into a Connection timed out loop. If I can provide any information to fix a driver I'll do my best. Here's the output: # /usr/local/ups/bin/usbhid-ups -DD -a eaton Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 0.000000 debug level is '2' 0.002550 upsdrv_initups... 0.288229 Checking device

On 10/01/2015 00:45, Charles Lepple wrote: > On Jan 8, 2015, at 11:43 PM, Graham Menhennitt > <graham at menhennitt.com.au <mailto:graham at menhennitt.com.au>> wrote: > >> Hello Nutters, >> >> I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) >> with an APC Back-UPS CS 350 connected via USB. I get persistent >> (every few

Hi - I just installed NUT from source, using the usbhid-ups driver for a tripplite UPS (i compiled with the appropriate flag for the USB device). NUT version is 2.7.3. I UPS is AVR900U System is archlinux - fully up to date, running on an ARM device. Linux <Systemnameomitted > 3.1.10-35-ARCH #1 PREEMPT Fri Jan 23 19:14:18 MST 2015 armv5tel GNU/Linux I can communicate with my UPS - no

This is new install on Ubuntu 16.04, using packages from Synaptic, *Network UPS Tools upsd 2.7.2 I am getting these messages in the terminal: Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): UPS CyberUPS1 at localhost is unavailable I am still unclear on where to set when nut shutdowns system. I see nut-client and nut server are automatically starting from SystemD.

Hi, This might be a simple thing to fix, but I can?t figure it out. We replaced the battery for the first time in our Eaton 5PX a couple of weeks ago, but we haven?t been able to clear the ?ups.alarm: replace battery!? status. Details of our installation are: OS: Debian 6 NUT version: 2.7.4 Installation method: from source tarball UPS device: Eaton 5PX2000IRT, 240V, 1800W, 2000VA, bought in

On Mon, Jun 8, 2015 at 11:20 PM, Charles Lepple <clepple at gmail.com> wrote: > On Jun 8, 2015, at 8:23 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > >> Hi Charles. I patched, reconfigured, remake'd, remake install'd - but >> no change. however, some more likely helpful information below for >> you. Thank you > > Odd. Are you sure that the

I recently purchased a CyberPower CP1500PFCLCD UPS as a replacement UPS for a headless server running Slackware 14.1 with the 3.10.7 kernel. I then downloaded the NUT 2.7.1 tarball on the server and following the directions installed the software. The installation went well and the UPS will shutdown the server using the forced down test and then it powers back up as it should. The

I've searched the listserv archive, to no avail, so I hope I'm not duplicating a previous problem. I am anxious to get this working, so I'm open to uninstalling what I have and starting over. One note which may not be meaningful is that this UPS pre-dates the Raspberry Pi I've got connected to it, and I used to use it with the CyberPower software, which requires logging in with a

Hello, I am hoping someone can point me in the right direction. I am setting up a new UPS, most things seem to be working except the UPS turns off immediately during a test shutdown using///"//upsmon -c fsd".//No delay before the UPS turns itself off leaving no time for the server to shutdown properly. I have attempted to set the delay higher using "upsrw -s

Hi there, OS: (L)ubuntu 12.04 precise LTS Nut: 2.6.3-1ubuntu1.1 Installation Method: Package (apt-get install nut) Hardware: HP R1500 G3 INT Hardware-Specs: http://h18004.www1.hp.com/products/quickspecs/14059_div/14059_div.pdf Problem: I tried to set up nut with our new arrived HP R1500 G3 UPS but there is a failure with the usb connection. After trying "/lib/nut/usbhid-ups -DD -a

Hello, I have been using NUT for a short period of time and have some questions regarding the UPS reboot signal that I can't figure out. Have tried some googling and reading the DOCs but I am struggling to understand how some variables / things are supposed to work, so would appreciate any help with any of the following questions. I am running NUT on standalone mode on a linux machine

Hi! Info OS: TinyCore Linux 4.5.6 NUT version: 2.6.4 NUT innstallation method: source tarball Device name: Eaton Ellipse ups eco 1600 usb din (EL1600USBDIN) /usr/local/ups/etc/ups.conf file: [eaton] driver = usbhid-ups port = auto When I run: root at Dalen:/usr/local/ups/bin/upsdrvctl start eaton I get this error message: Network UPS Tools - UPS driver controller 2.6.4

I have a Tripp-Lite BCPERS450, connected to a system running Ubuntu 16.04.3 LTS and NUT 2.7.2-4ubuntu1.2. I had to make my own /lib/systemd/system-shutdown/nutshutdown, but now everything is working except for powering on and off the UPS. Regardless of the settings of offdelay and ondelay in upsconf, and regardless of whether the AC power is on, when I say "upsdrvctl shutdown" the UPS

Thanks for the reply. However these two FAQ are unfortunately not describing the situation. - The first issue is that NUT switches off the UPS upon reboot on low battery (not that it dies because of low battery) - The second issue is that the UPS does not recognise being online again (not that the PC does not restart) Sent from my iPhone > On 11 Jun 2019, at 02:03, Charles Lepple <clepple

On Nov 12, 2014, at 3:53 AM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > Hi Charles, > >> Sigh, I wish the vendors wouldn't change operation without changing identifiers. >> >> Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? > > No-no, there is no an old 0x0004 or new 0x0004

Thanks for your help. From: Charles Lepple <clepple at gmail.com> Date: Mon, 18 Dec 2017 19:26:56 -0500 This may sound like an apples-to-oranges comparison, but we did uncover an issue with CyberPower UPSes where the delay values needed to be greater than or equal to 60 (seconds), since they were being rounded down to integer numbers of minutes internally: What was the largest