Nut upsuser - Sep 2015 - UPS/NUT with openSUSE 13.1

On Tue, 8 Sep 2015, Rob Groner wrote:
> I executed lsusb to verify the USB device is there, and it is.  I tried 
> the shutdown command again with debug enabled, but it didn't seem to 
> reveal much more:
>
-----------------------------------------------------------------------------------------------
> rtd at linux-5048:~> sudo /usr/local/ups/sbin/upsdrvctl -DDDDD shutdown
> Network UPS Tools - UPS driver controller 2.7.2.6_RTD
...
>   0.000137     Shutdown UPS: rtdups
>   0.000160     exec:  /usr/local/ups/bin/usbhid-ups -a rtdups -k
> Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD)
> USB communication driver 0.32
> Can't claim USB device [2a37:5110]: No such file or directory
>   0.007491     Driver failed to start (exit status=1)
>
-----------------------------------------------------------------------------------------------
Hello Bob, What happens if you execute the command

   /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD

Best Regards, Roger

Roger,

rtd at linux-5048> sudo /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD
Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD)
USB communication driver 0.32
   0.000000	debug level is '3'
   0.000405	upsdrv_initups...
   0.004386	Checking device (0930/6545) (002/002)
   0.004431	Failed to open device, skipping. (Permission denied)
   0.004442	Checking device (1D6B/0002) (002/001)
   0.004468	Failed to open device, skipping. (Permission denied)
   0.004479	Checking device (1D6B/0001) (008/001)
   0.004494	Failed to open device, skipping. (Permission denied)
   0.004504	Checking device (1D6B/0001) (007/001)
   0.004518	Failed to open device, skipping. (Permission denied)
   0.004530	Checking device (1D6B/0001) (006/001)
   0.004545	Failed to open device, skipping. (Permission denied)
   0.004555	Checking device (2A37/5110) (001/005)
   0.005862	- VendorID: 2a37
   0.005876	- ProductID: 5110
   0.005884	- Manufacturer: RTD Embedded Technologies, Inc.
   0.005891	- Product: UPS25110
   0.005898	- Serial Number: 123456789ABC
   0.005906	- Bus: 001
   0.005914	Trying to match device
   0.005927	Device matches
   0.005940	failed to claim USB device: Device or resource busy
   0.005954	failed to detach kernel driver from USB device: No such file or
directory
   0.005964	failed to claim USB device: Device or resource busy
   0.005974	failed to detach kernel driver from USB device: No such file or
directory
   0.005984	failed to claim USB device: Device or resource busy
   0.005993	failed to detach kernel driver from USB device: No such file or
directory
   0.006003	failed to claim USB device: Device or resource busy
   0.006013	failed to detach kernel driver from USB device: No such file or
directory
   0.006023	Can't claim USB device [2a37:5110]: No such file or directory



Rob Groner
Software Engineer Level II

RTD Embedded Technologies, Inc.
ISO 9001 and AS9100 Certified
Ph: +1 814-234-8087
www.rtd.com

-----Original Message-----
From: Nut-upsuser [mailto:nut-upsuser-bounces+rgroner=rtd.com at
lists.alioth.debian.org] On Behalf Of Roger Price
Sent: Tuesday, September 08, 2015 4:25 PM
To: nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org>
Subject: Re: [Nut-upsuser] UPS/NUT with openSUSE 13.1

On Tue, 8 Sep 2015, Rob Groner wrote:
> I executed lsusb to verify the USB device is there, and it is.  I 
> tried the shutdown command again with debug enabled, but it didn't 
> seem to reveal much more:
> ----------------------------------------------------------------------
> ------------------------- rtd at linux-5048:~> sudo 
> /usr/local/ups/sbin/upsdrvctl -DDDDD shutdown Network UPS Tools - UPS 
> driver controller 2.7.2.6_RTD
...
>   0.000137     Shutdown UPS: rtdups
>   0.000160     exec:  /usr/local/ups/bin/usbhid-ups -a rtdups -k
> Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) USB 
> communication driver 0.32 Can't claim USB device [2a37:5110]: No such 
> file or directory
>   0.007491     Driver failed to start (exit status=1)
> ----------------------------------------------------------------------
> -------------------------
Hello Bob, What happens if you execute the command

   /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD

Best Regards, Roger


_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

On Tue, 8 Sep 2015, Rob Groner wrote:
> Roger,
>
> rtd at linux-5048> sudo /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD
> Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD)
> USB communication driver 0.32
>   0.000000	debug level is '3'
>   0.000405	upsdrv_initups...
...
>   0.004555	Checking device (2A37/5110) (001/005)
>   0.005862	- VendorID: 2a37
>   0.005876	- ProductID: 5110
>   0.005884	- Manufacturer: RTD Embedded Technologies, Inc.
>   0.005891	- Product: UPS25110
>   0.005898	- Serial Number: 123456789ABC
>   0.005906	- Bus: 001
>   0.005914	Trying to match device
>   0.005927	Device matches
>   0.005940	failed to claim USB device: Device or resource busy
>   0.005954	failed to detach kernel driver from USB device: No such file or
directory
Hello Bob, I'm not an expert in usbhid-ups: perhaps someone else on this
list can explain what's happening at 0.005940.  Roger

On Sep 8, 2015, at 4:48 PM, Rob Groner <rgroner at RTD.com>
wrote:
> 
>   0.005927	Device matches
>   0.005940	failed to claim USB device: Device or resource busy
>   0.005954	failed to detach kernel driver from USB device: No such file or
directory
Rob,

this is a bit of a tough one to track down.

The "Device or resource busy" message can either come from a kernel
driver (usbhid, etc.) or from another userspace program. The simplest thing is
to check for other copies of usbhid-ups (at the point when you run
'<driver> -k', it is expected that most processes will have
terminated).

If it isn't that, you may need to verify whether you are compiling against
libusb-0.1.x, or libusb+libusb-compat. In theory, it shouldn't make any
difference, but in practice, there might be subtle differences in error messages
that could help narrow things down.

Also, what does 'dmesg' say around the time that you run the driver?

-- 
Charles Lepple
clepple at gmail