similar to: mge-shut doesn't use lowbatt parameter

Hi all, First of all thanks for the great work on nut ! (despite it's not fully functional yet overhere). Everything seemed to go fine until the final test : shutdown the UPS ! The system is running FreeBSD 5.3, the UPS is MGE Ellipse 800 USBS both linked with the MGE serial cable. The system is a remote server, only running some file services and large disks. The porting,

Hello happy nuters, Some complementary words about making nut 2.02 successfully run on FreeBSD with MGE Ellipse. With the usefull information Arnaud sent, it's rather obvious that the erratic response of the ups to the shutdown script is linked to its difficulty to handle large traffic on the serial line. These are the final tweak I made to have this configuration satisfyingly

Hi, We have been testing an MGE Pulsar M 3000 and found that the lowbatt doesn't appear to do much. You can see it in the output of upsc but battery.charge.low is still the default. Setting battery.charge.low with upsrw does seem to 'stick' though so I we can use that. Mostly I'm wondering what the driver param is for :) -- Daniel O'Connor software and network engineer

Hi, I took the advice of Daniel O'Connor, found out what variables I had available to me, and put them in the conf. So now it looks like : [ellipse] driver = mge-shut port = /dev/cuaa0 desc = "UPS" lowbatt = 5 offdelay = 120 let the UPS charge up fully, 24 hours. I plugged a single lamp into it, with a 60W bulb. At 3:40p

Fixes RHBZ#596238 --- lib/Sys/VirtV2V/Converter/Windows.pm | 57 +++++++++++++++------------------ 1 files changed, 26 insertions(+), 31 deletions(-) diff --git a/lib/Sys/VirtV2V/Converter/Windows.pm b/lib/Sys/VirtV2V/Converter/Windows.pm index 8de2bcd..e55d0f3 100644 --- a/lib/Sys/VirtV2V/Converter/Windows.pm +++ b/lib/Sys/VirtV2V/Converter/Windows.pm @@ -181,9 +181,8 @@ sub _preconvert

Hello, looking for replacements for some older Powerware equipment I found the MGE Pulsar Extreme 1000C and I'm currently testing one with nut-2.0.3 on a self-brewn i386-linux. Upto now everything seems to work fine - except I can't get the power outlets switching on again after mains returns. As this works with Personal Solution-Pac 2 on W2k I thought that there might be a way to

Hi Has anyone got a Compaq(/HP) T700 UPS to work with the BCMXCP driver? I've built yesterday's CVS of NUT 2.1 on one of my FreeBSD systems but chown root:wheel /dev/cuaa0 /usr/local/libexec/upsdrvctl -u root start gives: -- Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools - BCMXCP UPS driver 0.10 (2.1.0) Communications with UPS lost: Error executing command

Hokay. It appears that enumdrivers / getdriver in rpcclient is broken, and won't be fixed soon. I'd fix it meself, but hey, I'm too busy clearing skyscrapers in a single bound and moving faster than a speeding bullet. Or maybe I looked at the cvs once and got REALLY scared. Unfortunately, I can't wait, so I've come up with a nasty hack to help us with querying samba for the

I'm not sure I understand your question. The UPS was running for more than 15 minutes before it went below the battery.charge.low: of 70. Below is my /etc/nut/nut.conf. My goal is that when the UPS report a battery.charge.low of < 70 (or, if possible has been running for 5 minutes) it starts the shutdown process. The shutdown process should take 15 minutes so that proxmox can shutdown

The code for mounting the transfer iso in Converter::Windows didn't do the same level of error checking as the same code in GuestOS::RedHat. This change moves the GuestOS code into Config, and updates both GuestOS::RedHat and Converter::Windows to use Config. Fixes RHBZ#596091 --- lib/Sys/VirtV2V/Config.pm | 51 ++++++++++++++++++++++++ lib/Sys/VirtV2V/Converter/Windows.pm |

All, I'm using the Powercom driver from 2.2 (not the one recently mailed to thelist). Since it's a KIN2200AP, I'm using the driver settings right from the manpage. All the values look "sane" when I'm on-line, but note some of the odd values (<-- Here) when on battery: Also, does anyone know if this UPS supports logging of the "boost" or

Some one might have answerd this, but I can not find any think yet I am trying to load a SOLA 610 700va ups up and keep getting : --------------------------------- Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.88 (2.0.5) .Detected Pulsar ESV11+ on /dev/cuaa0 Network UPS Tools - Best UPS driver 1.03 (2.0.5) Unknown model detected - please

Hi, I just got at work an MGE UPS Comet EX RT 7 and I can communicate fine with it through mge-shut, it detects correctly when on battery. I am using Nut 2.0.3 on Linux (RHEL 3). I am trying to simulate a low battery condition to test my shutdown procedure by setting lowbatt to 98%: driver.parameter.lowbatt: 98 but the ups reaches this value, goes to 97% and still no LB. I tried to change,

This is my lightly tested patch which allows pre-conversion of Windows guests. You also need to supply rhsrvany.exe and firstboot scripts. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc.

Hi, FINALLY got my UPS working, YEA!!!! But now it brings up even more issues.. (BOOO!!) 1) I'm thinking this is a UPS issue, but when I pull the plug on my UPS, it goes from 100 to 30 in just a short amount of time (Minutes). This causes the machine to shut down. But once it gets to 0, its beeped its little heart out for a few more HOURS providing power to the non-system items perfectly.

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

Hello, It's a bit off topic, but I'm hoping someone has seen this before. I'm running a couple of headless boxes, one is 4.7 release, the other is 4.8 release. Both have the same issue with newsyslog when I've got the serial port enabled for console management. (-h in boot.conf and a getty running on cuaa0 after the boot process) Logrotate tries to send an HUP to syslogd, but

> If you set lowbatt=70 then the behaviour you are seeing is normal. Don't > set lowbatt and you'll get the default manufacturer settings which is > LOWBATTERY at 30% charge level. > > Philippe Thanks for quick response! I realized this and forget this setting! For now I think that my box does not recognize signal about low battery - I'm only started to read SHUT

Dear folks, According to mge-mib.c (NUT 2.6.2) LB condition is gained from variable .1.3.6.1.4.1.705.1.5.14.0 (i.e. upsmgBatteryLowBattery.0). The test device of me does not set this variable to yes(1) even if runtime drops below the preconfigured limit. I complained about this at Schneider Electric. They replied that low battery status is indicated by .1.3.6.1.4.1.705.1.5.14.0

Hello everybody, Our supoprt team is facing a problem which froze the CPU. They suspect that this happens after an automatic battery test, which lets the battery goes down to 30% and then stop the test. At this level of charge, our kernel also triggers a shutdown (CPU and UPS). I saw (in the doc found here : tools.*mge*ops.net/download/intl/products/*ellipse*-asr/28-umeasr_08.pdf) that this