similar to: New UPS Support: Eaton 5S 1000

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.

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

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

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

Oops... changing that to --with-user=nut solved one problem. I have the driver, upsd and upsmon running now. Thank you! Now I'm back to another issue, every 2 seconds I get in the logs: May 3 13:45:23 myhost upsd[2587]: Connected to UPS [eaton]: usbhid-ups-eaton It seems happy to do this forever. On Tue, May 3, 2016 at 8:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On

In /var/log/syslog Dec 23 13:04:50 ************** upsmon[2010]: Poll UPS [rack1ups at localhost] failed - Write error: Broken pipe After this, there is no longer a upsd daemon running. Error messages follow: Dec 23 13:04:50 ************** upsmon[2010]: Communications with UPS rack1ups at localhost lost ... Dec 23 13:04:55 ************** upsmon[2010]: UPS [rack1ups at localhost]: connect

Good evening, I tried getting this to work a couple years back but didn't have enough time to do all the debugging that was needed (apologies to the devs who tried to help at that time). It's working much better now, but I'm still not able to get an answer from upsc. Can anyone help me work out why I'm getting the error when querying with upsc: Error: Data stale My

Good evening, I tried getting this to work a couple years back but didn't have enough time to do all the debugging that was needed (apologies to the devs who tried to help at that time). It's working much better now, but I'm still not able to get an answer from upsc. Can anyone help me work out why I'm getting the error when querying with upsc: Error: Data stale My

Hello, I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. The attached UPS is an APC xs1500 (model bx1500g). The connection is an RJ45 to USB cable. Here is my ups.conf: [xs1500] driver = usbhid-ups port = auto desc = "APC Back-UPS xs1500" The problem I am encountering is upsd crashing with an 'Out of memory' error. I can

On Jan 24, 2015, at 12:45 AM, Ryan Sizemore <ryan.sizemore at gmail.com> wrote: > Hello, > > I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. I am not sure why they are not listed on the main download page, but there are actually three Windows MSI releases after that: http://www.networkupstools.org/package/windows/ I

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

Hi, I've had NUT 2.6.1 on OpenIndiana working with a Tripp-Lite ECO550. I've been playing around with the config files a little bit, and I must have done something that messed up the demon. I now get wiley$ pfexec /opt/nut/sbin/upsd -DD Network UPS Tools upsd 2.6.1 0.000000 listening on 127.0.0.1 port 3493 0.000486 listening on ::1 port 3493 0.001279 Can't connect to

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

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

An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20090120/ffb91e55/attachment.htm

Jan 19 05:50:13 mars nut-monitor[849]: Signal 15: exiting Jan 19 05:50:13 mars nut-monitor[849]: Network UPS Tools upsmon 2.8.0 Jan 19 05:50:13 mars systemd[1]: Stopping nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller... Jan 19 05:50:13 mars systemd[1]: nut-monitor.service: Deactivated successfully. Jan 19 05:50:13 mars systemd[1]: Stopped nut-monitor.service

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

With recent NUT releases, driver disconnections should be contained in its own `nut-driver at eaton` instance (the `@upsname` part is derived from the `ups.conf` section name). One of the drivers failing and restarting is not a proper cause for the data server to recycle. Also, nowadays some (maybe not all) USB-capable drivers should try to reconnect without restarting. Note however, that in some

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