Broken Packages? apcupsd and nut
-
Hi,
Rather than posting all the info again here, please see the thread at https://forum.pfsense.org/index.php?topic=80248.0.
Apcupsd and nut are not working, USB issues it seems (due to package install not being quite right?).
Thanks!
-
Hi,
It really does look like my issue here is USB support - is anyone having luck with USB devices in v2.2?
Thanks!
-
Hi
Yes i have very luck with USB :). -
That is good news! Any luck with apcupsd or nut (monitoring a UPS)?
Thanks!
-
I have thinking to bay a APC 1400 2u RACK UPS but using it on a serial and after that maybe in the network module, no USB in my thinking. But USB seems working great, i don't know on this packages.
-
APCUPSD works for me.
NUT does not after update from 2.1.5 to 2.2 built on Mon Dec 01 03:30:23 CST 2014.
Config was working with 2.1.5..
-
Hi,
Agree, NUT doesn't work for me either. APCUPSD … no go, but closer! A couple things,
- I have to manually edit apcupsd to remove "BLANK" from UPSTYPE (and actually make it blank, which the GUI won't accept).
- restart the service (apcupsd)
But even then, I get "STATUS : COMMLOST"
Thoughts?
Thanks!
-
Why not put USB there? I misread the lines below when I first tried and I wonder if you may have done the same? :o :)
To get apcupsd to work, in addition to defining the cable above, you must also define a UPSTYPE, which corresponds to the type of UPS you have (see the Description for more details).
This is for the first line where I have "USB"..
You must also specify a DEVICE, sometimes referred to as a port. For USB UPSes, please leave the DEVICE directive blank. For other UPS types, you must specify an appropriate port or address.
This is for the second line which is blank.
-
Hi,
That's what I tried, but when I leave the second line blank (like you have), this is the error I receive,
The following input errors were detected:
The field UPS Type / Device is required.
Perhaps it's a v2.2 issue?
Thanks!
-
The problem, at least in my case, appears to be a 64/32 bit mismatch between nut and libusb. Nut is built 64 bit but looking for libusb.so.2. The 64 bit version of libusb is libusb.so.3. libusb.so.2 is 32 bit only.
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 'libusbso'
/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)
