similar to: upssched timer configuration with redundant UPSes ?

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:

Further information on this issue, attn. Arnaud Quette: Here is the result of a test I made a few days ago. I've pulled the input plug on the UPS and watched the 3 critical OIDs through a MIB browser: - 1.3.6.1.4.1.232.165.3.4.5.0 goes from 3 (OL) to 5 (OB) (as expected => good) - 1.3.6.1.4.1.232.165.3.7.3.0 stays at 1 (OB) (=> seems meaningless) - 1.3.6.1.4.1.232.165.3.7.4.0

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

Hello Arnaud, On 05/04/14 22:01, Arnaud Quette wrote: > Philippe, Ivan, > > please see https://github.com/networkupstools/nut/issues/118 > and send back your data. I've pasted the requested files in github, but the auto-formatting may have damaged them, so here they are. Also, when I ran gen-snmp-subdriver.sh, it gave me the following message:

On 23/06/14 04:32, Stan Gammons wrote: > Can one have a single UPS powering multiple servers and have them all > shutdown in an orderly fashion pending a power loss? It seems as > though this is possible from what I gathered from the docs, but I've yet > to make this work on an OpenBSD and FreeNAS machine that are powered > from the same UPS. The master server that the UPS

Hi, I've stumbled over a race condition in upssched when using 3 or more UPSes in combination with START-TIMER/CANCEL-TIMER. I have a solution that works but is ugly, so I'm going to describe the bug here in the hope somebody can come up with a better solution. The problem is in upssched.c:629 check_parent() (see https://github.com/networkupstools/nut/blob/master/clients/upssched.c ).

I am having an extremely strange issue with a BL460c1 (G1) blade on a c7000 enclosure. I could not for the life of me get the machine to ping the gateway or any other blade on the same enclosure (yes, the subnet mask was correct & quadruple-checked); although pinging to the local IP works. I was almost convinced that it was a network or hardware issue; until I asked someone to try

Hey all, I found a pinout of powercom's Kingpro UPSes in their manual. http://www.powercom-ups.com/manuals/kingpro.pdf Page 11. Unfortunately, this doesn't give PROTOCOL details. Does anyone have a "first step" at how to decode that? (for example, how to gauge line speed, how to "snoop" the serial port under windows? (for which the only software exists right

Hello all, I am a long-time user of NUT (since last millennium, or so it seems) and beside Linux where I've started, I also integrated it with our Solaris 8 and 9 servers' shutdown procedures - avoiding the possible "hole" when the line power returns right at the bad moment when UPSes and systems are already told to power off. In this case, they see no event like "I am

I need a little help on this problem, please? I include my /etc/apcupsd/apcupsd.conf file is attached. port 3551 udp/tcp has been added to the (running) firewall. My APC is recognized as: APC Back-UPS 450 FW:844.Kld.D USB FW:Kld This from the hardware browser. PS says: root 2419 0.0 0.0 4196 584 ? Ss Mar23 0:09 /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf Is group 2419 the

Philippe Andersson I think tried to respond on this thread but all I see is your corporate email signature? I did some more troubleshooting tonight. TL;DR at the end. First, confirmed that NOTIFYCMD is in fact firing. So I changed it to: NOTIFYCMD logger "NOTIFYCMD FIRED!" followed by: sudo service nut-client restart and that message does show up in /var/log/messages when I pull the

I finally got this working, for the sake of anyone else who comes across this thread with a similar problem: Since NOTIFYCMD was working fine with bash scripts, I had it point to a bash script which I used to call my python script, and I set up the bash script to capture errors and write them to a log file: /etc/nut/ups-log.py > /home/pi/Documents/scripts/mylog 2>&1 I didn't realize

I'm struggling to configuring nut for MGE Pulsar Ellipse 800 (at least Ellipse 800) for two boxes - home firewall and file server. I'm using Debian 4.0 Etch, every one of them. I'm built (after some dangerouse experiments) a testing configuration, where boxes are plugged to line, server playing as a master, firewall as a slave, and UPS connected to an electric heater about 300 Wats (no

Good morning, I''m new to rails and am having some basic questions in development. See if anyone can help me with a test problem. I need to test if my model "Procedure" is linked to the workflow. If not, the system must acknowledge an error. Below is the code that is in the file test \ unit \ procedure_test.rb. require ''test_helper'' class ProcedureTest <

Hello Tomasz, first, thanks for your feedback. > First of all, I want thank you for excellent NUT software :) It saved my ass > from BIG pain :) > > I want to confirm that NUT works with ActivePower UPSes (ActivePower is Polish > company). I have two machines: > > 1st machine: > * mainboard: Asus ATX with Intel Celeron 2.53 GHz, > * OS: openSUSE 10.1, > *

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

Philippe, Ivan, please see https://github.com/networkupstools/nut/issues/118 and send back your data. cheers Arno -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140405/682f10dd/attachment-0001.html>

I'm now doubting if I've made this statement or not, so here it is: newmge-shut is *not* ready for production usage! I've lately found some bugs during the MGE PSP 3.0.4/3.0.5/3.0.6 updates. So for the moment, prefer to keep using mge-shut. 2007/10/25, R?zsa G?bor <mailer.tovis at freemail.hu>: > newmge-shut ??? > Shutdown, switch of ups does not work. Using command >

On Tue, Mar 18, 2014 at 1:02 AM, Spike White <spikewhitetx at gmail.com> wrote: > I have a question on how to deal with a quirk of the Intel Boot Agent. > Both for PXE boots and for EFI boots. > > I've noticed this IBA quirk for years. According to the "DHCP options" > RFC, variable length DHCP options are not necessarily null-terminated. > So if I specify

upsmon.conf using NOTIFCMD and NOTIFYFLG is working well, it is calling my script "notify" on requested events (ONBATTERY,LOWBATTERY and ONLINE). Command #upsmon -c fsd -u monmaster myups at localhost gracefully shutdown my box and after several seconds switch off the ups's load. Two problems: - notify script is called and executed as user "nut" (as it used to be