similar to: Runtime testing

On 2019-12-16 05:34, Roger Price wrote: > On Sun, 15 Dec 2019, Phil Stracchino wrote: > >> I switched a while back to a Cyberpower PR3000LCDRTXL2U UPS with an >> external battery chassis. We've lost power twice since I installed it, >> and both times, the UPS has killed power to everything while still >> indicating 80% capacity before NUT has even initiated

On 3/21/24 14:00, Greg Oliver via Nut-upsuser wrote: > All I can say is definitely replace the batteries if you are going to > keep using it.? The CyberPower(s) I have had in the past all have the > battery check that cannot be turned off and when the batteries are > actually "dead" the unit will kill the load to everything every time it > runs the check.? Just FYI.

Hello Is it possible to limit the frequency of specific notifications? In 2.7.4 it seems to be possible only for REPLBATT via RBWARNTIME, but that's it. My specific problem is that the UPS got disconnected and before I got hold of the server to turn the upsmon off my mailbox got flooded with hundreds of messages. It probably doesn't make sense for all notification types, but for

On Thu, Mar 21, 2024 at 12:23?PM Phil Stracchino via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote: > I have a CyberPower PR3000LCDRTXL2U with a BP48V75ART2U expansion > chassis, which I am monitoring using NUT 2.8.0 (on Gentoo Linux). TThe > UPS appears to be telling me that the batteries need replacement due to > age. CyberPower support has confirmed that for

SO, my full load on my core UPS is two Dell R610s, one Sun X4540, one HP DL360p gen8, two six-core Thuban-II workstations plua their monitors, and the network stack and KVM. The APC SU3000RM (3KVA) that blew up last week considered this to be just short of 60% load. The new Cyberpower PR3000 (also 3KVA), wqhich operates at a 90% power factor, considers this same load to be 43% load. I wasn't

On 2019-12-17 06:18, Roger Price wrote: > > I definitely need to check that the vile daemon is present and running. > > In upsmon.conf there are no NOTIFYFLAG declarations, especially for events > ONBATT and LOWBATT. When ONBATT and LOWBATT occur nothing will happen. There > are no NOTIFYMSG declarations and in particular no messages for the ONBATT and > LOWBATT events.

I have a CyberPower PR3000LCDRTXL2U with a BP48V75ART2U expansion chassis, which I am monitoring using NUT 2.8.0 (on Gentoo Linux). TThe UPS appears to be telling me that the batteries need replacement due to age. CyberPower support has confirmed that for me and told me how i should be able to mute the alarm from the front panel until I can replace the batteries, but it doesn't appear

I'm looking at switching from an APC UPS to a different brand after having had my third SU3000RM in a row blow up power transistors. I'm looking at the Cyperpower PR3000LCDRTXL2U. I see the PR3000E and the PR6000LCDRTXL5U listed as supported, but not the PR3000LCDRTXL2U. Howeverit seems likely that if the PR6000LCDRTXL5U is supported, the PR3000LCDRTXL2U ought to work as well. I've

I switched a while back to a Cyberpower PR3000LCDRTXL2U UPS with an external battery chassis. We've lost power twice since I installed it, and both times, the UPS has killed power to everything while still indicating 80% capacity before NUT has even initiated shutdown on anything. Here's what upsc reports on it right now: battery.charge: 100 battery.charge.low: 35

Hello, I'm quite new to NUT, currently setting it up on a few machines in my home lab because I switched from an APC UPS to a CyberPower unit. This is running in a home lab, and I'm trying to implement some apparently unusual logic around load-shedding. I'm strongly considering writing my own custom script to replace upsmon in order to achieve the desired result. I see a lot of

Well, for a bit of devil's advocate - if the battery swelled, it might hace leaked or fumed, contaminating the device and contacts. The safe approach (for their liability, and for end-users' fire hazard really) is to not claim the device is safe to use anymore. Jim On Tue, Apr 2, 2024, 07:11 Ben <bkamen at benjammin.net> wrote: > On 4/1/24 7:37 PM, Phil Stracchino via

Bonjour je n?arrive pas ? configurer convenablement NUT pour qu?il m?adresse des SMS en cas de coupure de courant. C?est important pour moi car dans ma maison les coupures sont tr?s fr?quentes. Voici ma configuration : ****************************************************************** 1/ dans /etc/nut/upsmon.conf MONITOR eaton at localhost 1 admin motdepasse master MINSUPPLIES 1 SHUTDOWNCMD

So, I just rebuilt the battery packs in my PR3000LCDRTXL2U and its expansion unit. You don't want to KNOW. If the internal batteries have overheated and bulged, you CANNOT remove the battery pack intact even by partially disassembling the UPS, you have to pry the batteries out via the top of the chassis one by one. It's not pretty. Three and a half hours of work including

Hi, I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

On Fri, 9 Jun 2017, Robbie van der Walle wrote: > ... and also still open is the notification on the Mac. If notify-send is available on the Mac, then perhaps this will work: In upsmon.conf on the Mac you need NOTIFYCMD /usr/sbin/upssched (or wherever this goes on a Mac) NOTIFYFLAG ONBATT SYSLOG+EXEC In upssched.conf you need CMDSCRIPT /usr/sbin/upssched-cmd (or wherever this

On 04/03/2017 07:03 PM, Gene Heskett wrote: > > But it does that because you have tried to get 12 years out of a gell > cell battery that is doing really really well if you get 4 years out of > it. I am not saying you should do that _now_, without first replacing > that thoroughly boiled dry battery, but as something you should set it > up to do once you have a serviceable

On Jan 21, 2014, at 3:16 AM, Rafa? Oleszek wrote: > I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines

Hi! Some systems I have take some time to shut down, so I would like them to shut down if the UPS have been on battery for 2 minutes. Internet has told me that SHUTDOWNCMD ?/sbin/shutdown -h +0? in /etc/nut/upsmon.conf will execute when the UPS is both OB (on battery) and LB (Low battery). Like in wiki.ipfire.org - Detailed NUT Configuration<https://wiki.ipfire.org/addons/nut/detailed>

On Thu, 8 Jun 2017, Robbie van der Walle wrote: > After the first test and the NAS is restarted I had to change the > setting battery.charge.low again to 80? Does the NAS DSM reset battery.charge.low to 10 or is it internal to the UPS? You will have to experiment by disconnecting the UPS control lead from the NAS and connecting it (if possible) to the Mac. After setting to 80 and a

Hi, I'm attempting to use the UPS network tools. I'm sure I got the configurations worked out as I get notified when the ups goes on battery and back online. I am having problems with upssched. I have the following in my upssched.conf: CMDSCRIPT /usr/local/ups/sbin/upssched-cmd AT ONBATT * EXECUTE onbatt The problem I have is that is seems like the script in CMDSCRIPT never gets