similar to: automatic shutdown of UPS (and RAID1)

Hi, I have a CyberPower UPS connected to a Ubuntu karmic machine. All functions are working well. I can use upsc to see all the UPS parameters, power loss and battery low events are correctly detected, and shutdown is correctly initiated. If I run upsdrvctl shutdown, the UPS cuts power immediately. However, if I simulate a shutdown with upsmon -c fsd, the UPS fails to cut power. The

I am running Ubuntu 6.06 connected via serial port to an MGE Pulsar Ellipse 800VA. Have just installed NUT 2.0.3, and have problems with connectivity. This UPS was workign via serial connectivity to a BSD system only a few days ago. I have followed the instructions at http://opensource.mgeups.com/install/debian.htm The details... jason@ubuntu:~$ ls -la /dev/ttyS? crw-rw-rw- 1 root dialout 4,

Nut will monitor the ups and shutdown Linux when the ups goes to low battery as it should. But the UPS is not shut down so the system will restart when the power is restored. If I switch the UPS off , restore power and switch the UPS on the system will restart. I have not been able to get nut to switch the UPS off after it brings the system down. I can get the UPS to switch off with upscmd

Hello! I use online UPS MV-1000 LT http://www.230v.ru/catalogue/?id=production/ups-sm/master-vision for the power of my Linux server SLES 10 SP1. I downloaded, compiled and configured diver nut 2.4.1 from this link http://www.networkupstools.org/source/2.4/nut-2.4.1.tar.gz Here are my configuration files: --- srv:/usr/local/ups # cat etc/ups.conf [npower] driver = megatec port = /dev/ttyS0

I am testing EXT3 as a filesystem for a server whose power supply is failure prone. In order to do the test, I have a lever that I can control from PC1 that can press the reset button on PC2. PC2's reset button is automatically pressed once every 120 seconds (the boot sequence on PC2 takes 80 seconds). While PC2 is booted, PC1 directs email and web requests at PC2, so that the PC2 disks are

Hello, I'm using Archlinux x86_64 with linux-nouveau kernel (based on linux-mainline (that is linux-3.6)). I've installed nut-2.6.5. I first tried to use new systemctl .service scripts, but they are problematic. So I start and stop nut from /etc/rc.c script. This way, it "woks". Here are my config files : nut.conf : MODE=netserver ups.conf : [ellipse] driver = usbhid-ups

On Jun 20, 2013, at 10:35 AM, Louis Chaillet wrote: > With respect clarification of the documentation (and reference to your question Charles). The documentation does suggest that you can shutdown the ups by the upsdrvclt shutdown [ups] command. Specifically in "http://www.networkupstools.org/docs/man/upsdrvctl.html" in the section commands under warning. In the "Network UPS

With the Dell OpenManage question on my mind (and having seen it answered very well), I was reminded of an interesting and a little surprising thing I saw yesterday. I upgraded a PowerEdge 2850 from CentOS4 to Fedora Core 5 (keeping everything updated for GNUradio to run on CentOS 4 became more of a job that it should have) for our pulsar data processing machine (it has a GNUradio Universal

Hi all, I am trying to communicate to this Eaton Ellipse (see above) using nut from a Debian Squeeze system on Armel architecture. But have not succeeded so far. Version: Linux b3 2.6.39.4-11 #1 Tue Apr 3 21:45:12 FET 2012 armv5tel GNU/Linux Nut version is 2.4.3-1.1squeeze2 this information if from dpkg. NUT installation method:from debian package for armel. The problem is I cannot

Hi all. I have a Dell SC440 running Centos 4.4. It has two 500GB disks in a RAID1 array using linux software raid (md1 is / and md0 is /boot). Recently the root file system was remounted read-only for some reason. The logs don't show anything unusual, presumably the file system was read-only before anythng was logged. Running dmesg showed this error repeated many times: EXT3-fs error (device

Hi, Apologies if this is a known problem. I have just joined the list and haven't done an exhaustive search of the archives. Also I am no UPS expert, so please excuse me if some of my terminology is poor. I use an MGE Pulsar Extreme 700C connected via RS232 to the linux server it powers. I have recently upgraded to a new linux distribution. Both new and old use 2.6 kernels, although

Hello, I have two disks sda and sdb. One of the was broken so I have changed the broken disk with a working one. I started the server in rescue mode, and created the partional table, and added all the partitions to the software raid. *I have added the partitions to the RAID, and reboot.* # mdadm /dev/md0 --add /dev/sdb1 # mdadm /dev/md1 --add /dev/sdb2 # mdadm /dev/md2 --add /dev/sdb3 # mdadm

Hi to all, i install nut and it's work perfectly but when i start upsmon i recive the message: POWERDOWNFLAG (/etc/killpower) does not contain the upsmon magic string My upmon.conf contain: MONITOR myups@theseo 1 orion91 carlos81 master SHUTDOWNCMD "/sbin/shutdown -h +0" HOSTSYNC 15 POWERDOWNFLAG /etc/killpower FINALDELAY 5 My killpower scrit in /etc/killpower

I've googled this question without a great deal of information. Monday I'm rebuilding a Linux server at work. Instead of purchasing 3 drives for this system I purchased 4 with intent to create a hot spare. Here is my usual setup which I'll do again but with a hot spare for each partion. Create /dev/md0 mount point /boot RAID1 3 drives with 1 hot spare Create two more raid setups

hello, I installed with NUT UPS MGE Pulsar Evolution 2200 all orders of arrest, interrogation etc etc ... UPS work well However, I have a problem with the order in NOTIFYCMD upsmon.conf that not run ... I created a script that generates a simply log I indicated in upsmon.conf NOTIFYCMD / home / nut / alert_ups.sh below my upsmon.conf RUN_AS_USER nut MONITOR pulsar at localhost 1 admin1

Hello! We have two upses: MGE Pulsar M 3000 and MGE Pulsar EXtreme 3200C. They connect to server by USB. EXtreme works good with usbhid-ups (nut 2.2.1) and newhidups (nut 2.0.5). But Pulsar M doesn't want to work with usbhid-ups. - my ups.conf: [extreme] driver = usbhid-ups port = auto product = "EXtreme" [pulsar] driver = usbhid-ups port =

Hi Charles, thank you for your answer. This was indeed the core of the problem. I have amended the configuration files. It means now the communication works as required. Alas I now have another problem. Just for the record here is the configuration after the changes. The configuration is as follows. #nut.conf MODE=standalone #ups.conf [eaton] driver = usbhid-ups port = auto

> I'll try to manually call `upsdrvctl shutdown` to check if the UPS then goes to 'OL DISCHRG' I now tested the manuall `upsdrvctl shutdown` and the UPS goes to 'OL DISCHRG'. So I think nut is sending the shutdown command to the UPS during boot without setting FSD. Just a wild guess: I recognized the system time in syslog during the bootsequence is suspicious. It looks

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All