Arnaud Quette
2017-Jun-15 13:32 UTC
[Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB
Hi Manuel, 2017-06-14 15:16 GMT+02:00 Manuel Wolfshant <wolfy at nobugconsulting.ro>:> Hello > > > > On 06/14/2017 03:32 PM, Arnaud Quette wrote: > > > > On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> > wrote: > >> > >>> > If that matters, the OS is a fully updated CentOS 6.9 and this >>> (latest stable ) version of nut was packaged by me. The problem appears on >>> any of the USB ports ( well, I tried the 2 in front and one in the back of >>> the server ). >>> > >>> > lsusb -v reports: >>> ... >>> > wDescriptorLength 549 >>> > Warning: incomplete report descriptor >>> > Report Descriptor: (length is 9) >>> > Item(Main ): (null), data=none >>> >>> Because both NUT and lsusb are having trouble retrieving the HID Report >>> Descriptor, I think the problem is at a lower level: probably between the >>> UPS, the kernel, and the USB HCI. The archives have a number of unresolved >>> emails about the 5E and "broken pipe" errors. >>> >>> Probably worth checking with Eaton, too. >>> >> >> Charles is right in both the fact that the issue is (or at least seems to >> be) upstream to NUT, and also that it's worth checking with "Eaton" >> >> >> I've approached "them" ( apparently my request for supported landed >> at after-sales support/Romania ) as soon as Charles replied. Unfortunately >> the "dialogue" rather stalls, they seem to have a policy to not send more >> than one email every 3 days. Leaving aside that after telling them that I >> am using an *USB *unit (and providing USB-related logs ) they wanted to >> know if I was using *SNMP*. >> > > no comments ;) > > .... still no reply from them ... >is the guy you contacted Paul Henri?> > >> Could you please tell me your kernel >> >> [root at belgrade ~]# uname -r >> 2.6.32-696.3.1.el6.x86_64 >> > > that may be part of the issue... long time I've not tried the 2.x series, > not sure how it goes nowadays. > btw, any interesting "usb" messages from your syslog? > also, would you be able to test with a 3.x or 4.x, at least to see if that > improves / solves the issue? > > It's a bit tricky. I tried to use the kernel-lt package from the elrepo > repository ( incidentally I am also part of the elrepo team but I am in > charge with other packages, not the kernels ) and failed miserably. For > reasons unknown to me ( and not logged ) the system failed to boot and a > colleague from that office had to manually make it use the stock CentOS > kernel ( typing what I was dictating to him over the phone .. ) > Due to a complete lack of logs, I have absolutely no idea what happened > and since the machine is critical for the activity there, I am a bit > reluctant to try again > > > > Would you also be able to test some github code? >> We have the libusb-1.0 branch that provides both libusb 1.0 support >> (interesting to test to see if the problem still happens) along with few >> other improvements (though these should not help for your issue): >> https://github.com/networkupstools/nut/tree/libusb-1.0 >> >> I can and I will test ( tomorrow, probably ). >> > > I just packaged and tested it ( see below some comments, not important for > my issue here ) > Unfortunately there is no change in the output: > > [root at belgrade ~]#u root -x explore -x vendorid="0463" -a eaton > Network UPS Tools - Generic HID driver 0.42 (2.7.4.1) > USB communication driver (libusb 0.1) 0.33 > 0.000000 [D1] debug level is '4' > 0.012088 [D1] upsdrv_initups... > 8.248213 [D2] Checking device (0463/FFFF) (002/004) > 9.249069 [D2] - VendorID: 0463 > 9.249094 [D2] - ProductID: ffff > 9.249129 [D2] - Manufacturer: unknown > 9.249135 [D2] - Product: unknown > 9.249140 [D2] - Serial Number: unknown > 9.249145 [D2] - Bus: 002 > 9.249151 [D2] - Device release number: 0001 > 9.249156 [D2] Trying to match device > 9.249199 [D2] Device matches > 9.249209 [D2] failed to claim USB device: could not claim interface > 0: Device or resource busy > 9.249373 [D2] detached kernel driver from USB > device... > 9.249394 [D3] nut_usb_set_altinterface: skipped > usb_set_altinterface(udev, 0) > 9.249991 [D2] Unable to get HID descriptor (error sending control > message: Broken pipe) > 9.250002 [D3] HID descriptor length (method 1) > -1 > 9.250009 [D4] i=0, extra[i]=09, extra[i+1]=21 > > 9.250017 [D3] HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 > 01 22 25 02 > 9.250023 [D3] HID descriptor length (method 2) > 549 > 9.250028 [D2] HID descriptor length 549 > > 9.250515 [D2] Unable to get Report descriptor: Broken pipe > >argh, no improvement, but still with libusb 0.1. do you have libusb 1.0 -devel package installed? With that libusb1.0 nut branch, if both 1.0 and 0.1 are available, 1.0 will take precedence.> > Comments on the new tree: > a) there seem to be some missing files in the tree: > - some bits for augeas, devs and udev: > configure.ac:1526: required file `scripts/augeas/nutupsconf.aug.in' not > found > configure.ac:1526: required file `scripts/devd/nut-usb.conf.in' not found > configure.ac:1526: required file `scripts/udev/nut-usbups.rules.in' not > found >when using git, you must call autogen.sh prior to calling configure...> - all man pages > b) on top of that, I did not manage to include the manpages in the final > rpms because the new configure script insists on using tools not available > on CentOS 6 ( a newer asciidoc, for a start ) and I was too lazy to just > include the pages as they are. Why did you change that towards 2.7.4, oooh > why ? It was working sooooooooooooo fine.... >my mems fails to recall that specific point, but it was on purpose, not to bother users... FWIW, I modified the spec to create a separate subpackage for the> augeas lenses/modules -- those did not seem to exists in 2.7.4. If anyone > wishes to toy with the spec or rpm packages I will be happy to share them. >cheers Arno -- Eaton Data Center Automation Solutions - Opensource Leader - http://42ity.org NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170615/6c3ac529/attachment-0001.html>
Manuel Wolfshant
2017-Jun-16 10:12 UTC
[Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/15/2017 04:32 PM, Arnaud Quette wrote: Hello> > .... still no reply from them ... > > is the guy you contacted Paul Henri?I wrote to a generic alias ( Ro-PQSupport ). Got a reply from a fellow Romanian who also CC:ed something looking like a list (List-EGPQCO-BUCRO-PQ ). I replied to both of them 5 days ago, received nothing since.> >>> Would you also be able to test some github code? >>> We have the libusb-1.0 branch that provides both libusb 1.0 >>> support (interesting to test to see if the problem still >>> happens) along with few other improvements (though these should >>> not help for your issue): >>> https://github.com/networkupstools/nut/tree/libusb-1.0 >>> <https://github.com/networkupstools/nut/tree/libusb-1.0> >> > > argh, no improvement, but still with libusb 0.1. > do you have libusb 1.0 -devel package installed? With that libusb1.0 > nut branch, if both 1.0 and 0.1 are available, 1.0 will take precedence.I just tried using libusb-1.0 instead of 0.1 (the only change I did was to replace libusb 0.1-devel with libusb 1.0-devel in the buildroot ) but it did not fly. I'll try to see what was missing and fix: libtool: link: gcc -I../include -I/usr/include/libusb-1.0 -DNETSNMP_ENABLE_IPV6 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_RPM_4_4_COMPAT -Ulinux -Dlinux=linux -I/usr/include/rpm -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib64/perl5/CORE -I/usr/include -I/usr/include/neon -I/usr/include/modbus -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wl,-z -Wl,now -Wl,-z -Wl,relro -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -o snmp-ups snmp-ups.o apc-mib.o baytech-mib.o compaq-mib.o eaton-mib.o ietf-mib.o mge-mib.o netvision-mib.o powerware-mib.o raritan-pdu-mib.o bestpower-mib.o cyberpower-mib.o delta_ups-mib.o xppc-mib.o huawei-mib.o eaton-ats16-mib.o apc-ats-mib.o raritan-px2-mib.o eaton-ats30-mib.o apc-pdu-mib.o main.o dstate.o -Wl,-z -Wl,relro -Wl,-z -Wl,now ../common/.libs/libcommon.a ../common/.libs/libparseconf.a -L/usr/lib64 -lnetsnmp -lpthread nutdrv_qx-nutdrv_qx.o: In function `ippon_command': /builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:679: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:692: undefined reference to `libusb_strerror' nutdrv_qx-nutdrv_qx.o: In function `fabula_command': /builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:907: undefined reference to `libusb_strerror' nutdrv_qx-nutdrv_qx.o: In function `krauler_command': /builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:770: undefined reference to `libusb_strerror' nutdrv_qx-nutdrv_qx.o: In function `sgs_command': /builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:542: undefined reference to `libusb_strerror' nutdrv_qx-nutdrv_qx.o:/builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:568: more undefined references to `libusb_strerror' follow collect2: ld returned 1 exit status make[1]: *** [nutdrv_qx] Error 1 [...] libtool: link: gcc -I../include -I/usr/include/libusb-1.0 -DNETSNMP_ENABLE_IPV6 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_RPM_4_4_COMPAT -Ulinux -Dlinux=linux -I/usr/include/rpm -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib64/perl5/CORE -I/usr/include -I/usr/include/neon -I/usr/include/modbus -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wl,-z -Wl,now -Wl,-z -Wl,relro -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -o bcmxcp_usb bcmxcp_usb.o bcmxcp.o usb-common.o main.o dstate.o ../common/.libs/libcommon.a ../common/.libs/libparseconf.a -lusb-1.0 -lm -lpthread bcmxcp_usb.o: In function `nutusb_open': /builddir/build/BUILD/nut-libusb-1.0/drivers/bcmxcp_usb.c:515: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-libusb-1.0/drivers/bcmxcp_usb.c:504: undefined reference to `libusb_strerror' collect2: ld returned 1 exit status make[1]: *** [bcmxcp_usb] Error 1 libusb1.o: In function `nut_libusb_strerror': /builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:484: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:469: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:479: undefined reference to `libusb_strerror' libusb1.o: In function `nut_libusb_open': /builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:181: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:282: undefined reference to `libusb_strerror' libusb1.o:/builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:289: more undefined references to `libusb_strerror' follow collect2: ld returned 1 exit status make[1]: *** [usbhid-ups] Error 1> > > Comments on the new tree: > a) there seem to be some missing files in the tree: > - some bits for augeas, devs and udev: > configure.ac:1526 <http://configure.ac:1526>: required file > `scripts/augeas/nutupsconf.aug.in <http://nutupsconf.aug.in>' not > found > configure.ac:1526 <http://configure.ac:1526>: required file > `scripts/devd/nut-usb.conf.in <http://nut-usb.conf.in>' not found > configure.ac:1526 <http://configure.ac:1526>: required file > `scripts/udev/nut-usbups.rules.in <http://nut-usbups.rules.in>' > not found > > > when using git, you must call autogen.sh prior to calling configure...running autogen.sh was triggered automatically. but even if I do it explicitly, I still get: + autoreconf -i configure.ac:887: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from... /usr/share/aclocal/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from... /usr/share/aclocal/libtool.m4:4161: _LT_LINKER_SHLIBS is expanded from... /usr/share/aclocal/libtool.m4:5236: _LT_LANG_C_CONFIG is expanded from... /usr/share/aclocal/libtool.m4:138: _LT_SETUP is expanded from... /usr/share/aclocal/libtool.m4:67: LT_INIT is expanded from... /usr/share/aclocal/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... configure.ac:887: the top level [.... looong part of output deleted...] configure.ac:1526: required file `scripts/augeas/nutupsconf.aug.in' not found configure.ac:1526: required file `scripts/devd/nut-usb.conf.in' not found configure.ac:1526: required file `scripts/udev/nut-usbups.rules.in' not found Makefile.am: installing `./INSTALL' autoreconf: automake failed with exit status: 1 error: Bad exit status from /var/tmp/rpm-tmp.F5xT0r (%build) Bad exit status from /var/tmp/rpm-tmp.F5xT0r (%build) regards, manuel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170616/55e31779/attachment-0001.html>
Charles Lepple
2017-Jun-18 14:42 UTC
[Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB
On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote:> > running autogen.sh was triggered automatically. but even if I do it explicitly, I still get: > + autoreconf -i > configure.ac:887: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body > ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... > ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from... > ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from... > /usr/share/aclocal/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from... > /usr/share/aclocal/libtool.m4:4161: _LT_LINKER_SHLIBS is expanded from... > /usr/share/aclocal/libtool.m4:5236: _LT_LANG_C_CONFIG is expanded from... > /usr/share/aclocal/libtool.m4:138: _LT_SETUP is expanded from... > /usr/share/aclocal/libtool.m4:67: LT_INIT is expanded from... > /usr/share/aclocal/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... > configure.ac:887: the top level > > [.... looong part of output deleted...] > > configure.ac:1526: required file `scripts/augeas/nutupsconf.aug.in' not found > configure.ac:1526: required file `scripts/devd/nut-usb.conf.in' not found > configure.ac:1526: required file `scripts/udev/nut-usbups.rules.in' not found > Makefile.am: installing `./INSTALL' > autoreconf: automake failed with exit status: 1This sounds like an autotools incompatibility. Which versions of autoconf, automake, libtool, etc. are you using? In the mean time, Buildbot generates snapshots using "make dist" that do not require auto*. Since there have not been any recent builds, they aren't on the first page of the waterfall, but usually there is a link to the snapshot off of the Debian jessie builder when the branch is rebuilt. Here is the generic URL: http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/snapshot/libusb-1.0/nut-latest.tar.gz <http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/snapshot/libusb-1.0/nut-latest.tar.gz> If you need a specific version for the .spec file, that link currently points to http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/snapshot/libusb-1.0/rb1314c693bef0ce639991dcee6e5742f25e94a88-753/nut-v2.7.4-418-gb1314c62.7.4.1.tar.gz <http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/snapshot/libusb-1.0/rb1314c693bef0ce639991dcee6e5742f25e94a88-753/nut-v2.7.4-418-gb1314c62.7.4.1.tar.gz> (not a typo; the code that generates the version stuck in both 2.7.4 and 2.7.4.1) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170618/eabed40e/attachment.html>