Nut upsuser - Mar 2014 - PowerWalker VFI 3000RT LCD: Device or resource busy

UPS: PowerWalker VFI 3000RT LCD

CentOS 6.5, nut installed from RPM package:

nut-2.6.5-2.el6.x86_64
nut-client-2.6.5-2.el6.x86_64

Driver: blazer_usb

Problem description:

USB device "loops" when starting blazer_usb. USB device permissions
are ok.
Receives some information.

Error messages:

"failed to claim USB device: could not claim interface 0: Device or
resource busy"

"send: error sending control message: Broken pipe"

"blazer_rating: short reply"


/etc/ups/ups.conf
--- clip ---
[pw1]
        driver = blazer_usb
        port = auto
--- clip ---


/var/log/messages
--- clip ---
Mar  6 10:09:28 iron kernel: usb 2-1.7: new low speed USB device number 60
using ehci_hcd
Mar  6 10:09:28 iron kernel: usb 2-1.7: New USB device found,
idVendor=06da, idProduct=0005
Mar  6 10:09:28 iron kernel: usb 2-1.7: New USB device strings: Mfr=3,
Product=1, SerialNumber=0
Mar  6 10:09:28 iron kernel: usb 2-1.7: Product: USB UPS
Mar  6 10:09:28 iron kernel: usb 2-1.7: Manufacturer: PPC
Mar  6 10:09:28 iron kernel: usb 2-1.7: configuration #1 chosen from 1
choice
Mar  6 10:09:28 iron kernel: generic-usb 0003:06DA:0005.003C:
hiddev96,hidraw0: USB HID v1.11 Device [PPC USB UPS] on
usb-0000:00:1d.0-1.7/input0
Mar  6 10:09:30 iron kernel: usb 2-1.7: USB disconnect, device number 60
Mar  6 10:09:30 iron kernel: usb 2-1.7: new low speed USB device number 61
using ehci_hcd
Mar  6 10:09:30 iron kernel: usb 2-1.7: New USB device found,
idVendor=06da, idProduct=0005
Mar  6 10:09:30 iron kernel: usb 2-1.7: New USB device strings: Mfr=3,
Product=1, SerialNumber=0
Mar  6 10:09:30 iron kernel: usb 2-1.7: Product: USB UPS
Mar  6 10:09:30 iron kernel: usb 2-1.7: Manufacturer: PPC
...
--- clip ---

disconnected -> new device loop with increased device number


# blazer_usb -DDDDDDD -a pw1 -u root
--- clip ---
Network UPS Tools - Megatec/Q1 protocol USB driver 0.09 (2.6.5)
   0.000000     send_to_all: SETINFO driver.parameter.port "auto"
   0.000040     debug level is '7'
   0.000459     Checking device (06DA/0005) (002/062)
   0.004289     - VendorID: 06da
   0.004300     - ProductID: 0005
   0.004304     - Manufacturer: PPC
   0.004308     - Product: USB UPS
   0.004312     - Serial Number: unknown
   0.004316     - Bus: 002
   0.004319     Trying to match device
   0.004324     Device matches
   0.004338     failed to claim USB device: could not claim interface 0:
Device or resource busy
   0.004464     detached kernel driver from USB device...
   0.004859     send_to_all: SETINFO ups.vendorid "06da"
   0.004871     send_to_all: SETINFO ups.productid "0005"
   0.004879     send_to_all: SETINFO device.type "ups"
   0.004884     send_to_all: SETINFO driver.version "2.6.5"
   0.004890     send_to_all: SETINFO driver.version.internal "0.09"
   0.004897     send_to_all: SETINFO driver.name "blazer_usb"
   0.004902     Trying megatec protocol...
   0.005604     send: Q1
   0.239828     read: (229.2 229.2 229.6 005 50.0 2.20 24.6 00000001
   0.239872     send_to_all: SETINFO input.voltage "229.2"
   0.239880     send_to_all: SETINFO input.voltage.fault "229.2"
   0.239886     send_to_all: SETINFO output.voltage "229.6"
   0.239900     send_to_all: SETINFO ups.load "5"
   0.239907     send_to_all: SETINFO input.frequency "50.0"
   0.239914     send_to_all: SETINFO battery.voltage "2.20"
   0.239920     send_to_all: SETINFO ups.temperature "24.6"
   0.239926     send_to_all: SETINFO ups.beeper.status "enabled"
   0.239931     send_to_all: SETINFO ups.type "online"
   0.239938     send_to_all: SETINFO ups.status "OL"
   0.239942     Status read in 1 tries
   0.239946     Supported UPS detected with megatec protocol
   1.260203     send: error sending control message: Broken pipe
   1.462548     blazer_rating: short reply
   1.462559     Rating read 1 failed
--- clip ---

After this it checks all USB devices until founds the UPS again but from
device 002/063 and this goes on and on..

I believe this is not permission problem since it gets some reasonable
information from the UPS. I have also tried to setup device permissions to
666:

/lib/udev/rules.d/62-nut-usbups.rules
--- clip ---
#  Phoenixtec Innova RT  - blazer_usb
ATTR{idVendor}=="06da", ATTR{idProduct}=="0005",
MODE="666", GROUP="dialout"
--- clip ---

Device /dev/bus/usb/002/062 permissions were:

crw-rw-rw- 1 root dialout

Didn't help. I don't know why the groupname is dialout, it is the same
with
all rules (nut from RPM package). And yes, nut belongs to dialout group:

/etc/group
--- clip ---
dialout:x:18:nut
--- clip ---

I have also tried blazer_usb with every protocol: megatec, megatec/old,
zinto

I did some searching and found nothing, usually "failed to claim USB
device" problems were related to permission issues.


--
Tapio
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140306/fec83df8/attachment.html>

On Mar 6, 2014, at 5:09 AM, Tapio Korkki wrote:
> After this it checks all USB devices until founds the UPS again but from
device 002/063 and this goes on and on..
This part is going to be hard to fix. While it may be indirectly caused by NUT,
the UPS shouldn't completely disconnect from the USB bus in case of a
protocol error (there are many softer ways for it to fail while keeping the
connection).

It doesn't sound like it is the USB cable, but if you have another handy, it
can't hurt to try.
> I believe this is not permission problem since it gets some reasonable
information from the UPS. I have also tried to setup device permissions to 666:
> 
> /lib/udev/rules.d/62-nut-usbups.rules
> --- clip ---
> #  Phoenixtec Innova RT  - blazer_usb
> ATTR{idVendor}=="06da", ATTR{idProduct}=="0005",
MODE="666", GROUP="dialout"
> --- clip ---
That looks correct.
> Device /dev/bus/usb/002/062 permissions were: 
> 
> crw-rw-rw- 1 root dialout
> 
> Didn't help. I don't know why the groupname is dialout, it is the
same with all rules (nut from RPM package). And yes, nut belongs to dialout
group:
> 
> /etc/group
> --- clip ---
> dialout:x:18:nut
> --- clip ---
NUT can only be configured to run as one user/group for all drivers, so the
dialout group was picked since the serial ports are usually set to that group.
> I have also tried blazer_usb with every protocol: megatec, megatec/old,
zinto
What software does the manufacturer recommend for Windows systems?

-- 
Charles Lepple
clepple at gmail