similar to: [Eaton 5S 1500] overvoltage shut down?

>> 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

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

Hi, 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 disconnect, device number 103 Mar 10 19:50:33 spike kernel: usb 4-5: new low-speed USB device number 104 using ohci-pci Mar 10 19:50:34 spike kernel: usb 4-5: New USB device found,

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

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 .

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

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

On Apr 26, 2016, at 11:56 AM, Ken Marsh <ken.marsh at sparkpost.com> wrote: > > > I've used NUT successfully for monitoring many different brands of UPS, but this one has me stumped. It has the same manufacturer ID and Product ID as older supported MGE-type Eaton UPS's, but has trouble talking. I tried Ubuntu's repo NUT Which release of Ubuntu, and which version of

On May 3, 2016, at 1:46 PM, Ken Marsh <ken.marsh at sparkpost.com> wrote: > > Oops... changing that to --with-user=nut solved one problem. I have the driver, upsd and upsmon running now. Thank you! Glad that worked - I was still hung up on the strange error message. > Now I'm back to another issue, every 2 seconds I get in the logs: > > May 3 13:45:23 myhost

On May 2, 2016, at 10:40 AM, Ken Marsh <ken.marsh at sparkpost.com> wrote: > > I just did strace. EINPROGRESS seems to be part of some socket connect code either doing with ldap or DNS. I have no idea why it is doing this as the upsmon process user "nut" is local, nsswitch.conf has files before ldap, and the UPS is on USB and in standalone mode. Maybe just boilerplate

> On May 4, 2016, at 9:00 AM, Ken Marsh <ken.marsh at sparkpost.com> wrote: > > 24.578753 upsdrv_updateinfo... > 24.831627 libusb_get_interrupt: Connection timed out > 24.831647 Got 0 HID objects... > 24.831661 Quick update... > 24.881602 Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 32, Value: 0 > 24.931613

On May 5, 2016, at 9:25 AM, Ken Marsh <ken.marsh at sparkpost.com> wrote: > > Well, whaddya know, when run with -DDDDD it works! upsc consistently returns data. Maybe it's a timing thing, or a select affected by I/O or something tricky like that. Nonetheless, I ran it, hit upsc eaton multiple times, collected the output and attached it. If this doesn't give you what you need,

On May 4, 2016, at 10:01 AM, Ken Marsh <ken.marsh at sparkpost.com> wrote: > > Is this actually functional? Usually I don't consider NUT operational until upsc works (among other things). You're right, the "ups.status: WAIT" isn't fully functional. I am surprised, though, since the usual problem area is driver-to-hardware rather than upsd-to-driver. From the

Hi, Thank you for taking a look at this. This is 13.10. I realize Saucy is no longer supported. This system is slated for replacement, but in the meantime I'm responsible for it. The repo version of nut was 2.6.4-2.3ubuntu2. Installing it was useful as it gave me the nut user and group. The compiled version errors out whether or not the repo version is installed. I just did strace.

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

Dear all, first post here and wanted to start by thanking everybody who made this possible. I've been reading the docs and setting up NUT from packages on ubuntu xenial. I have nut[-client,-server] installed, version 2.7.2-4ubuntu1. My UPS is an Eaton 5S 1500, which I picked from the list of supported devices. I've got it working and I can correctly query/monitor the UPS via USB etc.

Hi Charles, Thank you for sticking with me through this! Well, whaddya know, when run with -DDDDD it works! upsc consistently returns data. Maybe it's a timing thing, or a select affected by I/O or something tricky like that. Nonetheless, I ran it, hit upsc eaton multiple times, collected the output and attached it. If this doesn't give you what you need, I can retry with fewer/more

I've used NUT successfully for monitoring many different brands of UPS, but this one has me stumped. It has the same manufacturer ID and Product ID as older supported MGE-type Eaton UPS's, but has trouble talking. I tried Ubuntu's repo NUT, and it logs a Connecting to UPS message every few seconds forever, but never really succeeds (or says it fails). Different failure mode after

Hello. I have this UPS: Krauler UP-D1200VA Megatec USB protocol Vendor ID: 0x0001, Device ID: 0x0000 #KRAULER UP-D1200VA VER6.00 #220.0 004 23.50 50.0 Currently I have nut 2.2.0 installed from sources. Installation was successful except that I had to change a string in 52-nut-usbups.rules from: SUBSYSTEM!="usb_device", GOTO="nut-usbups_rules_end" to: