similar to: Automatic restart if power is restored after automatic shutdown?

Hello.... I'm testing the functionality of my NUT-setup (NUT 2.0.4-4 - Debian stable). The system is connected to the UPS, but is not powered by it. When running "upsmon -c fsd", upsmon says "Auto logout and shutdown proceeding". This is all well and good, but I never see the machine waiting for the UPS to cut the power. Instead it shuts down. It's my

Hi everybody, I've got an Unitek iZi UPS 525 with a serial interface. The supplied cable looks fairly simple: RX->RX , TX->TX and GND->GND. Using this cable and Minicom with 2400 8N1 I'm able to issue commands to the UPS using the "Megatec Protocol" http://www.networkupstools.org/protocols/megatec.html so I know the UPS is fairly "intelligent" :-) and the

Hi List, I just got myself a new everpower-1000va. according to the compatibility list, the 'safenet' driver supposed to support it, however, when I try, I get this in syslog: Jul 24 15:05:22 tv upsd[26458]: Can't connect to UPS [everpower1000] (safenet-ttyS1): No such file or directory this is my ups.conf: [everpower1000] driver = safenet port = /dev/ttyS1 desc =

Hi all! As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have a question regarding ups.delay.*. The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary number of seconds, i.e. they wait for n seconds and then shutdown or kill. The delay for the restart after the shutdown can't be changed. Which of the ups.delay.* variables correspond to these values?

Hi all! As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have a question regarding ups.delay.*. The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary number of seconds, i.e. they wait for n seconds and then shutdown or kill. The delay for the restart after the shutdown can't be changed. Which of the ups.delay.* variables correspond to these values?

2006/11/16, Arjen de Korte <adkorte-guest@alioth.debian.org>: > Author: adkorte-guest > Date: Thu Nov 16 21:16:40 2006 > New Revision: 585 > > Modified: > trunk/ChangeLog > trunk/conf/upsd.conf.sample > trunk/server/conf.c > trunk/server/upsd.c > trunk/server/upsd.h > Log: > upsd: add MAXINIT parameter to upsd.conf to make the time upsd

Hi, I'm just looking at the code of snmp-ups driver in the source tree. I'm trying to find out, what can I change in the code to force the snmp-ups driver to send shutdown command to the upsd to shutdown the computer when I set up on the UPS via telnet that it should restart gracefully. The communication otherwise works perfectly but the gracefull restarts and turn off. Using apcsmart

Hi. Could anyone please provide info on how nut makes ups restart after power is back? I've configured nut to communicate with APC SmartUPS 750 via 'newhidups' driver and this works w/o probs in case of shutting the system down. The UPS would stay on though. After the power returns, I'd expect UPS to restart so that servers would start either. This would never happen, and I have to

I did a test shutdown on a nut controlled UPS and it all went as expected except that when it got to: /usr/local/ups/bin/upsdrvctl shutdown Nothing happened. So the halt script went on and shut down the system. I waited a while but the UPS never turned itself off. Am I doing something wrong, or does this UPS not support this function? Thank you, David Mathog mathog at caltech.edu Manager,

On a test shutdown of an APC Back-UPS RS1500 upsc was run periodically to follow the UPS discharge, it showed these values: battery.low 120 battery.charge.low 10 As it turned out, the battery.charge.low was encountered first and the system shut down there. However, considering the rate at which the charge was falling at the end I would much rather have had it shutdown sooner than it did. Is

Hello. I have a PW9120 hooked up via a serial cable running NUT 2.0.4. When running upsc I cant see any parameter that looks like it would trigger a shutdown. Theres is nothing like "battery.charge.low: 30" or "battery.charge.warning: 30". I get: ambient.temperature battery.(charge|runtime|voltage) driver.(misc) input.(misc) output.(misc)

Hi again, it seems to me that "upsdrvctl shutdown" fails to pass the "-u" flag to the driver. See drivers/upsdrvctl.c:shutdown_driver(), and compare to start_driver() in the same file. This has been so since ancient history (I checked back to 1.5.0), so there must be a reason, but I can't think of any. I have a good reason for passing "-u root": at the time

Hi there I have a Mustek PowerMust 1000 USB using serial port /dev/ttyS0. I use nut 2.2.1 with the megatec driver on Debian Lenny (testing), running on an AMD64 X2. (I was using a Debian Etch as slave, but to keep it simple I turned it off) My problem is that sometimes the UPS is running OK, but when the message "UPS is trimming incoming voltage" appears on knutclient (i.e. OL TRIM in

Hello, Being new to this list and to Nut, maybe my question has been asked before but I didn't find a clear answer. My question is : is it possible to make nut aware of the percentage (or duration) of time before the UPS exhausts its power ? Thus making Nut conditionning the shutdown of the servers depending on the remaining load. I saw this thread on the mailing list :

Hello, I'm using driver newhidups with APC Back-UPS CS 500. Most things works fine except the following: After I disconnect the UPS the upsd write "Data for UPS [apc] is stale - check driver" in /var/log/messages. In the same second it tells "UPS [apc] data is no longer stale". This repeats all the time the ups is disconnected: Jan 25 14:45:03 degpn026w226 kernel: usb

Hi I am thinking about using the existing NUT software to tell the slave servers to shutdown if the temperature in the server room becomes too high. I was thinking of monitoring the temperature on the master NUT server and then just letting the slave clients shut down. But the slaves (and master server) needs to do a complete power off even though the UPS's does get 220v power all the

Hello, I had a brief power fluctuation earlier, which caused the UPS to power up a few seconds. Then suddenly NUT was busy shutting down my server, after full power had already been restored. Here's the logs: Jun 6 13:28:30 hell upsmon[607]: UPS apc620 at localhost on battery Jun 6 13:28:35 hell apcsmart[602]: Communications with UPS lost - check cabling Jun 6 13:28:35 hell upsd[604]:

Hello, My APC Ups uses nut to manage all systems connected to it. But if online power failed until it shutdown, it not restart automatically after the power returned. It stay down until i restart it. When i execute the command: # upsc siUps1 it output me this: battery.alarm.threshold: L battery.charge: 018.0 battery.charge.restart: 15 battery.date: 03/31/07 battery.runtime: 120

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb