Since a few days, I think I have the same behavior on a small ARM server
running Debian Jessie with an Eaton Protection Station 800USB and
usbhid-ups driver.
I keep getting messages with the pattern "UPS xxx@yyy is unavailable".
If I run lsusb, the UPS does appear (first line, bus 001 device 014):
root@b3:/etc/nut# lsusb
Bus 001 Device 014: ID 0463:ffff MGE UPS Systems UPS
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@b3:/etc/nut#
If I look for this 001/014 device in /dev/bus/usb, I don't see it:
root@b3:/etc/nut# ls -lR /dev/bus/usb/001
/dev/bus/usb/001:
total 0
crw-rw-r-T 1 root root 189, 0 Sep 30 09:16 001
crw-rw-r-T 1 root root 189, 1 Sep 30 09:16 002
crw-rw-r-T 1 root nut 189, 2 Jul 28 17:24 003
crw-rw-r-T 1 root nut 189, 4 Aug 25 05:10 005
crw-rw-r-T 1 root nut 189, 5 Aug 25 12:46 006
crw-rw-r-T 1 root nut 189, 7 Sep 3 12:48 008
crw-rw-r-T 1 root nut 189, 9 Sep 27 06:41 010
root@b3:/etc/nut#
I see several previous numbers for the device (003, 005, 006, 008, 010),
probably remains of previous restarts, but I do not see number 014.
If I run the driver manually in debug mode to get some info, I only see
the two hub devices (001 and 002), but not the 014, probably because it
does not show up in /dev/bus/usb :
root@b3:/etc/nut# /lib/nut/usbhid-ups -DDDD -a zintiel
Network UPS Tools - Generic HID driver 0.37 (2.6.5)
USB communication driver 0.31
0.000000 debug level is '4'
0.003376 upsdrv_initups...
0.005297 Checking device (05E3/0608) (001/002)
0.006014 - VendorID: 05e3
0.009693 - ProductID: 0608
0.010199 - Manufacturer: unknown
0.010690 - Product: unknown
0.011148 - Serial Number: unknown
0.011598 - Bus: 001
0.012045 Trying to match device
0.012589 Device does not match - skipping
0.013137 Checking device (1D6B/0002) (001/001)
0.013740 - VendorID: 1d6b
0.014391 - ProductID: 0002
0.014861 - Manufacturer: unknown
0.015315 - Product: unknown
0.015765 - Serial Number: unknown
0.016215 - Bus: 001
0.016658 Trying to match device
0.017017 Device does not match - skipping
0.017095 No appropriate HID device found
0.017358 No matching HID UPS found
root@b3:/etc/nut#
If I try to run "udevadm trigger" to force events, nothing happens.
The /lib/udev/rules.d/52-nut-usbups.rules appears to come from
nut-server. The nut-server version I have is:
root@b3:/etc/nut# aptitude show nut-server
Package: nut-server
New: yes
State: installed
Automatically installed: no
Version: 2.6.5-4
Priority: optional
Section: admin
Maintainer: Arnaud Quette <aque...@debian.org>
Architecture: armel
Uncompressed Size: 2817 k
Depends: libc6 (>= 2.15), libupsclient1 (>= 2.4.1), libusb-0.1-4 (>=
2:0.1.12), libwrap0 (>= 7.6-4~), init-system-helpers (>=
1.4), adduser, lsb-base (>= 3.0-6), udev (>= 0.124-1),
nut-client (= 2.6.5-4)
Suggests: nut-cgi, nut-snmp, nut-ipmi, nut-xml
Conflicts: nut-hal-drivers
Breaks: nut (< 2.6.1-2~)
Replaces: nut (< 2.6.1-2~)
Description: network UPS tools - core system
Network UPS Tools (NUT) is a client/server monitoring system that
allows computers to share uninterruptible power supply (UPS)
and power distribution unit (PDU) hardware. Clients access the hardware
through the server, and are notified whenever the power
status changes.
This package provides NUT's core system, and the serial and USB UPS
drivers.
Homepage: http://www.networkupstools.org/
root@b3:/etc/nut#
Contrary to what is writtent in message #10 above, I do not see any
SYSFS attribute in the 52-nut-usbups.rules, but I see ATTR. This file
have worked for me for a while. The rules corresponding to my Eaton UPS
seems to be (the second one should be applied in my case since lsusb
identifies my device as 0463:ffff).
# Eaton
# various models - usbhid-ups
ATTR{idVendor}=="0463", ATTR{idProduct}=="0001", MODE="664", GROUP="nut"
# various models - usbhid-ups
ATTR{idVendor}=="0463", ATTR{idProduct}=="ffff", MODE="664", GROUP="nut"
best regards,
Luc
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
