hi there, I ran portmon. Read on...
I'm running nut 2.2.2-6.5 under Debian Lenny 5.05 on a Dell T110
PowerEdge Server hooked to a Cyberpower 1500 AVR LCD. All new hardware
purchased in the last 3 months. I tried to attach via usb at first, but
was getting stale data errors in syslog
My previous post was a follow-up to this discussion in February:
http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-February/005924.html
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
I applied the aforementioned patch to 2.4.3 and recompiled. Since the
patch only affects newmge-shut and usbhid-ups I just copied the latter
into /lib/nut/ This works, insomuchas all the nut programs start up and
run. However, there are 3 remaining problems:
1) syslog errors every 20+
It turns out Cyberpower's own Linux software can't talk to the cp1500avr
over serial cable either.
So the nut serial driver probably isn't the problem.
I've already shown the UPS and cable are OK by talking to Windows.
It seems unlikely that both Thomas and I and all the other posts you can
1) syslog errors every 20+ minutes or so like : Aug 7 10:21:03 ben
usbhid-ups[3321]: libusb_get_string: error sending control message:
Broken pipe
Not a cause of concern. It is a way of telling that the UPS is
currently not able to handle a command. Most likely this is due to the
UPS
Thanks - that brought me more progress than I've seen all day :)
Changing to the following on the server :
upsd.conf:
LISTEN 0.0.0.0
with no other changes from what I posted on the previous page got both
the server and slave nuts starting up ok.
For the record ifconfig on the server
Changing to the following on the server :
upsd.conf:
LISTEN 127.0.0.1
LISTEN 192.168.1.102
also works :)
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
7 matches
Mail list logo
