[Nut-upsuser] Liebert PSIXR 3000 intellislot web card support with NUT 2.6.0
Hi, Just started using NUT with a Liebert PSI-XR 3000 with an Intellislot web card. It seems I can't get it to run properly. I am using NUT 2.6.0 built from source on Ubuntu 8.0.4 . My build parameters are : ./configure --enable-strip --with-linux-hiddev=/usr/include/linux/hiddev.h --with-udev-dir=/lib/udev \ --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \ --mandir=/usr/share/man \ --libdir=/lib \ --includedir=/usr/include \ --without-ssl \ --with-dev \ --enable-static \ --with-statepath=/var/run/nut \ --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut \ --with-htmlpath=/usr/share/nut/www \ --with-pidpath=/var/run/nut \ --datadir=/usr/share/nut \ --with-pkgconfig-dir=/usr/lib/pkgconfig \ --with-user=nut --with-group=nut I get this when I run upsdrvctl start Detected LiebertPSI on host 192.168.0.11 (mib: ietf 1.3) [liebertpsiweb] unhandled ASN 0x6 recieved from 1.3.6.1.2.1.33.1.7.1.0 Then when I run /etc/init.d/nut I get * Starting Network UPS Tools[ OK ] Broadcast Message from n...@mail.sop.com.my (somewhere) at 1:02 ... Communications with UPS liebertpsiweb@localhost lost Running upsc liebertpsiweb@localhost gets me : battery.charge: 100.00 battery.current: 0.00 battery.runtime: 0.00 battery.runtime.low: 120.00 battery.temperature: 30.00 battery.voltage: 55.00 beeper.status: enabled device.mfr: Emerson Network Power device.model: LiebertPSI device.type: ups driver.name: snmp-ups driver.parameter.mibs: auto driver.parameter.pollinterval: 2 driver.parameter.port: 192.168.0.11 driver.version: 2.6.0 driver.version.internal: 0.50 (mib: ietf 1.3) input.bypass.phases: 0.00 input.current: 0.00 input.frequency: 50.00 input.frequency.nominal: 50.00 input.phases: 1.00 input.realpower: 0.00 input.transfer.high: 0.00 input.transfer.low: 0.00 input.voltage: 247.00 input.voltage.nominal: 2300.00 output.current: 0.00 output.frequency: 50.00 output.frequency.nominal: 50.00 output.phases: 1.00 output.power.nominal: 0.00 output.realpower: 0.00 output.realpower.nominal: 0.00 output.voltage: 249.00 output.voltage.nominal: 2300.00 ups.firmware: EX000842 ups.firmware.aux: 2.39.CP504.ABE.00 ups.load: 17.00 ups.mfr: Emerson Network Power ups.model: LiebertPSI ups.start.auto: no ups.status: ups.test.result: done and passed ups.timer.reboot: -1 ups.timer.shutdown: -1 ups.timer.start: -1 What can I do or is this particular model not supported? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Problems with usbhid-ups and CyberPower CP1500 on 2.6.0
On 3/15/2011 6:22, Charles Lepple wrote: On Mar 14, 2011, at 1:20 AM, Cheetah wrote: If I run it under strace, the ioctls on the /dev/bus/usb file descriptor preceeding each operation not permitted error return 0, not an error code such as EPERM. That seems strange. Would you please compress and send the strace output (without -u root)? Attached. Also, what architecture is this running on? x86_64, Intel X58 chipset, core i7 series processor. usbhid-ups.strace.gz Description: GNU Zip compressed data ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Problems with usbhid-ups and CyberPower CP1500 on 2.6.0
On Wed, Mar 16, 2011 at 5:02 PM, Cheetah fast...@gmail.com wrote: On 3/15/2011 6:22, Charles Lepple wrote: On Mar 14, 2011, at 1:20 AM, Cheetah wrote: If I run it under strace, the ioctls on the /dev/bus/usb file descriptor preceeding each operation not permitted error return 0, not an error code such as EPERM. That seems strange. Would you please compress and send the strace output (without -u root)? Attached. Looks like Ubuntu fixed 2.4.3 here: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/572262 That was committed to NUT here: http://trac.networkupstools.org/projects/nut/changeset/2407 This breaks reading larger reports, so it was reverted: http://trac.networkupstools.org/projects/nut/changeset/2719 This patch (committed after 2.6.0 was released) claims to restore 2.4.1 behavior: http://trac.networkupstools.org/projects/nut/changeset/2893 Arjen: do we actually have any cases of reports larger than 8 bytes? If so, should we mark this as a quirk for CyberPower devices? Also, it seems like we need to distinguish between returning 0 and 0 from the libusb call. Currently, we are reading errno when a zero-length packet is being read. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
