[Nut-upsdev] Constant "on battery" and "on line power" status changes (again)

Patrick cso at satcharters.com
Thu May 19 12:12:07 UTC 2011


Hello all,

I am in the process of building a newer server, and trying to get the 
Debian NUT package running correctly. I have run into a problem that I 
ran into three years ago (that was graciously patched by Arjen de 
Korte), but I am not sure if it is caused by the same issue. The 
original thread was:
http://lists.alioth.debian.org/pipermail/nut-upsdev/2007-December/002751.html

This is the same UPS, but a different server. In fact the server I had 
originally configured back then was replaced about 18 months ago with a 
newer piece of equipment, and it is running Debian Lenny. I installed 
that Debian package (NUT 2.2.2 I believe) with no issues. The OS on this 
new server is Debian Squeeze (upgraded from Lenny in early March), with 
NUT 2.4.3, just installed.

Since the usbhid-ups library functioned on the Lenny box, I copied it to 
the Squeeze box and all appears fine. I am attaching the output of 
/lib/nut/usbhid-ups -DDD -a su1500 using each version on the new server.

I will be happy to provide any additional information if necessary, with 
the only caveat being I am not on-site, so I have to rely on someone 
else to do anything physically. That could delay my response. In the 
meantime, is there a problem with using the older library on the newer 
system? It will be at least a week before it is ready to go live, so I 
do not need NUT working right now. I just want to know if I am opening 
myself up to any unforeseen issues if I continue to test the system 
using the older library.

Regards,
Patrick

-------------- next part --------------
A non-text attachment was scrubbed...
Name: usbhid-ups.outs.tar.gz
Type: application/gzip
Size: 11400 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20110519/3db46013/attachment.bin>


More information about the Nut-upsdev mailing list