similar to: MGE EllipseMAX 1500 shuts down after a few hours

> If there is no message to NUT, I would consider opening a trouble > ticket with Eaton. It is possible that there is a known issue and/or > a firmware upgrade. What kind of message to NUT? In the log (syslog) there is no other message registered. In nut.log only this appears: > Dec 1 08:10:54 openmediavault upsd[5284]: Data for UPS [ellipsemax] > is stale - check driver >

I have restored original configuration and enabled the ignorelb flag. I didn't point out in the original e-mail that after every poweroff the battery percentage is reported at 40% instead of 100% and charges slowly again to 100%. Maybe the UPS sends a LB event and shuts down immediatly as suggested in the manual. But the UPS powered off again. The variables reported by upsc can be found

On Dec 1, 2018, at 3:45 PM, raul <raulvior.bcn at gmail.com> wrote: > > The UPS is connected to the following environment: > OS: Debian GNU/Linux 9.6 (stretch) > NUT version: 2.7.4-5 > Device output from lsusb: 0463:ffff MGE UPS Systems UPS > Model name: MGE EllipseMAX 1500 > URLs: >

On December 2, 2018 7:29:38 PM GMT+02:00, raul <raulvior.bcn at gmail.com> wrote: >I have restored original configuration and enabled the ignorelb flag. I > >didn't point out in the original e-mail that after every poweroff the >battery percentage is reported at 40% instead of 100% and charges >slowly again to 100%. Maybe the UPS sends a LB event and shuts down

I have a ups that doesn't always (sometimes it does) load NUT right. I use Gentoo: * sys-power/nut Latest version available: 2.6.0-r1 Latest version installed: 2.6.0-r1 Size of files: 1,663 kB Homepage: http://www.networkupstools.org/ Description: Network-UPS Tools License: GPL-2 The kernel is 3.0.4. Here is the dmesg output:

Hi, I keep getting the following messages (or similar) in my syslog: Nov 23 11:38:08 io kernel: [763936.921566] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -110 Nov 23 11:38:08 io kernel: [763936.972569] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -75 Nov 23 11:38:08 io kernel: [763936.976568] usb 3-2: usbfs: USBDEVFS_CONTROL

Hello, I have a Salicru UPS in a Debian Wheezy connected with a USB HUB: # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ... Bus 001 Device 003: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial The problem is that I have some failed messages: # dmesg ... [90941.136274] usb 1-3.7: usbfs:

On Mar 7, 2014, at 4:12 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote: > Are the messages a problem? Or could I ignore? Since they aren't happening on each poll interval, they are not a big problem. The driver should recognize -110 as a timeout, and retry the query.

I have nut 2.6.4-2.3+deb7u1 on debian 7 32bit, with UPS Eaton Nova AVR 1250 connected via USB. It happens several times a day that I get a message about Apr 3 16:41:49 kernel: [422581.049671] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 Apr 3 16:41:54 kernel: [422586.041057] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 3 ret

I have taken out the batteries and measured them with a multimeter. They put out 13V (they are rated 12V 9Ah). Putting them back again and disconnecting the UPS from the mains it is kept on, powering all the connected devices. The shutdowns only occur when the UPS is being monitored. Are you sure it's a battery problem? Do UPS perform further tests when they are being polled for data?

On Apr 3, 2014, at 3:40 PM, Adam Pribyl wrote: > I have nut 2.6.4-2.3+deb7u1 on debian 7 32bit, with UPS Eaton Nova AVR 1250 connected via USB. Which kernel version? > It happens several times a day that I get a message about > > Apr 3 16:41:49 kernel: [422581.049671] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 > Apr 3 16:41:54 kernel:

Hello, I encounter a problem using the UPS MGE Evolution 850 VA USB with Debian Etch and the nut package available for this version. I got this error: ==syslog== Can't connect to UPS [MGE850VA] (usbhid-ups-auto): No such file or directory upsd[2767]: Startup successful upsmon[2769]: Startup successful upsd[2767]: Connection from 127.0.0.1 upsd[2767]: Client MGE at 127.0.0.1 logged

I recently purchased a CyberPower CP1200AVR UPS and am trying to get NUT 2.0.3 or NUT 2.1.0 to work with the newhidups driver, but am having little success. Before I purchased I did some googling and saw people talking about problems so I'm guessing it may not be supported yet? I did find some posts about people getting it to (sort of) work with some hacks, but couldn't tell if they

Folks, I have been working on a problem with the usbhid-ups driver and the MGE / Eaton Ellipse series UPS. There seems to be light at the end of the tunnel. For whatever reason, these devices seem to trigger error 'EPIPE' randomly. So far, the response to this of the usbhid-ups (and previously, newhidups) driver is to reconnect. Most of the time this will succeed on the first

Hello, I'm using NUT to manage a MGE Ellipse ASR UPS, with the newhidups driver. It works fine, except that after a few hours, I get a few errors from the kernel and the driver dies. Here's the output from the syslog: Apr 26 02:00:41 ezquiel kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Apr 26 02:00:43 ezquiel last message repeated 2 times

Hi all, after a change of UPS (to Atlantis Host Power 851) I began to use the new driver blazer_usb and compared to old one (blazer used with serial connection) I noted more CPU use and errors in dmesg: [...] [256712.584370] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [256789.640795] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8

Dear List, I thought it might be useful if I wrote up my notes on getting an MGE UPS to work with NUT and openSUSE. The MGE UPS (an Ellipse 1500 USB) will work well with NUT and openSUSE 10.2, but not "out-of-the-box": there are some things you need to do: Intro. MGE have built rpms of NUT which greatly simplify installation. Merci MGE. I used the rpm's for nut-2.0.5 and the

Well, also below in dmesg: [ 190.249219] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 26.11.2014, 03:05, "Victor Porton" <porton at narod.ru>: > A fragment of dmesg output (here idVendor=0665, idProduct=5161 is the UPS; the webcam is idVendor=17a1, idProduct=0128): > > [ ???1.317085] usb 4-1: new high-speed USB device number 2

Hi, There is many (20 per day on average) messages like: kernel: usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -110 usbhid-ups[6768]: HIDGetDataValue: Connection timed out What can be done do correct that problem? best regards, Franck my configuration: debian etch nut 2.2.1 (recompiled source from testing to use latest version before posting here) updated

I am seeing some problems when using the Powerware 5115 UPS when connected to the Patsburg USB controller and would like to know if anyone has a solution. The symptom is that PING messages sent to the bcmxcp_usb driver take as long as 25 seconds to complete. The configuration is a Romley patform (a.k.a., Sandy Bridge + Patsburg) running Debian 6 with 2.6.39 kernel with NUT 2.6.4 in which the