Nut upsuser - Nov 2010 - NUT 2.4.3 on new server can not see serial number, but old nut on different hardware can?

hi

NUT 2.4.3 on new server can not see serial number, but old nut on different
hardware can?

I have 2 USB-hid ups from APC, 1500 and 3000 RM, i use the serial number to
identify them. However my new UPS monitor server can not see the serial number?

It works on 
	Linux dkserver 2.6.22.18-vs2.2.0.6 #1 SMP Sat Feb 16 20:54:32 CET 2008 i686
GNU/Linux
	debian package 2.2.2-6.5

it does not work on
	Linux dkplugbab9 2.6.32-00007-g56678ec #1 PREEMPT Mon Feb 8 03:49:55 PST 2010
armv5tel GNU/Linux
	NUT 2.4.3 self compiled

dkplugbab9:/usr/local/ups/etc# /usr/local/ups/bin/usbhid-ups -a apc1500 -u nut
-DD
Network UPS Tools - Generic HID driver 0.34 (2.4.3)
USB communication driver 0.31
   0.000000	debug level is '2'
   0.002738	upsdrv_initups...
   0.005059	Checking device (051D/0002) (001/011)
   0.005304	- VendorID: 051d
   0.005351	- ProductID: 0002
   0.005383	- Manufacturer: unknown
   0.005420	- Product: unknown
   0.005451	- Serial Number: unknown
   0.005486	- Bus: 001
   0.005516	Trying to match device
   0.005630	Device does not match - skipping


But if i use
	udevadm info --name=/dev/bus/usb/001/011 --attribute-walk 
i can see it just fine?

    ATTRS{manufacturer}=="American Power Conversion"
    ATTRS{product}=="Smart-UPS 1500 FW:653.12.I USB FW:4.2"
    ATTRS{serial}=="AS0535132782"


What is going on here?

Citeren Jon Bendtsen <jbendtsen op laerdal.dk>:
> NUT 2.4.3 on new server can not see serial number, but old nut on  
> different hardware can?
For the same UPS? It is not clear to me what the problem is. Are you  
attempting to monitor two devices from the same system, or are these  
connected to different systems?

Note that in your setup there are too many variables. Not only NUT  
versions are different, but also the kernel versions (and libusb  
versions). Diagnosing problems with that many changes is challenging.  
Try to limit the variables...

Best regards, Arjen
-- 
Please keep list traffic on the list (off-list replies will be rejected)

On Nov 12, 2010, at 11:16 AM, Jon Bendtsen wrote:
> dkplugbab9:/usr/local/ups/etc# /usr/local/ups/bin/usbhid-ups -a  
> apc1500 -u nut -DD
> Network UPS Tools - Generic HID driver 0.34 (2.4.3)
> USB communication driver 0.31
>   0.000000	debug level is '2'
>   0.002738	upsdrv_initups...
>   0.005059	Checking device (051D/0002) (001/011)
>   0.005304	- VendorID: 051d
>   0.005351	- ProductID: 0002
>   0.005383	- Manufacturer: unknown
>   0.005420	- Product: unknown
>   0.005451	- Serial Number: unknown
>   0.005486	- Bus: 001
>   0.005516	Trying to match device
>   0.005630	Device does not match - skipping
Arjen has a point about a lot of things changing at once, but one  
thing that can cause these items to show up as "unknown" is that the  
"nut" user doesn't have write access to the device.

In order to fetch a string from a USB device (such as the serial  
number), you need to be able to write a control message to it.

On the old system, the Debian packaging would have interacted with  
udev to set this up. Chances are that you just need to find the right  
place to drop the scripts/udev/nut-usbups.rules file, and tell udev to  
rescan the bus.

On 12/11/2010, at 18.45, Arjen de Korte wrote:
> Citeren Jon Bendtsen <jbendtsen at laerdal.dk>:
> 
>> NUT 2.4.3 on new server can not see serial number, but old nut on
different hardware can?
> 
> For the same UPS? It is not clear to me what the problem is. Are you
attempting to monitor two devices from the same system, or are these connected
to different systems?
the same UPS. I only run the monitor software on a new computer and no i do not
connect the UPS to 2 monitors.

> Note that in your setup there are too many variables. Not only NUT versions
are different, but also the kernel versions (and libusb versions). Diagnosing
problems with that many changes is challenging. Try to limit the variables...
i know, i can not do much different.

On 15/11/2010, at 13.11, Charles Lepple wrote:
> On Nov 15, 2010, at 6:59 AM, Jon Bendtsen wrote:
> 
>> So now I am only left pondering what is up with the ATTR and ATTRS
difference?
> 
> Ah, Gene Heskett just ran across this last night.
> 
> What does "udevadm --version" return?
> 
> We will need to figure out when they introduced that change.
On both the new and the old machine i get 125 as the version.

Looking closer in the old debian 52_nut-usbups.rules 
	SYSFS{idVendor}=="051d", SYSFS{idProduct}=="0002",
MODE="664", GROUP="nut"

And then in the new 52_nut-usbups.rules file
	ATTR{idVendor}=="051d", ATTR{idProduct}=="0002",
MODE="664", GROUP="nut"

And my change
	ATTRS{idVendor}=="051d", ATTRS{idProduct}=="0002",
MODE="664", GROUP="nut"

When i try with the SYSFS line on the new server that too works perfectly.