On Feb 8, 2013, at 12:26 PM, m.roth@xxxxxxxxx wrote:
> Toby Bluhm wrote:
>> On 2/8/2013 1:23 PM, m.roth@xxxxxxxxx wrote:
>>> Craig White wrote:
>>>> service apcupsd status
>>>>
>>>> (or cat /var/log/apcupsd.events)
>>>>
>>> Already posted the latter; the former, hey, neat results, excerpted
>>> here:
>>> MODEL : Smart-UPS 3000 RM
>>> STATUS : SHUTTING DOWN
>>> LINEV : 118.0 Volts
>>> LOADPCT : 55.9 Percent Load Capacity
>>> BCHARGE : 100.0 Percent
>>> TIMELEFT : 10.0 Minutes
>>> <...>
>>> TONBATT : 0 seconds
>>> CUMONBATT: 27 seconds
>>>
>>
>> You can specify in the conf file that shutdown occurs when it hits X
>> minutes of runtime left - "MINUTES" should be the parameter. You're at
>> 10.0 minutes left & if you have it set to something 10.0 or greater,
>> it's probably gonna want to shutdown immediately at any AC power loss.
>
> I'm afraid you've missed the whole beginning of this thread - I suggest
> you read it. I know what you were saying; it's the response of apcupsd to
> a power blip this morning that's the issue: as much as these servers draw,
> there's no way that the UPS is out of power in 3 seconds.
----
You can configure the anticipation of how many minutes are necessary for powering down because it's definitely not instantaneous and in fact, powering down is likely to cause an increase of power consumption.
That said, 55% load capacity is very high and obviously fits into the calculation that APCUPSD is making when it instructs connected server(s) to shut down.
Craig
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
