I have a FreeNS box attached to a APC Smart UPS. I've configured the UPS service, and it all works as expected.
I have
For the ups.conf
Which means (and functions correctly) that FreeNAS turns itself (and a pfSense box) off when either the charge is below 20% or it reports less than 20 mins runtime.
This all fine, and both the pfSense box and FreeNAS do indeed turn off when either of these conditions are met.
I have two questions: 1 - the time it takes FreeNAS to shutdown is outrageous. I tested this morning and it took just in excess of 15 mins. This is from the point when the UPS goes onto Low Battery, FreeNAS identifies and issues an automatic shutdown notice. Within a minute the pfSense box has completed its shutdown.
I lost access to jails within a minute or so, I had access to the WebGUI for probably around 5 mins, and then a further 10 minutes for the shutdown procedure to finish and then power off the UPS. Whilst I had no access to FreeNAS for those 10 minutes the hdd light was blinking, and all the systems fans were still spinning etc etc. Now it did shutdown (and just before it does the UPS says shutdown initiated by USB, counts down from 180 seconds and powers off after the shutdown has completed dropping the rest of the load) Therefore its functioned perfectly, but I am a little concerned with why it takes FreeNAS 15 mins to shutdown. when via the webGUI shutdown is a lot quicker?
Second question - if the power has been out long enough to discharge the batterys to the point where everything turns off - I don't want the UPS to boot until I have more charge (and therefore runtime) than the low battery condition. I.e wait until its at 30% charge before turning everything back on. I tried to use
override.battery.charge.restart = 30
But as soon as I gave the UPS power, everything turned on, the pfSense and FreeNAS both received power and started booting up. The UPS only had 6% charge at this point, and if there was to be another power cut, wouldn't be able to shutdown in time. Any advice on making this work?
I have
Code:
ignorelb override.battery.runtime.low = 1200 override.battery.charge.low = 20
For the ups.conf
Which means (and functions correctly) that FreeNAS turns itself (and a pfSense box) off when either the charge is below 20% or it reports less than 20 mins runtime.
This all fine, and both the pfSense box and FreeNAS do indeed turn off when either of these conditions are met.
I have two questions: 1 - the time it takes FreeNAS to shutdown is outrageous. I tested this morning and it took just in excess of 15 mins. This is from the point when the UPS goes onto Low Battery, FreeNAS identifies and issues an automatic shutdown notice. Within a minute the pfSense box has completed its shutdown.
I lost access to jails within a minute or so, I had access to the WebGUI for probably around 5 mins, and then a further 10 minutes for the shutdown procedure to finish and then power off the UPS. Whilst I had no access to FreeNAS for those 10 minutes the hdd light was blinking, and all the systems fans were still spinning etc etc. Now it did shutdown (and just before it does the UPS says shutdown initiated by USB, counts down from 180 seconds and powers off after the shutdown has completed dropping the rest of the load) Therefore its functioned perfectly, but I am a little concerned with why it takes FreeNAS 15 mins to shutdown. when via the webGUI shutdown is a lot quicker?
Second question - if the power has been out long enough to discharge the batterys to the point where everything turns off - I don't want the UPS to boot until I have more charge (and therefore runtime) than the low battery condition. I.e wait until its at 30% charge before turning everything back on. I tried to use
override.battery.charge.restart = 30
But as soon as I gave the UPS power, everything turned on, the pfSense and FreeNAS both received power and started booting up. The UPS only had 6% charge at this point, and if there was to be another power cut, wouldn't be able to shutdown in time. Any advice on making this work?