similar to: No subject

tags 441342 upstream thanks Hi Robert, thanks for your report and investigation. We will check to fix this and give you news back. 2007/9/9, Robert Woodcock <rcw at debian.org>: > Package: nut > Version: 2.2.0-2 > Severity: important > > I recently set up nut at work to monitor the 15 APC Smart-UPS 1500s we have > in our server room. Since we currently only have one

charge, but instead will be raised a few seconds before the power will be cut by the UPS, either because of a low battery event or a user initiated shutdown (with delay) command. The thing I don't like about that, is that by that time the shutdown sequence has apparently already started by the UPS, which means that we have no control over when the power will be cut. Also, if it indeed only

Hi to all, I am new on the lists but using nut on megatec for last two and half years. Looking at archives I saw that there is a lot of people confused about battery voltage and I want to help them to clear out some stuff in their heads. This story is based on my experience with UPS devices from 600VA to 20kVA, from single phase systems to three phase systems, with battery packs from 1

Hi David and fellows, I'm reviving this important thread about a common power management. To sum up, the first aim is to allow a better user experience on Linux by bridging NUT with Linux HAL, and Gnome Power Management / any PM GUI. But it also initiate a bigger investigation about how to integrate NUT support for UPSs into the native OS Power Management infrastructure for all supported

Hi Powermen ;-) I recently came across the Powerman project (http://sourceforge.net/projects/powerman/), pointed by Tony Merenda, from Opengear (thanks Tony). Congrats for your work in this area! I've thought a bit about Powerman and NUT since then... NUT currently supports hosts of UPSs and few PDUs (RPCs), and provides tons of features: http://test.networkupstools.org

There's supposedly another way with a custom upsmon.conf: NOTIFYMSG type message upsmon comes with a set of stock messages for various events. You can change them if you like. NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "Someone pulled the plug on %s" Note that %s is replaced with the identifier of the UPS in question. The message must be one

I'm setting up a NUT server. During testing, I have deployed it on both CentOS and SUSE. I have both servers looking at two physical UPSs and two "dummy" UPSs. My NUT client is running on Solaris and is rigged to look at the "dummy" UPSs. As I toggle states on the dummy UPSs, the client correctly detects the changes and throws a message of the type: > Broadcast

Garrett, I hope you're not barking up the wrong tree because that's exactly what I'm working toward. The web display was pretty straightforward. I haven't worked out the email notification part yet but it seems like it should be doable. -Charles From: Nut-upsuser [mailto:nut-upsuser-bounces+fairfaxc=missouri.edu at lists.alioth.debian.org] On Behalf Of Garrett Michael Hayes

This was the secret sauce! I first modified my BASH script to stuff the output of the 'set' command into a variable, then passed that variable in to my email command. Then I triggered an event and saw what variables were there in the body of the message. Voila! $UPSNAME and $NOTIFYTYPE were there and available. I modified the script to pump THOSE into the mail command, and the problem

Hi Guys, I'd like to submit a patch to enable NUT to communicate with APC 5G UPSs. The current usbhid-ups driver recognises APC UPSs by the Vendor ID and Product ID of 0x051D and 0x0002. This needs to be amended with the new Product ID of 0x0003. (See attached file: apc-hid.patch) Secondly, when Nut polls the UPS via the interrupt channel, these will time out, resulting in frequent lost

I'm running a single "nut-server" that monitors seven ups units. In upsmon.conf: MONITOR ups-1 0 <User> <Pw> master MONITOR ups-2 0 <User> <Pw> master MONITOR ups-3 0 <User> <Pw> master MONITOR ups-4 0 <User> <Pw> master MONITOR ups-5 1 <User> <Pw> master MONITOR ups-6 1 <User> <Pw> master MONITOR

I have been happily using NUT to monitor a couple of Eaton UPS. These are independent UPSs, each driving one "leg" of the power in our data center. In this scenario, I've told my clients they need to have one UPS working and to shutdown when the last UPS reaches critical battery. I have recently learned that our power arrangement will be changing to a parallel-fed/redundant

On October 31, 2017 4:09:46 PM GMT+01:00, Garrett Michael Hayes <Garrett at VerbalImaging.com> wrote: >Greetings Gentlebeings, > >I have started deploying a number of NUT instances on Raspberry Pi >machines (Raspbian Jessie) across my network. The purpose of these >"nutcases" as we refer to them is to monitor the status of the UPSs >supporting our network

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm in the process of upgrading my solution to spread the load over two ups'es. Both are Cyberpower, where one is the classic "Intelligent" 1500LCD, the other a "Value" 2200E Both connect via UPS, and both work using the ups-hid driver. So far so good. The idea is to connect both of them via USB to the same FreeBSD 8

I have three APC SmartUPS 5000s. Two of them are AP9617 and one is AP9619. I have a RS-232 connections from my monitor host to all three. All three report status and give information. One of the two AP9617 - ups3-1 - does not shut down when FSD is sent. It did when I first set this system up a year or two ago but it's stopped doing so since then. Resetting the management interface does not

Re: "Does it work well with NUT?" Assuming it is the SU5000RT4UHV, the similar units I've tried seemed to work fine. For reference, the SU5000RT4UHV should be a 4004 USB protocol. ________________________________ From: David Zomaya Sent: Wednesday, March 25, 2020 5:21 PM To: Lee Damon; nut-upsuser Mailing List Subject: Re: [EXTERNAL] [Nut-upsuser] thoughts on tripp lite Smart

I'm obviously biased but I like Tripp Lite stuff. I try to pitch in and help with Network UPS Tools issues related to Tripp Lite when I can too (albeit the developers and users on this list are usually more helpful than me). Just to confirm, it sounds like you are looking at the SU5000RT4UHV, correct?

I have a couple EMC relabled ACBEL/Polytech UPSs which I'm unable to find anything about. What I do know is that ACBEL/Polytech is CoolerMaster, however, they don't make UPSs that I know of. These UPSs were used as part of an EMC Clarion array. Does anyone know anything about these? Thanks, Mark. -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Thu, 2 Mar 2017, Garrett Michael Hayes wrote: > I would like to set up a Linux host as a central monitoring system for > UPSs throughout our network.? I?d like that system to be able to see the > various UPSs basically in one of two ways: > > 1)????? Tapping into a native network interface on the target UPS (such as some larger APC and Tripp-Lite UPSs we have) > 2)?????

Dear Daniele, thanks a lot for your support, i have some things that are not so clear for me: - I can send you the whole sources for our UPSs, do you need only Headers and C files or also other files (i suppose Driver list)? - Seen that we had some problems with the Blazer driver (the battery voltage calculation were not correct for our UPSs) we copied it and modified a bit while changing the