Nut upsuser - Oct 2010 - usbhid-ups did not claim interface 0 before use

Hi,

I tried in vain to find an answer for my question, so let's post it 
here. I've got a seemingly perfectly well running setup with NUT and a 
APC SmartUPS 750. However, my log is being filled with messages like this:

Oct 13 12:13:08 alkmene kernel: usb 3-1: usbfs: process 16588 
(usbhid-ups) did not claim interface 0 before use
Oct 13 12:13:40 alkmene last message repeated 43 times
Oct 13 12:14:42 alkmene last message repeated 85 times
Oct 13 12:15:44 alkmene last message repeated 85 times


# upsc smartups750 at localhost ups.status
OL

How to prevent these messages? Is something wrong (probably). How to 
debug it.

Thanks,

Mark

CentOS 5.4
nut-2.2.0-7.el5
nut-client-2.2.0-7.el5


-- 
Oudenhof 14b, 4191 NW Geldermalsen, The Netherlands
Web site and travel directions:   www.in2sports.net
Phone +31.88.0084102    ::    Mobile +31.6.51298623

Citeren Mark Ruys <mark.ruys op in2sports.net>:
> How to prevent these messages? Is something wrong (probably). How to  
> debug it.
>
> Thanks,
>
> Mark
>
> CentOS 5.4
> nut-2.2.0-7.el5
> nut-client-2.2.0-7.el5
Upgrade NUT to the latest version first. Loads of changes have been  
made to the usbhid-ups driver since nut-2.2.0 was released well over  
three years ago. We no longer support this version.

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

Op 19-10-2010 23:57, Arjen de Korte schreef:
> Citeren Mark Ruys <mark.ruys at in2sports.net>:
>
>> How to prevent these messages? Is something wrong (probably). How to 
>> debug it.
>>
>> Thanks,
>>
>> Mark
>>
>> CentOS 5.4
>> nut-2.2.0-7.el5
>> nut-client-2.2.0-7.el5
>
> Upgrade NUT to the latest version first. Loads of changes have been 
> made to the usbhid-ups driver since nut-2.2.0 was released well over 
> three years ago. We no longer support this version.
>
> Best regards, Arjen
Okay, I upgraded to 2.4.3 and restarted nut. I still get:

Oct 20 11:33:16 alkmene kernel: usb 3-1: usbfs: process 16588
(usbhid-ups) did not claim interface 0 before use
Oct 20 11:33:48 alkmene last message repeated 43 times
Oct 20 11:34:50 alkmene last message repeated 85 times


Thanks, Mark

-- 
Oudenhof 14b, 4191 NW Geldermalsen, The Netherlands
Web site and travel directions:   www.in2sports.net
Phone +31.88.0084102    ::    Mobile +31.6.51298623

Hi Mark,

2010/10/20 Mark Ruys
>  Op 19-10-2010 23:57, Arjen de Korte schreef:
>
>  Citeren Mark Ruys :
>>
>>  How to prevent these messages? Is something wrong (probably). How to
>>> debug it.
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>> CentOS 5.4
>>> nut-2.2.0-7.el5
>>> nut-client-2.2.0-7.el5
>>>
>>
>> Upgrade NUT to the latest version first. Loads of changes have been
made
>> to the usbhid-ups driver since nut-2.2.0 was released well over three
years
>> ago. We no longer support this version.
>>
>> Best regards, Arjen
>>
>
> Okay, I upgraded to 2.4.3 and restarted nut. I still get:
>
> Oct 20 11:33:16 alkmene kernel: usb 3-1: usbfs: process 16588
>
> (usbhid-ups) did not claim interface 0 before use
> Oct 20 11:33:48 alkmene last message repeated 43 times
> Oct 20 11:34:50 alkmene last message repeated 85 times
>
upgrading NUT is not enough: you also have to stop the old instances and
start new ones that use the newly installed version.
this remark comes from the fact the PID above (16588) is the same than the
previous "faulty" one.

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/20101021/cb350245/attachment.htm>

On Oct 21, 2010, at 3:58 AM, Arnaud Quette wrote:
> upgrading NUT is not enough: you also have to stop the old instances  
> and start new ones that use the newly installed version.
> this remark comes from the fact the PID above (16588) is the same  
> than the previous "faulty" one.
Mark,

you might want to report this as a bug to the CentOS or RedHat folks -  
ideally, a restart of NUT should kill all of the running drivers as  
well as upsd and upsmon. (The start/stop scripts are specific to each  
distribution, and are not maintained by the NUT team.)

-- 
Charles Lepple