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 need to invoke a script to check. The netclients are what I need shutdown in a particular order. I'm currently using upsc to get ups.status = "OB" and battery.runtime < n (seconds). My UPS has about 16 minutes capacity when fully charged and a 19% load with all hardware on. 8 minutes remaining (battery.runtime <= 480) shut down VMs and hypervisors (clients). 5 minutes remaining (battery.runtime <= 300) shut down FreeNAS (client). 2 minutes remaining LOWBATT shut down the master. Even if it's a kludge I guess it gets the job done. I was looking for native support for battery.runtime triggers. Thanks Danny From: "Charles Lepple" <clepple at gmail.com> To: "Danny Siminiuk" <daniel at siminiuk.com> Cc: "nut-upsuser" <nut-upsuser at alioth-lists.debian.net> Sent: Tuesday, December 4, 2018 12:07:48 PM Subject: Re: [Nut-upsuser] battery.runtime On Dec 4, 2018, at 10:12 AM, Danny Siminiuk < [ mailto:daniel at siminiuk.com | daniel at siminiuk.com ] > wrote: 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. Does “ignorelb” do what you need? See the description here: [ https://networkupstools.org/docs/man/ups.conf.html | https://networkupstools.org/docs/man/ups.conf.html ] BQ_BEGIN BQ_END BQ_BEGIN _______________________________________________ Nut-upsuser mailing list [ mailto:Nut-upsuser at alioth-lists.debian.net | Nut-upsuser at alioth-lists.debian.net ] [ https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser | https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser ] BQ_END -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20181204/7d88be86/attachment.html>
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 set up the "clone" driver, and set "ignorelb" there. pfSense, as the master, would connect to the real driver without ignorelb. Each of the server groups could have its own "clone" driver pointed at the real driver with a different override.battery.runtime.low parameter.
That's an idea Charlie. The APC UPS I am using has an AP9630 card in it and pfSense is grabbing the snmp. I could try to use the USB cable on the FreeNAS so both could be masters. ----- Original Message ----- From: "Charles Lepple" <clepple at gmail.com> To: "Danny Siminiuk" <daniel 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 set up the "clone" driver, and set "ignorelb" there. pfSense, as the master, would connect to the real driver without ignorelb. Each of the server groups could have its own "clone" driver pointed at the real driver with a different override.battery.runtime.low parameter.