[Nut-upsuser] Usbhip-ups going wild

[Arnaud Quette]

2009/8/5 Antoine Gatineau <antoine.gatineau at alcatel-lucent.com>

>  Well,
>
> I have unfortunately uplugged the usb cord. Now I am not able to start the
> drivers again.
> When I plug in the usb cord I get :
> Aug  5 16:23:33 localhost kernel: usb 3-2: new low speed USB device using
> address 6
> Aug  5 16:23:34 localhost kernel: usbhid: probe of 3-2:1.0 failed with
> error -5
>
> When I start the nut driver using upsdrvctl start, I get :
> Aug  5 16:24:05 localhost upsdrvctl: Can't claim USB device [0463:ffff]:
> could not detach kernel driver from interface 0: Operation not permitted
> Aug  5 16:24:05 localhost upsdrvctl: Network UPS Tools - Generic HID driver
> 0.34 (2.4.1)
> Aug  5 16:24:05 localhost upsdrvctl: USB communication driver 0.31
> Aug  5 16:24:05 localhost upsdrvctl: Network UPS Tools - UPS driver
> controller 2.4.1
> Aug  5 16:24:05 localhost upsdrvctl: Driver failed to start (exit status=1)
>
> I gess there are some conflicts somewhere. What is really wierd is that I
> get the same messages after reboot or reinstallation of the rpms.
> Any idea?
>

check that your hotplug or udev file is installed correctly, and that the
permissions on the USB device are correctly set (using the lsusb + ls -l
/dev/bus/usb/XXX/YYY method)

to first validate that it's a device perm issue, simply launch the driver as
root, ie:
$ /path/to/usbhid-ups -a <ups>

this should start and happily says "Detected something..."

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/


>  ------------------------------
> *De :* Arnaud Quette [mailto:aquette.dev at gmail.com]
> *Envoyé :* mercredi 5 août 2009 11:16
>
> *À :* Antoine Gatineau
> *Cc :* nut-upsuser
> *Objet :* Re: [Nut-upsuser] Usbhip-ups going wild
>
>
> 2009/8/4 Antoine Gatineau <antoine.gatineau at alcatel-lucent.com>
>
>>  Hello everyone,
>>
>
> Hi Antoine,
>
>
>>
>> I have nut and nut-client installed from rpm, up and running without any
>> error in the logs or at screen.
>> upsc gives me the state of the battery and stuff. It seems functional.
>>
>
> nice
>
>
>>  Is there something to do in order to verify the health of the whole
>> chain? (upsmon -> upsd -> upsdrv)
>>
>
> yep, unplug the UPS' power cord, and check that upsc has an ups.status = OB
>
>
>
>>  One last question, after installing the rpms, /var/state/ups is not
>> created and the rights are not given like it should. I was suprised to see
>> that this was not ntegrated in RHEL5 rpms... Is there some restriction to
>> integrate that configuration?
>>
>
> most modern distro have a volatile /var fs. For example, on Debian, the
> init.d script create these dirs at launch time...
>
> cheers,
> Arnaud
> --
> Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
> Debian Developer - http://www.debian.org
> Free Software Developer - http://arnaud.quette.free.fr/
>
>
>>  ------------------------------
>>  *De :* Arnaud Quette [mailto:aquette.dev at gmail.com]
>> *Envoyé :* lundi 3 août 2009 21:46
>> *À :* Antoine Gatineau
>> *Cc :* nut-upsuser
>> *Objet :* Re: [Nut-upsuser] Usbhip-ups going wild
>>
>>
>>
>> 2009/8/3 Antoine Gatineau <antoine.gatineau at alcatel-lucent.com>
>>
>>>  I tried to recompile without xorg-x11-devel and I get this error :
>>> configure: error: libgd not found, required for CGI build.
>>> It is indeed required for nut-cgi
>>> udev-devel, however, is not required.
>>>
>>>
>>
>> yup, you got me wrong: only the dbus-glib as to be removed. xorg-devel (or
>> xpm-devel) is needed for nut-cgi
>>
>>
>>>  Anyway I made it build correctly.
>>> I attached nut.spec (modified for RHEL4) and nut.spec.ori (original spec
>>> file for RHEL5) for info.
>>>
>>> There were no %files entry for libhidups, libhid.usermap
>>>
>>
>> these 2 are for hotplug. if you use udev, you don't need these.
>>
>>
>>>  and 20-ups-nut-device.fdi
>>>
>>
>> this file is for HAL. so not needed too.
>>
>>
>>>  in the original spec file, so I added them. I'm not an rpm building
>>> expert but I wonder how it could work...
>>> I also removed hal, powerman and netxml-ups man page and related files as
>>> they are not used in this package.
>>>
>>> I didn't test it running yet but I expect it to be OK. I'll come back to
>>> you with results.
>>>
>>> BTW, in the first answer to this (too?) long thread, Arjen said that
>>> there were lot of bug fixes and performance improvement done since
>>> nut-2.2.0. Is there a bug tracker to seek if my issues will be solved with
>>> this new one?
>>>
>>
>> to be short: ChangeLog
>>
>> cheers
>> Arnaud
>> --
>> Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
>> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
>> Debian Developer - http://www.debian.org
>> Free Software Developer - http://arnaud.quette.free.fr/
>>
>>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090805/4895b60d/attachment-0001.htm>