[Nut-upsdev] Best Ferrups reporting uptime in minutes, not seconds

[Chris Adams]

Once upon a time, Charles Lepple <clepple at gmail.com> said:
> On Fri, Jun 13, 2008 at 3:11 PM, Chris Adams <cmadams at hiwaay.net> wrote:
> > I had a power hiccup yesterday and a server connected to a Best Ferrups
> > 18KVA shutdown.  The problem is that the UPS is reporting remaining
> > runtime in minutes but nut treats it as seconds (so nut thought it only
> > had 46 seconds left).
> 
> The patch looks good at first glance, but by default, NUT should not
> use the runtime estimate to initiate a shutdown.
> 
> Are you using upssched? Any special parameters to the driver?
> 
> Otherwise, NUT will shut down when the UPS signals LB (low battery),
> which is a unit-less boolean value.

No, I'm not using upssched.  I wasn't sure exactly how nut decided when
to shut down (maybe a gap in the documentation or a gap in my reading).
Here's what I got in my log:

Jun 12 17:05:10 spider upsmon[27383]: UPS best at localhost on battery
Jun 12 17:05:10 spider upsmon[27383]: UPS best at localhost battery is low
Jun 12 17:05:10 spider upsd[27379]: Client monuser at 127.0.0.1 set FSD on UPS [best]
Jun 12 17:05:10 spider upsmon[27383]: Executing automatic power-fail shutdown
Jun 12 17:05:10 spider upsmon[27383]: Auto logout and shutdown proceeding
Jun 12 17:05:20 spider upsd[27379]: Signal 15: exiting

The UPS does have old batteries (we're getting them replaced), but it
still is reporting 46 minutes of runtime, so I didn't expect that it
would have instantly reported low battery.

-- 
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.