similar to: Three scenarios for simplifying NUT configuration on Linux

I've spent the better part of two working days reading the NUT code and documentation and thinking about typical modern use cases for the software. I'm now questioning whether I want to get any further involved with this project, because it seems to me that the codebase is a huge and complicated pile of machinery mainly aimed at solving problems that no longer matter. I could be wrong

On Jul 9, 2014, at 6:31 AM, Eric S. Raymond <esr at thyrsus.com> wrote: > What I'd like to do is this: confer in real-time, perhaps via IRC, > with someone who knows this process. Ask about every step (thought > processes and diagnostics). *Write them down* and turn this into a > document on how to qualify and support a new device. Happy to help, but scheduling something

was: Re: [Nut-upsdev] usbhid-ups.h: hid_info_t structure On 8/2/07, Peter Selinger <selinger at mathstat.dal.ca> wrote: > All this needs to be replaced by a re-designed, cleaned-up data > structure. It's on my to-do list, but nothing on that list will get > done by me anytime soon. As nothing is technically broken, and the > changes are prone to introducing subtle bugs, this

On 1/2/07, Eric A. Hall <ehall@ehsco.com> wrote: > I can hack up a Cacti PHP script to monitor UPS state via the upsc client > in the meantime. I'll have to manually enumerate the UPS names associated > with a host target (is there a way to probe for them with upsc now?), but > otherwise it ought to be pretty straightforward scripting. NUT developers, The NUT protocol

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

Additional question: I noticed on the HP Website that the latest version of "CPQPOWER.MIB" (1.76, dated Sept. 19, 2013) was more recent than the related file (./drivers/compaq-mib.c) in the NUT driver. Is the MIB structure as implemented on the management card perhaps no longer in line with the NUT driver ? The latest MIB file can be downloaded from the following URL:

Hi Occasionally I get emails from my NUT system saying that one of my UPSes lost power for about a minute. Losing power: Date: 15. nov 2010 17.40.25 CET regaining power: Date: 15. nov 2010 17.41.34 CET 69 seconds later. But why? None of the 3 other UPSes reports any power loss. What is the problem? So I made some scripts that logs the input, output and frequency at the time of power loss,

Hi Ted there was a drift from the initial topic. worth a new thread! 2014-07-27 9:13 GMT+02:00 Ted Mittelstaedt <tedm at mittelstaedt.us>: > On 7/26/2014 12:18 PM, Arnaud Quette wrote: > >> Hi Eric, >> >> sorry for the lag, summer time... >> >> I'm first seconding Charles comments >> >> 2014-07-09 12:31 GMT+02:00 Eric S. Raymond <esr

Carsten, This is a common issue in technology when you have complex products that the majority of consumers of those products do not understand how they operate. If most UPS customers understood the importance of standardization they would have refused to purchase non-standard UPSes and all UPSes would have long ago standardized on a single management protocol. The normal thing is that product

On 7/9/2014 6:51 AM, Charles Lepple wrote: > On Jul 9, 2014, at 6:31 AM, Eric S. Raymond<esr at thyrsus.com> wrote: > >> What I'd like to do is this: confer in real-time, perhaps via IRC, >> with someone who knows this process. Ask about every step >> (thought processes and diagnostics). *Write them down* and turn >> this into a document on how to qualify

Hi guys, I have a couple Mitsubishi 2033C UPSes that I badly want data from. We used to have Mitsubishi Netcom devices which took the serial output and provided a web interface, SNMP, and email alerts. All of those devices died. They're really awful devices (they're clunky and have 386s in them) and not worth the pricetag for a replacement. The closest replacement I've seen

My UPS Powercom WOW-1000U does greatly work with NUT, but not auto-cofigurable... This UPS is not usb-hid ups, and works well with this settings in NUT: [powercom] desc = "powercom" driver = powercom port = "/dev/serial/by-id/usb-POWERCOM_CO.__LTD._USB_to_Serial-if00-port0" type = IMP lsusb -v fragment attached. Unlike other UPSes, gnome-power-manager does

Here are three wishes for the future of upsmon: 1. The NOTIFYMSG texts should allow UTF-8 encoded messages. 2. The flags used in NOTIFYFLAG should be extended to include USER. This flag says that the message is to be sent to the notify daemon, perhaps with the command notify-send -a NUT -t 604800000 -u critical <message> This will allow the users of a workstation to see the

Hello list, I've installed NUT on an HP blade server, and I try to get it communicating via SNMP with 2 HP R3000 UPSes, each fitted with a AF465A management card. To do this, I used the snmp-ups driver, and configured it for the "cpqpower" MIB. Communication with the UPSes is established. My problem is that both UPSes constantly return the "OL OB" status which, in

Hi One idea I&#39;ve had for some time, but unfortunately not had time to implement, is to add a general SNMP agent, which will work with all UPSes supported by nut. The idea is to have the SNMP agent use the "nut API" to fetch values from the UPS. So the SNMP agent will be similar to the "upsc" utility. Whenever the SNMP agent is queried for information, it will use the

some notes: - for this kind of discussion, please cc upsdev list (I've added it), - I've fwded the full thread to upsdev, - this subject is part of what I call NUT-NG (next gen.), aka nut 3.0... - I'll study in depth the thread this week end, and complete with my thoughts, - thanks to Stan to have put us all in touch Arnaud 2006/3/10, Stanislav Brabec <sbrabec@suse.cz>: >

Dear Ted, Am 07.11.2014 um 17:47 schrieb Ted Mittelstaedt: > On 11/3/2014 9:25 PM, thomas schorpp wrote: >> Hi Ted, >> >> Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: >>> >> >>> Note that since the UPS relies on the voltage from the battery pack to >>> determine state of charge, it is quite useful to add in the battery pack >>>

Hi, my name is Sebasti?n from Spain I need help for that. I have 2 salicru ups I need monitor with a fedora 14 pc. Someone knows if i can configure ups.conf to monitor one or another ups? only make a upsc "ups" for take data. The upses are connected via usb and nut always read the first one connected. The upses are the same model. Thanks for all! Sebasti?n Le?n del Moral urticaries at

Hello, We have two APC Back-UPS RS 1500 USB stuff, and i've got a bit of a problem with it and NUT. The usbdevs output: addr 2: Back-UPS RS 1500 FW:8.g8 .I USB FW:g8, American Power Conversion addr 3: Back-UPS RS 1500 FW:8.g8 .I USB FW:g8, American Power Conversion (UPS1 and UPS2) I've configured our NUT system to monitor the UPSes, and it went very fine till the time had arrived for a

Hi All, About a month ago APC announced they were including MODBUS protocol support in their new APC UPSes. The technical note on this is here: http://www.apcmedia.com/salestools/MPAO-98KJ7F/MPAO-98KJ7F_R0_EN.pdf "Application Note #176 Modbus Implementation in APC Smart-UPS" The APC "announcement" appeared on their site in their user blogs by an APC employee, here: