search for: ignorelb

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(), if ignorelb is set, there?s code to compare battery.charge aga...

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

Hi again, On 5/22/23 18:31, Willcox David via Nut-upsuser wrote: > Hmm. Is there maybe something there already that will do this? Maybe > kind of back-handed. > > In drivers/dstate.c, I see: > > 1. In status_init(), if ?driver.flag.ignorelb? is set in the driver > state, the ?ignorelb? flag is set. > 2. 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. > 3. In status_commit(), if ignorelb is se...

Hmm, looking at status_commit(), if the UPS actually reported just ?OB", but the ?ignorelb? logic kicked in, wouldn?t status_commit() change it to ?OB LB?? And would clients interpret that correctly? And, assuming status_commit() is called, is the status so saved what?s returned on a future client query? I?m really unsure how all of this works. I don?t suppose there?s some kind of ?ge...

...l at siminiuk.com> Cc: "nut-upsuser" <nut-upsuser at alioth-lists.debian.net> Sent: Tuesday, December 4, 2018 9:38:41 PM Subject: Re: [Nut-upsuser] battery.runtime On Dec 4, 2018, at 1:38 PM, Danny Siminiuk <daniel at siminiuk.com> wrote: > > 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. > Ah, the multiple thresholds weren't clear from your original post. I haven't tried this, but in theory, you could s...

Carsten Aulbert <carsten.aulbert at aei.mpg.de> writes: > Hi all, > > On 5/19/23 15:11, Greg Troxel wrote: >> LB is baked in to nut behavior. So if a UPS doesn't report LB, then >> it makes sense to synthesize it. Synthetic LB is the cleanest fix at >> the earlier processing point. > > I fully agree and thus this ought to be done in/near uspd

On December 2, 2018 7:29:38 PM GMT+02:00, raul <raulvior.bcn at gmail.com> wrote: >I have restored original configuration and enabled the ignorelb flag. I > >didn't point out in the original e-mail that after every poweroff the >battery percentage is reported at 40% instead of 100% and charges >slowly again to 100%. Maybe the UPS sends a LB event and shuts down >immediatly as suggested in the manual. But the UPS powered...

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

...1 ups.vendorid: 09ae ups.watchdog.status: 0 [root at localhost ~]# Broadcast message from nut at localhost.localdomain (Mon May 16 17:16:12 2016): UPS myups at localhost on battery [root at localhost ~]# ========================================================================== I added the "ignorelb" option and changed the "battery.charge.low" to "90" to try to get it to reboot fast. No luck. Got it down to "70" without it actually powering off. Perhaps I have something else misconfigured... I'm attaching a tar.gz of my ups directory. Can you take a...

On Dec 4, 2018, at 1:38 PM, Danny Siminiuk <daniel at siminiuk.com> wrote: > > 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. > Ah, the multiple thresholds weren't clear from your original post. I haven't tried this, but in theory, you could s...

...the UPS needs to be powered off during a power failure when low battery is reached." That is correct. You can also configure NUT drivers to ignore the UPS's LB flag and synthesize it from battery.charge or battery.runtime: http://networkupstools.org/docs/man/ups.conf.html (search for 'ignorelb') -- Charles Lepple clepple at gmail

...verride.device.serial = "G008E39401" override.ups.serial = "G008E39401" override.battery.mfr.date = 09/28/14 pollonly vendorid = 0463 productid = ffff desc = "Eaton 3S700DIN" UPS stops after 4 minutes. LB flag is not set. Battery.charge: 91 b) 2nd attempt: (based on ignorelb + upslog) [3s] driver = usbhid-ups port = auto pollinterval = 5 ignorelb override.battery.charge.low = 30 override.battery.runtime.low = -1 override.battery.voltage.nominal = 12 override.battery.mfr.date = 09/28/14 override.outlet.1.desc = "BATTERY" override.outlet.2.desc = "FILTER&q...

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

...de this specific command as an instant command, it may respond? I could give it a try if you confirm that?s what you mean. > Out of curiosity, which notifications? In the openups_drv_start_onbatt log, the PresentStatus values look the same as the online log. Or do you mean you got that from the ignorelb configuration? The notifications are : ONLINE ONBATT FSD COMMOK COMMBAD SHUTDOWN (following FSD from command line). I believe it notified LOWBATT too when I used ignoreLB and over-rode battery.charge.low. But I?ve never seen the OpenUPS notify LB via USB. If I use the scenario I proposed I would m...

...PS isn't publishing that time threshold, only the current remaining time estimate. (Per the previous email, the battery.runtime.low value in upsc seems to be coming from the override.battery.runtime.low setting in ups.conf.) I still think the combination of override.battery.runtime.low and the ignorelb setting should get you the shutdown trigger you are looking for. You might also need to set pollfreq to a lower value than its default of 30 seconds, since the RemainingTimeLimit value is not requested during the Quick update every two seconds. On the other hand, the whole reason for the two separ...

...rride.ups.serial = "G008E39401" > override.battery.mfr.date = 09/28/14 > pollonly > vendorid = 0463 > productid = ffff > desc = "Eaton 3S700DIN" > > > UPS stops after 4 minutes. LB flag is not set. Battery.charge: 91 > > b) 2nd attempt: (based on ignorelb + upslog) > [3s] > driver = usbhid-ups > port = auto > pollinterval = 5 > ignorelb > override.battery.charge.low = 30 > override.battery.runtime.low = -1 > override.battery.voltage.nominal = 12 > override.battery.mfr.date = 09/28/14 > override.outlet.1.desc = "BAT...

...clunk and the ups outlets are back on. I don't understand why the UPS is not staying off when issuing the command /etc/killpower or via sudo upsdrvctl shutdown. ups.conf: [Tripp_Lite] driver = usbhid-ups port = auto pollinterval = 10 desc = "Tripp-Lite SMART1500LCD" vendorid = 09ae ignorelb override.battery.charge.low = 10 ---------------------------------------------------------------------------- nut.conf MODE=standalone ---------------------------------------------------------------------------- upsd.users [upsmon] password = xxxxx actions = SET instcmds = ALL upsmon master -...

...override.ups.serial = "G008E39401" > override.battery.mfr.date = 09/28/14 > pollonly > vendorid = 0463 > productid = ffff > desc = "Eaton 3S700DIN" > > > UPS stops after 4 minutes. LB flag is not set. Battery.charge: 91 > > b) 2nd attempt: (based on ignorelb + upslog) > [3s] > driver = usbhid-ups > port = auto > pollinterval = 5 > ignorelb > override.battery.charge.low = 30 > override.battery.runtime.low = -1 > override.battery.voltage.nominal = 12 > override.battery.mfr.date = 09/28/14 > override.outlet.1.desc = "BAT...

This is 2nd version of the earlier patch featuring a few new features and fixes to the apcsmart driver, following the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level -

...soon (judging by the battery charge level monitored with upsc). The load is about 300W, less than half nominal load, so despite the batteries not being brand new, it ought to keep going for maybe 5 minutes. Instead it starts the shut down after about 20 seconds. This sounds like a case for "ignorelb", I was just wondering if this is well known for this UPS? -- Per Jessen, Z?rich (23.4?C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.