similar to: Question about NUT config

Good morning everyone, we're currently in the process of redesigning our UPS signalling scheme, and decided to have a closer look at NUT. This is our setup: - a (really) big UPS (Piller, with a web/SNMP interface) - several computer rooms with equipment of different importance, managed by several people not sharing ssh keys etc., with an unknown number of machines - IPMI signalling to

01.12.2014, 06:18, "Charles Lepple" <clepple at gmail.com>: > On Nov 29, 2014, at 7:32 AM, Victor Porton <porton at narod.ru> wrote: >> ?On Debian Linux jessie: >> >> ?After buying an UPS and installation of nut-server and nut-client at my PC and configuring the ports and the protocol, do I need to adjust time and/or percentage parameters, to be sure my

On Dec 1, 2014, at 4:11 AM, Victor Porton <porton at narod.ru> wrote: > battery.voltage: 13.70 > battery.voltage.high: 13.00 > battery.voltage.low: 10.40 These are the voltage thresholds for the UPS, so theoretically the UPS will send the LB signal when the battery voltage goes lower than 10.40 Volts. Also, if battery.charge works, you can use "ignorelb" if you want to

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>

Now I have this in /etc/nut/upsmon.conf (my QNAP NAS wants admin and 123456 or not working) RUN_AS_USER root MONITOR qnapups at localhost 1 admin 123456 master MONITOR qnapups at 192.168.222.252 3493 admin 123456 slave MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC

On 2/20/2014 6:55 AM, Charles Lepple wrote: > On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote: > >> Worse, however, is if there's a power failure right near the end of >> the 2-days-off cycle. That happened to me last week - it was a >> short duration 15 second loss - and the upscode2 driver decided it >> needed to issue a forced shutdown. >> >>

Roger, The topology is: UPS TOPAPC, Data link to master, Power supply to master, slave1 and slave2 UPS MIDAPC, Data link to master, Power supply to master, slave1 and slave2 UPS BOTAPC, Data link to master, Power supply to master, slave1 and slave2 Shutdown plan: When wall power fails for any of the three UPS units, they continue powering the master and the two slaves. When two of the UPS

On Mar 17, 2015, at 11:46 AM, Philip Taylor <philip at kelsotowers.co.uk> wrote: > Charles, > > Did you get chance to look at the data I sent you, please? > > I?ve done some more work myself and the conclusion I?ve reached is that if the minibus OpenUPS doesn?t support instant commands, then sending ?upsdrvctl shutdown? won?t ever work, as it would need to send instant

MASTER SYSTEM nut.conf MODE=netserver ups.conf [TOPAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309002707" desc = "TOPAPC" [MIDAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309001233" desc = "MIDAPC" [BOTAPC] driver = usbhid-ups port = auto

On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote: > I'm going to guess that since your test runtime of 305 is very close to > the low limit of 300, that's the warning. Not yet a fail, but very, very > close. > I tried setting override.battery.runtime.low = 60 in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to report only

On Thursday 29 October 2020 22:12:00 Charles Lepple wrote: > On Oct 28, 2020, at 9:56 PM, Gene Heskett <gheskett at shentel.net> wrote: > > Which looks very incomplete to me. OTOH, its not a very big UPS but > > neither is the pi. I have tested that, and it shuts off long before > > it outouts a LB signal. > > Which part looks incomplete, the variables or the

Hi Charles, I don't think "ignorelb" will work in my case because that is set on the master. I am using the nut package in pfSense as the master and I want pfSense to shutdown on LOWBATT as designed. I tried using upssched.conf with timers on the netclients but that's not appropriate because ONBATT by itself doesn't tell you how much capacity remains in the UPS. You still

I?m a new user of NUT and the OpenUPS - in the past I?ve used APC hardware and apcupsd on Centos 6. I?ve built NUT 2.7.2 from source but used the OpenUPS HID driver v0.4 that?s in github. I?m using firmware version 1.5 on the openups which is the latest published version; I?ve also tried 1.7 which Mini-box sent to me but reverted to the published version. Their support seems a bit slow! I?ve got

Charles, to your specific points : > The other HID drivers seem to trigger shutdown by writing to the various timers (e.g. UPS.PowerSummary.DelayBeforeReboot). Your firmware seems to have UPS.PowerSummary.PresentStatus.ShutdownRequested, which according to the HID PDC spec, is read/write. I wonder if the firmware responds to this? So are you suggesting if I modify openups-hid.c to include

Hmm. Is there maybe something there already that will do this? Maybe kind of back-handed. In drivers/dstate.c, I see: In status_init(), if ?driver.flag.ignorelb? is set in the driver state, the ?ignorelb? flag is set. In status_set(), if ignorelb is set, and the status being set (presumably from the UPS) is LB, it?s ignored. In other words, LB reported by the UPS is ignored. In status_commit(),

> > battery.charge: 3 > battery.charge.low: 10 > battery.charge.warning: 30 > battery.runtime: 93 > battery.temperature: 32.9 > battery.type: PbAC > battery.voltage: 46.4 > battery.voltage.nominal: 48.0 Is it possible that battery.charge is really 30% rather than 3%? The 3016 protocol models have issues with scaling on some of the voltages and frequencies. You can see

First time poster but I've been using NUT periodically for a long time. I was looking for a way to initiate a shutdown on servers when UPS battery runtime drops to a certain threshold. I never found a published way after much searching. I have upsmon running mostly for the email notifications and removed the shutdowncmd command to keep it from running. Rather I'm using a cron job

Hi everybody! It has been a journey but I almost manage to make my UPS properly communicate. This is the config: UPS Mecer/Mustek 2000 VA connected via USB with blazer_usb driver. MASTER Raspberry PI-1 SLAVE Raspberry PI-2 SLAVE iMac OSX 10.10.3 I can get access to the UPS from any of the three devices successfully. Problems: 1. When I launch /usr/local/ups/sbin/upsmon -c fed for testing I see

*Platform: Proxmox VE 8.1.4NUT version: Network UPS Tools upsstats 2.8.0* I configured Proxmox and I can pull up the UPS stats. Typing in `*upsrw -l cyberpower at localhost*` I get the following: *[battery.charge.low]Remaining battery level when UPS switches to LB (percent)Type: STRINGMaximum length: 10Value: 10[battery.runtime.low]Remaining battery runtime

On Aug 15, 2017, at 5:24 AM, Song Teck <songteck at gmail.com> wrote: > > Hi Charles, > > Have managed to make some progress after a fashion. Got the unit to work on the jessie version of NUT (2.7.2). upsc does output the unit parameters, along with the mis-scaled voltage readings described at http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying to get the