similar to: Multiple servers connected to the same UPS

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

Hello, I'm using nut with my MG Ellipse on serial port. No problem since one year. Two days ago, I wanted to add a phone alert through my asterisk box when power is down. Since then, upssched doesn't make his job anymore. here is the "syslog" I get when the power cord is unplugged : > > May 9 11:39:34 serveur upsmon[6411]: UPS ellipse@localhost on battery > May 9

Hello, The UPS I am developing a driver to is able to report several flags for critical hardware conditions, like overheat, overload, inverter failure, output short etc. What should be the correct policy of operation when such a condition occurs? I think that the an UPS in such a condition is not reliable and therefore a system shutdown should be called. However, the developer's manual and

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>

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:

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:

Hi Charles, Thanks for your help. Seems to be mostly ok except am getting error access denied. See below. I see from searching this is a common error but so far I can't find a fix. This is how I configured things before make and install. created group nut nut:x:103: created system user ups with group nut. ups:x:123:103::/home/ups:/bin/bash Create statepath directory. sudo mkdir -p

Dear nut users, I am fighting to configure a smooth server shutdown with an ubuntu server and a dell usb ups using nut. It seems that the drivers connect properly (upsc gives very coherent outputs). However I can't get anything to happen when the ups goes on battery. How can I be sure the the UPS status is really monitored ? Is there a particular log file where I upsmon reports problems

I'm trying to use a Nas4Free storage system. This same hardware worked fine on Freenas 0.7.2. O/S: Nas4Free 9.0.0.1.148 which comes with nut 2.6.4. UPS is an APC Back UPS RS 800. USB interface. Driver : usbhid-ups Port: auto my NAS is communicating with the UPS, but in testing power failures, I'm not getting the shutdown to be handled properly. When I pull the AC plug on the UPS,

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

Hi there! I'm a n00b NUT user trying to get it running on RHEL5 and actually do something useful for me. Few questions: 1) I want it to notify me by email on power loss and power back events. I can't find any sample scripts for this purpose... Where shall I look for them? 2) So far, I've backported the package from Fedora and got my Ablerex running (previously used with Upsilon /

I just went through the same issue. Take a look at my thread. Double check that upsmon.conf:NOTIFYCMD /sbin/upssched is not still commented. On Tue, Feb 11, 2020 at 7:00 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to > nut-upsuser at alioth-lists.debian.net > > To subscribe or unsubscribe via the World Wide

On 04/01/2017 03:14 PM, Dan Craciun wrote: > On my Nagios monitoring system I use check_nut_plus (that in turn > calls upsc) to monitor the status (ups.status), load (ups.load), > battery charge (battery.charge) and runtime (battery.runtime). > > If these return "unknown", it means upsd is no longer monitoring the > UPS. As long as you get data, upsd is working. >

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]

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

Hello list, I am a pretty green Linux admin managing 3 ROCKS CentOS clusters total about 2,000 cores. My predecessor set up NUT for me on the primary head node. We have about 42 Tripplite UPS units in the room. The way our power systems work I intend to use the NUT connected head node to shut down the entire server room any time power is lost for over 30 seconds or so. It is about 95% likely that

On 09/19/14 07:23, Charles Lepple wrote: > On Sep 19, 2014, at 7:26 AM, Stan Gammons <sg063015 at gmail.com> wrote: > >> --enable-debug-log was in the original makefile. I added --enable-debug. At this point I guess trying to build from source or go back to OpenBSD 5.5 are the only options left. > Ah, my confusion was that --enable-debug-log was wrapped in ".ifdef

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120104/34be491b/attachment.html>

Hi all, I've not been able to find the answer to my timer problem in the faq or the archives. (or google) Basically, I can't get timers to fire. They fire ignoring the timer value, as if the timer was set to 0. I'm using the OpenFiler distribution, patched to the latest and greatest. upsmon 2.2.2 When I pull the power plug, I see the text "Im In Battery" instantly, instead