<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello,</p>
<p>CONFIGURATION:<br>
</p>
<p>I am using a Powerware PW9120 3000i, on a network configuration
with a server and a couple of slaves. <br>
</p>
<p>The nut-server OS is <i>Debian 12 (6.1.0-37-amd64)</i>. Nut was
installed from the Debian repo with version <i>2.8.0-7 amd64</i>,
and client has the same version.</p>
<p>UPS is connected with a standard RS232 serial connection, and
works with all standard commands and functionality.</p>
<p>Command "<i>upscmd -l upsname</i>" provides the following, where
I have successfully used <i>test.battery.start</i> and <i>test.system.start</i>:</p>
<p>beeper.disable - Disable the UPS beeper<br>
beeper.enable - Enable the UPS beeper<br>
beeper.mute - Temporarily mute the UPS beeper<br>
load.on - Turn on the load immediately<br>
outlet.1.load.off - Turn off the load on outlet 1 immediately<br>
outlet.1.load.on - Turn on the load on outlet 1 immediately<br>
outlet.1.shutdown.return - Turn off the outlet 1 and return when
power is back<br>
outlet.2.load.off - Turn off the load on outlet 2 immediately<br>
outlet.2.load.on - Turn on the load on outlet 2 immediately<br>
outlet.2.shutdown.return - Turn off the outlet 2 and return when
power is back<br>
shutdown.return - Turn off the load and return when power is back<br>
shutdown.stayoff - Turn off the load and remain off<br>
test.battery.start - Start a battery test<br>
test.system.start - Start a system test<br>
</p>
<p>ISSUE:</p>
<p>Every couple of years when I have to replace batteries in the
UPS, I get an issue with not being able to clear the REPLBATT
alert. That is not until I reboot the server running NUT-SERVER.
This might seem as not a big deal, but becomes a hassle when
batteries haven't quite failed yet and are still good after a ups
battery test.</p>
<p>The UPS itself reports OK after battery replacement or battery
test, and clears alarm on its LCD. But when I poll the UPS data
using "upsc upsname" I still see the RB or REPLBATT and this will
not clear until I reboot the server. So without reboot the alert
will then be generated based on RBWARNTIME in upsmon.conf, which
is as per nut design.<br>
</p>
<p>So without reboot I always get the RB flag with status:</p>
<i>Alert type: REPLBATT</i><br>
<i>............</i><br>
<i>ups.status: OL RB</i><br>
<i>ups.test.result: Done and passed</i><br>
<p>After reboot of server the alert is cleared:</p>
<i>Alert type: COMMOK<br>
............<br>
ups.status: OL<br>
ups.test.result: Done and passed</i><br>
<p>So my question becomes, why is this reboot required and it
doesn't seem to make any sense? I can't understand why the polled
data from a UPS would change after a reboot, while on the UPS LCD
its reporting all OK? I tried restarting NUT-SERVER to see if it
would make any difference. Also, the command test.battery.start
will clear the alarm on the UPS if battery test good.</p>
<p>The only explanation that I have come up with is that the
persistent RB/REPLBATT is latched to this condition and is an
artifact of UPS to NUT handshaking.<br>
</p>
<p>Any feedback would be kindly appreciated, as I have searched and
searched.</p>
<p>Thank you!<br>
</p>
Vyasa<br>
</body>
</html>