similar to: upsmon/upssched shutdown problem

UPSmon.py --------- I have been experimenting with a Python3 re-implementation of upsmon, upssched and upssched-cmd. This is currently in use on openSUSE and Debian boxes. It provides a much richer "language" for UPS management. For example, the key part of the well known "warn on [OB], shutdown on [LB]" approach is written as # Warnings when on-battery, wait for low

Hi All, I was wondering what people are doing to shutdown their equipment based on the temperature NUT grabs from a UPS? It doesn't appear that upsmon(8) has an appropriate notify event for temperature levels. For the time being, it looks like I'll write a simple perl wrapper around upsc to get ups.temperature, but would love to use something natively from NUT, if possible. Also,

Hi, I cant seem to get my upssched to get called by upsmon. Upsmon -c fsd just shuts down without the message I set or the one in upssched-cmd /etc/ups/upsmon.conf: MONITOR ups6 at localhost 1 <user> <pass> master MONITOR ups8 at localhost 1 <user> <pass> master SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/sbin/upssched NOTIFYMSG

Where syslog output ends up is an OS specific question and depends upon the configuration of the system logger in use. On most systems the logging information will be found in /var/log. On most Linux systems, the default system log is /var/log/messages. Denny > On Sep 20, 2018, at 13:30, Ito-Cole, Kaeny (Student) <Kaeny.Ito-Cole.stu at gtri.gatech.edu> wrote: > > First

Ah yes sorry I forgot to specify I am on CentOS 7 and the newest NUT for that is 2.7.2 On 9/21/18, 9:04 AM, "Denny Page" <denny at cococafe.com> wrote: Where syslog output ends up is an OS specific question and depends upon the configuration of the system logger in use. On most systems the logging information will be found in /var/log. On most Linux systems, the

Hi, just through setting up nut-2.0.2 I ran into a shutdown problem. As I have already spend some time on it and don't know any further, I like to ask for advice. Situation: Powerware 9125 serially connected using /dev/cua0 nut compiled and installed fine system shall - broadcast a message and shut down if ups on battery for 30+ s - wait 120 s - broadcast another message - give system 120

Using the HOWTO in http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ I installed nut on an Ubuntu Edgy LAMP Server with an Eaton Powerware 5110 attached to it via usb. But nut fails to start properly (see the error message "Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon" below). It then complains about communication with the UPS being lost ("UPS

Hello. I've tried to configure Windows (complete port, Beta): Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port but have no luck. Here is my config files: *nut.conf:* MODE = netserver *ups.conf:* [PW5115] driver = bcmxcp_usb port = notUsed desc = "PowerWare 5115" *upsd.conf:* LISTEN 192.168.1.12 3493 *upsd.users:* [monuser]

Hi all We're considering getting some Powerware 9355-30-M-0 UPSes to replace some older ones, so I wonder if it would be possible to use NUT for this. It seems 9315 is supported, but AFAICS that's the top model. Thanks roy -- Roy Sigurd Karlsbakk (+47) 97542685 roy at karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det

I decided to try this to see if it worked better since Powerware decided to build in some oddball USB protocol instead of using a HID UPS profile, but it doesn't seem to work. The USB/serial dongle is recognized by Linux and added as /dev/ttyUSB0, owned by group "dialout", so I had to add the nut user to the dialout group. In the compatibility list, the proper driver for the

Hello... I have a PowerWare 9120 attached via USB to my Debian system. My ups.conf looks like this: [ups1] driver = bcmxcp_usb port = auto desc = "PowerWare 9120" When testing the driver with "upsdrvctl -u root start" I get: Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Communications with UPS

Hi, just wanted to confirm that Fiskars UPS 9000 series (aka Powerware Plus 500 series) with optional UPS Information Unit works fine with upscode2 driver. Tested on Fiskars 9200 (20kVA/400V/3ph). Regards, -- Sebastian Zagrodzki Dzia? Sieciowy ICM, Uniwersytet Warszawski s.zagrodzki at net.icm.edu.pl (+48-22) 5520527, 8268009, fax. 8284195 http://www.net.icm.edu.pl/

Adam: Thanks for putting up this page. But something is wrong. In particular, our Powerware 9135 is a three phase UPS system with THREE 480 volt outputs. So the displayed voltage is not correct -- in fact there should really be THREE voltages displayed, all around 480v. Nut developers: I am copying the NUT mailing list to see if anyone can suggest how to fix this. NUT developers, see the

Hi there, all I have subj UPS, connected by USB. ups.conf: === [eaton] driver = bcmxcp_usb port = auto desc = "Eaton Powerware 9120 3000" override.battery.charge.low = 91 === upsmon.conf: === NOTIFYCMD /sbin/upssched NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC === upssched.conf === CMDSCRIPT /etc/nut/ups.sh AT LOWBATT * START-TIMER battery 3 AT ONLINE *

Hi everyone, First of all a big thank you for the NUT package, I've been using it for years and couldn't get by without it! I have two Powerware UPS's here, a 9120/1500va and a 5110/700va. The 9120 has used a hacked bcmxcp driver (serial) from the 2.0.2 nut version for about a year now (which I'll explain more about in a seperate email to the dev list), and the 5110 which I just

2009/1/22 Spiros Ioannou <sivann at gmail.com> > Cher Arnaud, > Hi Spiros, > I send you a demo that reads info from an Emerson Liebert > GXT2-10000T230 through the RS-232 port. This uses the "ESP-II (ESP 2) > Protocol". > Current supported data includes: measurements (voltage, temperature, > etc) , ID strings (serial number, etc), status flags (inverter on,

Nut for Windows 2.6.3-3 + Eaton/PW 5110 (103004256-5591). I had to manually install libusb driver and I'm using bcmxcp_usb. upsd.exe is reporting to me "Out of memory". It will run, but once anything connects to the daemon, it dies with that message. I don't have much experience with NUT yet so I'm not sure what the next course of action is. I do have NUT for Windows

THE GOOD: NUT is able to communicate with my Powerware 5115A over USB using the bcmxcp_usb driver: ambient.temperature: 38 battery.charge: 99 battery.runtime: 9000 battery.voltage: 27.07 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.1 driver.version.internal: 0.13 input.frequency: 50.34 input.voltage: 235 output.current: 0.0

Has anyone gotten the newhidups driver to work w/ the Powerware 9120 series? Here's what I get for debug info (It's the Phoenixtec device): $ sudo lsusb Bus 002 Device 002: ID 0846:1040 NetGear, Inc. Bus 002 Device 001: ID 0000:0000 Bus 001 Device 002: ID 06da:0002 Phoenixtec Power Co., Ltd Bus 001 Device 001: ID 0000:0000 $sudo /lib/nut/newhidups -DDDDD auto Network UPS Tools: New

My UPS is an Exide NetUPS SE PRC1500i (1500 VA), also known as Powerware 5119, according to Karl Schmidt (http://lists.alioth.debian.org/pipermail/nut-upsuser/2005-July/000026.html) also Deltec PowerRite Pro II, and according to http://www.usedups.de/compaq_ups.html also Compaq R3000h. I am not sure if the information in http://www.bps.hu/powerware/model_en.html is to be interpreted as that it was