I would try the following: plug your computer into a wall outlet, plug
a desk lamp into the UPS. First, start the driver and upsd (but not
upsmon). Monitor the ups variables with upsc. Pull the power, wait 5
minutes or more, see what happens. Are there changes to ups.status?
Does the lamp go off? Normally, the lamp should not go off until the
battery runs out, which should happen some time after ups.status shows
"LB" (low battery). If the lamp goes off before that, there's a
problem.
Then try the same thing again, this time with upsmon running. When the
UPS gets to "LB", then upsmon should start slowly shutting down the
computer. When the computer is in a safe state, the lamp should go off
(the computer will stay on, as it doesn't know it is not plugged into
the UPS).
When I ran the first scenario you outlined, the UPS stayed on for about
5 minutes (slightly less) and then shut off. upsmod was not running,
but upssched was running for a short while (after I removed power) until
I realized it was running and killed it. Here is the info from upsc
during the two relevant points (the second time being just after the UPS
shut off)
While plugged into the wall:
battery.charge: 100.0
battery.runtime: 64:41
driver.name: cpsups
driver.parameter.port: /dev/ttyS2
driver.version: 2.0.4
driver.version.internal: .04
input.frequency: 60
input.voltage: 122
output.voltage: 122
ups.load: 9
ups.mfr: CyberPower
ups.model: CPS1200VA 1.500
ups.power.nominal: 1200
ups.runtime: 70
ups.status: OL
ups.temperature: 28
After power removed for ~5 minutes:
battery.charge: 65.0
battery.runtime: 46:29
driver.name: cpsups
driver.parameter.port: /dev/ttyS2
driver.version: 2.0.4
driver.version.internal: .04
input.frequency: 0
input.voltage: 0
output.voltage: 0
ups.load: 0
ups.mfr: CyberPower
ups.model: CPS1200VA 1.500
ups.power.nominal: 1200
ups.runtime: 70
ups.status: OB
ups.temperature: 42
I didn't try the second scenario as the first one seemed to highlight an
issue of some sort and I didn't think the second scenario would add much
useful info. Was I correct, or should I also run the second scenario?
Rob
Peter Selinger wrote:
That is very odd indeed. Why should the system shut off abruptly? If
the log shows nothing, then it seems that the UPS just turned off the
power.
I recommend testing this while attaching, say, a lamp to the UPS,
instead of a computer. (You can still use your computer to monitor the
UPS, just don't plug it into it!)
-- Peter
Rob wrote:
Upsmon is responsible for monitoring and reacting to power events.
See also the man pages for upsmon(8), upsmon.conf(5), upssched(8), and
upssched.conf(5).
There could be many reasons your Windows machine lasts longer than
your Linux machine on their respective UPSs. Perhaps the battery on
the second one is older, or has lost some of its charge, or is lower
quality... Batteries tend to wear out quite easily, especially if they
are discharged and recharged a few times.
Did you try switching the two machines?
On my system, I only have 1 UPS and I have monitored it in windows and
in Linux. In windows, the same set of systems will properly wait until
the designated time to shutdown (>5 minutes). When I boot into Linux,
my Linux system performs an abrupt poweroff after about 5 minutes. I
notice that UPS has been shutoff, but that the system has not been
shutdown cleanly as the logs do not show a system shutdown and disks
need to be recovered on bootup.
In windows, I monitored the power output and saw that the battery
drained very quickly down to 60%, and then stabilized. I contacted
CyberPower about this and they stated that this is a normal discharge
pattern for SLA batteries. Does NUT possibly detect the power drain
rate and perform an action based upon that? Even if the UPS was sending
a low power indicator, I can't see why NUT wouldn't do a clean shutdown
of the system?
Rob
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
