[Nut-upsuser] Premature end of script headers: upsimage.cgi
Arjen de Korte
nut+users at de-korte.org
Fri Jul 10 19:50:41 UTC 2009
Citeren benjamin thielsen <bthielsen op safarivideonetworks.com>:
> aha - thank you, that seems to have done the trick. i suppose that
> dividing by zero would also explain the floating point error.
Yes. That tipped me off that there might be something wrong in the
values reported by the UPS.
> regarding the values you've specified above for the override and
> defaults - how are those determined?
Your UPS reports a battery voltage of 55 V. Assuming this is correct,
this would be right what you'd expect for a 48 V nominal lead acid
battery (24 cells) that is fully charged (depending on the vendor,
2.27 - 2.30 V per cell). The minimum cell voltage is where the UPS
shuts down to protect the batteries for deep discharge (1.60 - 1.80 V
per cell). If 'battery.voltage.nominal' is provided, both will be
calculated automatically if not reported by the driver, but I'd rather
make this explicit in the configuration.
>> What remains is the question if this is a problem in the snmp-ups
>> driver or the UPS. I honestly don't know.
> well, if the output of snmpwalk is any indication, it appears that
> snmp-ups is accurately passing on values:
>
> snmpwalk -v1 -c xxxxxxxxxx -m '/usr/share/snmp/mibs/powernet391.mib'
> ups4 .1.3.6.1.4.1 | grep -i nominal
> PowerNet-MIB::upsAdvBatteryNominalVoltage.0 = INTEGER: 0
That sucks, but this also explains the other weird values that are
reported. I noticed quite a couple of firmware updates for this UPS on
the APC site. It might be worthwhile to check if this fixes things.
Best regards, Arjen
--
Please keep list traffic on the list
More information about the Nut-upsuser
mailing list