similar to: Bug#441342: Nut can kill power to UPSs that never went on battery

>> Over the last couple months, we have had a couple incidents (luckily a= ll >> on weekends) where all 15 UPSs will mysteriously shut off, and we had = to >> manually power them back up. To top it off, there was nothing in syslo= g >> about any UPS going onto battery power and staying there - just a coup= le >> curious low-battery warnings from one of the UPSs. You

(Viral: I'm forwarding your message to the FLAC mailing list) ----- Forwarded message from Viral <viral@debian.org> ----- Date: Fri, 3 Aug 2001 00:00:07 +0530 From: Viral <viral@debian.org> To: mdz@debian.org Subject: [rcw@debian.org: Re: Patches to abcde to include support for flac format.] Hi, I patched abcde so that it can encode flac files. The patch will not be included in

I'm having a problem that I hope those with greater experience might have some ideas on. I live up in the mountains where the power is ill-conditioned. Transients which would cause a computer to reboot occur on a daily basis. Power failures are frequent and can last anywhere from five minutes to five days. I have all my computers on UPSs so the first two problems are solved. I have a

On Mar 25, 2020, at 6:09 PM, Lee Damon <nomad at ee.washington.edu> wrote: > > I have no experience with Tripp Lite UPSs and the reviews I've found online are scant and fairly mixed so I thought I'd ask here... It's always hard to get a good read on whether a particular UPS brand is problematic, or if there is more noise on the lists because people are trying to make

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

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

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

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 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 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

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?

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

We're looking at replacing some old APC SmartUPS 5000s with something that has USB so NUT can more easily talk with it (and yes, I've tried USB-RS232 adapters and every one I tried started kicking out errors within a few hours). One of the bids we have is for a "Tripp Lite UPS Smart Online 5000VA 4500W Rackmount 5kVA 200V/240V" as the potential replacement unit. I have no

Larry, On 2017-06-25 23:26, Larry Fahnoe wrote: > Hi Phil, > > I don't have an answer to your question about the lack of LAN ports, I think it is weird - with everything else being connected to LANs like fridges etc . . why not UPSs? > but can offer my experience with NUT for a home server environment. > I've tended to prefer the Tripp-Lite UPS systems, mainly

Can anyone tell me whether 4 has better native support for UPSs with a USB monitoring interface? Thanks Nigel

Don't choose mini-box OpenUPS. No instant commands. No reporting of power fail. No replies to emails to support. Otherwise perfect! I have mine working with support from Charles but not ideal. Regards, Philip. Sent from my iPhone > On 9 Apr 2015, at 05:16, Ben Kamen <bkamen at benjammin.net> wrote: > > I'm looking to buy some new UPSs and am thinking of parting ways

On 06/25/2017 05:52 PM, Philip Rhoades wrote: > Larry, > > > On 2017-06-25 23:26, Larry Fahnoe wrote: >> Hi Phil, >> >> I don't have an answer to your question about the lack of LAN ports, > > > I think it is weird - with everything else being connected to LANs > like fridges etc . . why not UPSs? because probably an UPS port ( or even RS232-to-USB

Ah! So I can detect the source UPS in the upssched.conf and pass it as a distinct event to the shell script. That sounds like an excellent approach. Thanks! GMH From: O'Shaughnessy, Mike [mailto:Mike.OShaughnessy at gd-ms.com] Sent: Tuesday, October 31, 2017 12:46 PM To: Garrett Michael Hayes <Garrett at VerbalImaging.com>; nut-upsuser at lists.alioth.debian.org Subject: RE: Email

Hi Phil, I don't have an answer to your question about the lack of LAN ports, but can offer my experience with NUT for a home server environment. I've tended to prefer the Tripp-Lite UPS systems, mainly because I originally felt they did a good job of power filtering. I use a NUT master running on a Raspberry Pi 3 which is easy to maintain and gets current updates via its Debian roots.