similar to: Eaton 1500 USB constant disconnections

Arno, thanks for taking the time to write back and no worries about lag, we're all busy and I'm grateful there is a community to interact with to begin with. You're right - the problem went away once I actually configured nut. I guess I was too "cautious" and when I saw the errors I thought something was wrong with the usb connection and didn't try to get nut going

2017-03-11 4:55 GMT+01:00 Spike <spike at drba.org>: > Hi, > Hi Spike, sorry for the lag in answering, I was collecting the needed information. I have a eaton 1500 that connects to an Ubuntu Xenial box via USB. The UPS > works, however exactly *ever 5 minutes* it disconnects and reconnects and I > see this in syslog: > > Mar 10 19:50:32 spike kernel: usb 4-5: USB

>> last night we had what looked like a power spike and 3 machines plugged >> into 2 Eaton UPS went down instantly. I heard the click the UPS makes when >> it shuts the load on the ports and then shuts itself down (ie same thing if >> I simulate with upsmon -fsd). The machines instantly came back, there was no >> actual downtime, and the machine next to them which is

Dear all, maybe not strictly a NUT question but I can't imagine a better place to ask, hope that's ok. last night we had what looked like a power spike and 3 machines plugged into 2 Eaton UPS went down instantly. I heard the click the UPS makes when it shuts the load on the ports and then shuts itself down (ie same thing if I simulate with upsmon -fsd). The machines instantly came back,

Hi, I've been setting up a few Eatons 1500 USB in master/slave mode and run into what I'm thinking is a hostname resolution problem. Basically, to avoid hardcoding ips, I'd love to be able to add a LISTEN on the lan's ip which has hostname, let's say, server1.local . If I set up upsd.conf such as LISTEN server1.local 3493 what I end up with is upsd listening on 127.0.0.1 .

My UPS is a Eaton Ellipse 1000S (But its identified as MGE Ellipse 0463:ffff). I have been using the usb interface with the usbhid-ups driver, but I found that sometimes (too much times) the driver doesn't respond and NUT doesn't receive changes nor notifications from the UPS. The kernel lose the connections with USB device, in the kernel logs appears: Dec 30 11:24:12 rei kernel:

Sorry, I'll gzip/attach next time. I tried pollonly and made sure no processes were hanging out. While everything comes up and seems to run happy, I still get log messages every couple of seconds, and "upsc eaton" gives me one of two messages: Error: Driver not connected ups.status: WAIT Is this actually functional? Usually I don't consider NUT operational until upsc works

Maybe a kernel USB issue, but people on this list may have encountered this issue. I am testing a new UPS (EATON 5E 1500iUSB) and am having a problem with the USB connection failing. My old UPS (EATON Ellipse MAX 1500) works just fine with the latest f30. Both devices identify as ID 0463:ffff MGE UPS Systems UPS To narrow the focus I booted recent live CDs on a PC that has no other USB devices

2017-03-29 12:32 GMT+02:00 Arnaud Quette <arnaud.quette at gmail.com>: > > > 2017-03-29 5:49 GMT+02:00 Spike <spike at drba.org>: > (...) > >> Is this really the desired behavior? I can certainly work with it, but it >> seems it'd be nice if it could work with dns resolution (at least client >> side, the LISTEN statement I guess it's ok), but

A final note: http://lists.alioth.debian.org/pipermail/nut-upsuser/2014-April/008977.html That message talks about the Eaton Nova AVR which on the Eaton 5E product page it says the 5E replaces the Nova. Do they perhaps share hardware/firmware? Thanks, Leith Bade leith at leithalweapon.geek.nz On 10 August 2014 10:16, Charles Lepple <clepple at gmail.com> wrote: > On Jul 26, 2014, at

and I should have probably mentioned... right after the event I unplugged the UPS's main and it went on battery, showing it had 11 mins worth of power left which is exactly what I'd expect on that load with full batteries. So the UPS "works" as expected, but then unplugging the cable would test a power dip, not a power spike, which si what I believe happened. thanks again, Spike

Hello Charles, I've attached a dump below. There were no long entries on any of the hosts, neither the one running standalone, nor the master/slave combo, which is not too surprising, it was really fast: I saw the light flickering in the room, almost like flash, and all those 3 systems went down. I first heard the "click" of the ports being disabled, heard the systems shut down, and

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

On Aug 7, 2014, at 7:57 AM, Leith Bade <leith at leithalweapon.geek.nz> wrote: > I have tried to plug it into every USB port (including the USB 3.0 > ones) and I still get these errors. I discovered that power cycling > the UPS will fix it for a while, and also unplugging and replugging > the USB cable will also fix it sometimes. Error -32 is EPIPE, which means that the PC

On 10 August 2014 09:05, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 7:57 AM, Leith Bade <leith at leithalweapon.geek.nz> wrote: > > Error -32 is EPIPE, which means that the PC didn't see a reply from the device during the descriptor read. I don't know that we have ever successfully run one of these issues to ground. > Considering Eaton do

Hi, I recently purchased a new Easton 5E UPS. I plugged the USB cable into my computer so I could use the NUT UPS tools. However every so often NUT fails to connect to the device after a boot. Looking at dmesg I see errors like this: [ 3.277075] usb 1-9: new low-speed USB device number 6 using xhci_hcd [ 3.302091] usb 1-9: device descriptor read/8, error -32 [ 3.430241] usb 1-9: device

Hello, Just baught this ups to replace an Ellipse. I've had a look at the nut hardware compatibility list, it's fully compatible and uses the same driver as ellipse (usbhid-ups) Here is the error I get when I "/usr/bin/upsdrvctl start" : Network UPS Tools - UPS driver controller 2.6.5-Unversioned directory Network UPS Tools - Generic HID driver 0.37 (2.6.5-Unversioned

Hello and thanks for all the replies. This morning at 9:50 the server stopped working unexpectedly - I was still sleeping until 10:00, so no user intervention took place. Jan 19 05:50:17 mars nut-server[1303]: mainloop: Interrupted system call Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting Jan 19 05:50:17 mars nut-server[1303]: Network UPS Tools upsd 2.8.0 Jan 19 05:50:17 mars

On 19.01.24 16:20, Stefan Schumacher via Nut-upsuser wrote: >This morning at 9:50 the server stopped working unexpectedly - I was >still sleeping until 10:00, so no user intervention took place. > >Jan 19 05:50:17 mars nut-server[1303]: mainloop: Interrupted system call >Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting >Jan 19 05:50:17 mars nut-server[1303]: Network UPS