Bug #4078
closedNUT fails to start with USB
0%
Description
On 64 bit, the NUT build is looking libusb.so.2, whereas the native build for 64 bit in /usr/lib is libusb.so.3. There is a libusb.so.2 present in the system, but it is a 32 bit build in /usr/lib32.
root: /usr/local/etc/rc.d/nut.sh start
starting usbhid-ups
Network UPS Tools - UPS driver controller 2.6.5
Shared object "libusb.so.2" not found, required by "usbhid-ups"
Driver failed to start (exit status=1)
usbhid-ups failed to start
root:
root: find / -name 'libusb*so*'
/usr/lib/libusbhid.so.4
/usr/lib/libusbhid.so
/usr/lib/libusb.so
/usr/lib/libusb.so.3
/usr/lib32/libusbhid.so.4
/usr/lib32/libusbhid.so
/usr/lib32/libusb.so.2
/usr/lib32/libusb.so
root:
/root: file /usr/local/libexec/nut/usbhid-ups
/usr/local/libexec/nut/usbhid-ups: symbolic link to `/usr/pbi/nut-amd64/libexec/nut/usbhid-ups'
root: ldd /usr/pbi/nut-amd64/libexec/nut/usbhid-ups
/usr/pbi/nut-amd64/libexec/nut/usbhid-ups:
libusb.so.2 => not found (0)
libthr.so.3 => /lib/libthr.so.3 (0x80075d000)
libc.so.7 => /lib/libc.so.7 (0x800982000)
Updated by Chris Buechler almost 10 years ago
- Priority changed from Very High to Normal
- Affected Architecture All added
- Affected Architecture deleted (
amd64)
Updated by Denny Page almost 10 years ago
After updating to 2.2 RC, removing the NUT package, cleaning up 2.1.5 NUT leftovers by hand, and reinstalling the NUT package under 2.2 RC, I now have a different problem:
/root: /usr/local/etc/rc.d/nut.sh start
starting usbhid-ups
/usr/local/etc/rc.d/nut.sh: /usr/local/libexec/nut/upsdrvctl: not found
usbhid-ups failed to start
Updated by Denny Page almost 10 years ago
I've determined that the USB problem was due to leftover files from the NUT install under pfSense 2.1.5. After having removed all the old NUT files by hand, the USB problem is no longer pertinent.
What remains is a simple startup script problem. I have created a new issue (4118) to track the script problem and would like to close issue 4078.
Denny
Updated by Denny Page almost 10 years ago
This issue can be closed. It is addressed by 4118.
Updated by Renato Botelho almost 10 years ago
- Status changed from New to Resolved
- Target version set to 2.2