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
Citeren Rob Donovan hikerman2005-...@yahoo.com:
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
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
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+
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
Citeren Thomas Jensen tom.jen...@digitaltoolbox-inc.com:
server:# /usr/local/ups/bin/powerpanel -DDD -a server
Network UPS Tools - CyberPower text/binary protocol UPS driver 0.25
(2.4.3)
Warning: This is an experimental driver.
Some features may not function correctly.
0.00 debug
On Wed, 24 Feb 2010 12:37:50 +0100, Arjen de Korte
nut+us...@de-korte.org
wrote:
Citeren Thomas Jensen tom.jen...@digitaltoolbox-inc.com:
server:# /usr/local/ups/bin/powerpanel -DDD -a server
Network UPS Tools - CyberPower text/binary protocol UPS driver 0.25
(2.4.3)
Warning: This is an
Citeren Thomas Jensen tom.jen...@digitaltoolbox-inc.com:
Are you referring to dmesg output? If so, does it matter in this regards
whether the machine is a virtualized or not. The UPS is connected to a Xen
Dom0 machine.
Don't do any debugging on virtualized systems. You have no idea
On Wed, 24 Feb 2010 21:00:03 +0100, Arjen de Korte
nut+us...@de-korte.org
wrote:
Citeren Thomas Jensen tom.jen...@digitaltoolbox-inc.com:
Are you referring to dmesg output? If so, does it matter in this
regards
whether the machine is a virtualized or not. The UPS is connected to a
Xen
Citeren Thomas Jensen tom.jen...@digitaltoolbox-inc.com:
Are you suggesting I temporarily hook up the UPS to a Windows machine,
install the software, and then use PerfMon to analyze the communications?
Yes. If this is not feasible, running it on a Linux box is acceptable
too, but not on a
Citeren Thomas Jensen tom.jen...@digitaltoolbox-inc.com:
server:#
upsdrvctl start
Network UPS Tools - UPS driver controller 2.2.2
Network
UPS Tools - CyberPower driver 1.00 (2.2.2)
Try running the powerpanel driver. The cyberpower driver is no longer
maintained and has no provisions for
On Tue, 23 Feb 2010 12:49:03 +0100, Arjen de Korte
nut+us...@de-korte.org
wrote:
Citeren Thomas Jensen tom.jen...@digitaltoolbox-inc.com:
server:#
upsdrvctl start
Network UPS Tools - UPS driver controller 2.2.2
Network
UPS Tools - CyberPower driver 1.00 (2.2.2)
Try running the
I recently purchased a Cyber Power 700 AVR UPS. I installed it just fine
and wanted to install NUT to monitor the unit.
I searched the mailing
list and found a similar post. However, the distro used in that post was
different and the unit was slightly different (900 AVR).
My server is
14 matches
Mail list logo
