similar to: [RFC] PowerChain: add device.parent to NUT variable names

Hi, this is the 2nd part of the PowerChain RFC. 2011/6/13 Arnaud Quette <aquette.dev at gmail.com> > As already presented, the links below will describe in details the > PowerChain notion: > > https://wiki.ubuntu.com/ServerOneiricInfraPower > https://wiki.ubuntu.com/ServerOneiricInfraPower#PowerChain%20design >

Hey, I'm scheduling a 2.6.2 release for max. September 15. The content will be lighter than first expected with 2.8.0 (see below). This includes the current trunk plus: - merge the nut-scanner branch, - some snmp-ups improvements (sysOID matching for init stage) and some more MIBs, - a first complete version of the nut-ipmipsu driver, - the new jNut Java binding, - preliminary support of

Fellows, I've been caught by real life, and didn't find time to share / discuss this with you. I've been attending UDS Oneiric, from May 9 to 13 in Budapest, and had a chance to present and complete some ideas around NUT: https://wiki.ubuntu.com/ServerOneiricInfraPower The end target is to have NUT ready to address infrastructures, both static like data-centers and flexible like

Dear NUT developers and contributors, time has come to shed more light on 2.8.0 roadmap! Ubuntu Developer Summit attendance has helped to clarify things. several of 2.8.0 tasks are detailed here: https://wiki.ubuntu.com/ServerOneiricInfraPower I'm conscious that our development infrastructure (Alioth) is not that suitable to track roadmaps, "Agile" specs and developments, as we do

Hi, I've got a question about managing two UPSes under NUT. I have two similar model APC usb-connected UPSes to work with, but don't know how to manage them simultaneously from under Windows. Long story short, my ups.conf looks like this: --- ups.conf --- [ups1] driver= usbhid-ups port= auto serial=AS1054340323 [ups2] driver= usbhid-ups port= auto serial=AS1026662626 ---

I have three APC SmartUPS 5000s. Two of them are AP9617 and one is AP9619. I have a RS-232 connections from my monitor host to all three. All three report status and give information. One of the two AP9617 - ups3-1 - does not shut down when FSD is sent. It did when I first set this system up a year or two ago but it's stopped doing so since then. Resetting the management interface does not

Hi, I didn't found an answer for my question in NUT documentation/FAQ or this mailing list archive so I?m posting it here. I want to start a timer only if both of my UPSes remain on battery. Not just one, both. My UPSes are: - ups1@host-a - ups2@host-b Is it possible to use something like this in upssched.conf? AT ONBATT ups1.* && ups2.* START-TIMER onbattwarn 180 Thanks,

Hi Charles, Running upsdrvctl -D start on the host with all three configured to SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all three but importantly they all start up and keep running. I'm starting to suspect the startup is taking so long that systemd is timing out and killing it. time -p reports real time of 133.27. I'm not a fan of systemd but

Hi All, I have an mge pulsar esv 14+ rackmount UPS connected via straight through serial cable to a USB to serial adaptor (My motherboard does not have a native RS232 port). I am running Ubuntu Server 9.04 x64, and nut 2.4.1-2ubuntu4 installed via APT. I am getting the error: Poll UPS [ups1 at localhost] failed - Driver not connected My conf files: (ups.conf) [ups1] driver=mge-utalk

Hi, I have had a long standing problem with NUT talking to 110V MGE UPSs on FreeBSD, I was recently investigating again and noticed that upsd seems overly noisy, eg.. May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5

(Note that I mentioned this *was* previously working with an older version of Nut). [irs2-ups1] driver = snmp-ups port = irs2-ups1.sum.naoj.org mibs = auto community = private irs2-ups1.sum.naoj.org responds to pings. On Tue, Oct 8, 2013 at 3:55 PM, Tim Rice <tim at multitalents.net> wrote: > On Tue, 8 Oct 2013, Philip Tait wrote: > > > Here is the upsc

Hi, you need a newer version of NUT. I was doing a similar project with that library and NUT needed some PRs to get it work. IIRC, v2.8.2 has everything needed. On Fri, Oct 18, 2024 at 4:58?AM linkinpiocz via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote: > Hello All, > > I have been trying to get NUT package working on proxmox host with > Arduino HIDPowerDevice

Hi there. I bought a generic UPS from a local (South African) hardware company, Sahara. They call it an "Electra 1000 Plus". From what I am told it is a 1000 VA line interactive UPS. It comes with "WinPower" Java based software that I couldn't get to work. (Crashes on start-up, without any explanation.) I would like to know if any one on this mailing list could help me

Hi, I have the above UPS connected to a FreeBSD 6.2 box and it shows 'data stale' very frequently (every few minutes). I have tried the usual trick of setting maxage, poll interval, etc etc but to no avail. When I wind up logging I see (on mge-shut) entering shut_get_report(id: 0d, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 16, len: 1800) shut_wait_ack():

Hello All, I have been trying to get NUT package working on proxmox host with Arduino HIDPowerDevice (https://github.com/abratchik/HIDPowerDevice) And I have been banding my head against the wall and looking through the internet why I am getting "Can't claim USB device [2341:8036]@2/0: Invalid parameter" error, but could not find anything relevant. The information : - OS name

Hello, I've got a setup with NUT, where we've got two UPSes, ups1 and ups2. UPS1 supports our servers, while UPS2 supports our desktop boxes. We monitor both of them via USB on a box now called "upsmon". The interesting point comes here. We monitor both UPSes on the upsmon box, but if UPS2 fails, which supports our desktop boxes, NUT shouldn't initiate a shutdown in

Hello I'm having a bit of a trouble to set up a Back-UPS on a production box. We're using the newhidups driver for this module here, in the office, and I'd like to monitor the one, out in our server farm. The situation is the following: # /lib/nut/newhidups -u root -DD -a ups1 2> ups1.out Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) this one worked

I am currently trying to use your NUT program to monitor a SMART3000RMOD2U TRIPP LITE device. I find that it connects with the in the device folder as hiddev0 and if I connect a second device it connects under hiddev1. I attempted to use your software with the driver=usbhid-ups and port=auto, but when I try to discover it it can't be found. Then when I run the command /sbin/usbhid-ups -a

On Tue, 8 Oct 2013, Philip Tait wrote: > Here is the upsc output: > > # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > 0.000000 debug level is '2' > 0.000327 SNMP UPS driver : entering upsdrv_initups() [snip] > 4.457750 No supported device detected I'm using a APC smart ups with a

Hi, I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified