Nut upsuser - Mar 2009 - Nut-upsuser Digest, Vol 45, Issue 13

---> On 15/03/2009 8:00 AM, nut-upsuser-request at lists.alioth.debian.org 
wrote:
> Message: 1
> Date: Sat, 14 Mar 2009 21:47:08 +0100
> From: Arjen de Korte <nut+users at de-korte.org>
> Subject: Re: [Nut-upsuser] Weird Load and Battery Temp Readings
> To: nut-upsuser at lists.alioth.debian.org
> Message-ID: <20090314214708.37122w00w79l6u9s at mail.de-korte.org>
> Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";
> 	format="flowed"
>
> Citeren Bob Blackwell <rc.blackwell at yahoo.ca>:
>
> [...]
>   
>> The systems message.log contains several lines with;
>>
>> Mar 13 19:16:20 DNS323_NAS user.warn kernel: usb 1-1.2: usbfs: process
>> 26398 (usbhid-ups) did not claim interface 0 before use
>>     
>
> This usually means that more than one driver is active for the same  
> USB device and/or hotplug/udev isn?t setup properly. It could  
> occasionally happen if the connection is lost as well.
>
>   
 From what I can tell three's only one active driver. PS shows;

PID   USER     COMMAND
 2045 root     /ffp/bin/usbhid-ups -a APC_UPS
 2047 root     /ffp/sbin/upsd
 2049 root     /ffp/sbin/upsmon -u monuser
 2050 nutmon   /ffp/sbin/upsmon -u monuser

 Running  usbhid-ups -u root -DDDDD -a APC_UPS>debug.log 2>&1 never 
stops without a ^C. The log shows many disconnect and re-connect 
attempts. I'm rather green at Linux thus it'll likely take me a couple 
of days to determine if there's a hotplug/udev issue. Until then I'll 
refrain from posting debug's output.

With appreciation

Bob Blackwell

Citeren Bob Blackwell <rc.blackwell op yahoo.ca>:
>  From what I can tell three's only one active driver. PS shows;
>
> PID   USER     COMMAND
>  2045 root     /ffp/bin/usbhid-ups -a APC_UPS
>  2047 root     /ffp/sbin/upsd
>  2049 root     /ffp/sbin/upsmon -u monuser
>  2050 nutmon   /ffp/sbin/upsmon -u monuser
Could it be that you're running virtualization software and that  
you're running NUT on one of the slaves?
>  Running  usbhid-ups -u root -DDDDD -a APC_UPS>debug.log 2>&1
never
> stops without a ^C. The log shows many disconnect and re-connect
> attempts.
Usually this either means that your USB system isn't setup properly  
(or you're in a really 'noisy' environment) or that some other
process
is also attempting to claim the same USB device. This will lead to an  
endless mess of reconnection attempts for both drivers. USB doesn't  
really handle this well if you don't use the kernel (HAL) to startup  
drivers, but instead talk to them directly like we do. We do have HAL  
addons that would not suffer from this, but these usually are only  
worth using if you have a graphical desktop.
> I'm rather green at Linux thus it'll likely take me a couple
> of days to determine if there's a hotplug/udev issue. Until then
I'll
> refrain from posting debug's output.
It looks like this might be caused by an (unexpected) use of signed  
chars on your system. The HID parser really doesn't cope with that  
properly in nut-2.4.1 and before. I have attempted to work around that  
in the latest version in the SVN trunk. I could be that the problem  
with the strange readings, is that the logic used to calculate the  
exponent is off by a factor of 10^256 due to problems with the  
interpretation of (signed char) values as (unsigned char) on your  
system.

If you post debug output, make sure to include the report descriptor,  
which would be the most valueable part, together with the initial dump  
of the variables.

Best regards, Arjen
-- 
Please keep list traffic on the list