Nut upsdev - Apr 2010 - Syslog flooding

Hello,

I have a TrippLite SU2200XLA UPS with a possibly unreliable USB interface
running on NUT 2.4.3. This flooded syslog last night, beginning with the USB
connection spontaneously reconnecting:

Apr 18 22:00:42 kernel: hiddev96: USB HID v1.11 Device [Tripp Lite       TRIPP
LITE UPS  ] on usb-0000:00:0f.2-2
Apr 18 22:00:44 usbhid-ups[486]: Got disconnected by another driver: Device or
resource busy
Apr 18 22:00:46 usbhid-ups[486]: Got disconnected by another driver: Device or
resource busy
Apr 18 22:00:48 usbhid-ups[486]: Got disconnected by another driver: Device or
resource busy

/* repeats every two seconds */ 

Apr 18 22:34:33 usbhid-ups[486]: Got disconnected by another driver: Device or
resource busy
Apr 18 22:34:35 upsd[490]: Data for UPS [upsserv7] is stale - check driver
Apr 18 22:34:40 upsmon[495]: Poll UPS [upsserv7 at localhost] failed - Data
stale
Apr 18 22:34:40 upsmon[495]: INFO UPS upsserv7 at localhost communications lost
Apr 18 22:34:45 upsmon[495]: Poll UPS [upsserv7 at localhost] failed - Data
stale
Apr 18 22:34:50 upsmon[495]: Poll UPS [upsserv7 at localhost] failed - Data
stale
Apr 18 22:34:55 upsmon[495]: Poll UPS [upsserv7 at localhost] failed - Data
stale

/* repeats every five seconds */

Apr 18 22:39:35 upsmon[495]: INFO UPS upsserv7 at localhost is unavailable
(can't be contacted for monitoring)

/* continues repeating every five seconds */

Apr 19 08:13:02 upsmon[495]: Poll UPS [upsserv7 at localhost] failed - Data
stale
Apr 19 08:13:02 upsmon[495]: Signal 15: exiting
Apr 19 08:13:02 upsd[490]: User upsmon at 127.0.0.1 logged out from UPS
[upsserv7]
Apr 19 08:13:02 upsd[490]: User upsmon at 127.0.0.1 logged out from UPS
[upsserv8]
Apr 19 08:13:03 upsd[490]: mainloop: Interrupted system call
Apr 19 08:13:03 upsd[490]: Signal 15: exiting
Apr 19 08:13:03 usbhid-ups[486]: Signal 15: exiting
Apr 19 08:13:03 usbhid-ups[477]: Signal 15: exiting

When I restart NUT, everything is OK until the next spontaneous reconnection.
Two questions:

1. If I can reset the connection by restarting the driver, is there a way to
make the driver do this itself?

2. If not, is there a way to suppress or limit the syslog messages, other than
a syslog filter?

Note that I have three other UPSs of the same type which do not exhibit this
behavior.

Thanks,
Kelvin

On Mon, Apr 19, 2010 at 4:22 PM, Kelvin Ku
<kelvin at telemetry-investments.com> wrote:
> Hello,
>
> I have a TrippLite SU2200XLA UPS with a possibly unreliable USB interface
> running on NUT 2.4.3. This flooded syslog last night, beginning with the
USB
> connection spontaneously reconnecting:
>
> Apr 18 22:00:42 kernel: hiddev96: USB HID v1.11 Device [Tripp Lite ? ? ?
TRIPP LITE UPS ?] on usb-0000:00:0f.2-2
> Apr 18 22:00:44 usbhid-ups[486]: Got disconnected by another driver: Device
or resource busy
> Apr 18 22:00:46 usbhid-ups[486]: Got disconnected by another driver: Device
or resource busy
> Apr 18 22:00:48 usbhid-ups[486]: Got disconnected by another driver: Device
or resource busy
Rather than restarting the driver, you probably want to start by
figuring out what else is claiming the driver. You can only have one
program talking HID to a USB device* at a time. Do you have any other
power management software on your system which might try to grab this
device?

* technically, one per interface, but most UPSes have one HID interface.

-- 
- Charles Lepple

Citeren Kelvin Ku <kelvin op telemetry-investments.com>:
> When I restart NUT, everything is OK until the next spontaneous  
> reconnection. Two questions:
>
> 1. If I can reset the connection by restarting the driver, is there a way
to
> make the driver do this itself?
>
> 2. If not, is there a way to suppress or limit the syslog messages,  
> other than
> a syslog filter?
>
> Note that I have three other UPSs of the same type which do not exhibit
this
> behavior.
If you're monitoring two (or more) UPSes from the same host system,  
make sure they can be uniquely identified by the regular expressions  
you specified in 'ups.conf'. The situation you're describing is  
typical for an installation where this is not done properly (see also  
'man 8 usbhid-ups'). The regular expressions are *mandatory* as soon  
as you connect multiple UPS devices to a single host.

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

Citeren Sean Conner <sean op conman.org>:
>> If you're monitoring two (or more) UPSes from the same host system,
>> make sure they can be uniquely identified by the regular expressions
>> you specified in 'ups.conf'. The situation you're
describing is
>> typical for an installation where this is not done properly (see also
>> 'man 8 usbhid-ups'). The regular expressions are *mandatory* as
soon
>> as you connect multiple UPS devices to a single host.
>
>   Can you give an example?  Or does this only apply if the UPSes are of the
> same make and model?  For instance, here's my ups.conf file:
>
> [apc1000]
>         driver = usbhid-ups
>         port = auto
>         desc = "APC Back-UPS XS 1000"
>         vendorid = 051D
>
> [cp1000]
>         driver = usbhid-ups
>         port = auto
>         desc = "CyberPower 1000AVR"
>         vendorid = 0764
Both devices have a different 'vendorid', which is one of the regular  
expressions (see 'man 8 usbhid-ups') we use for device matching. This  
makes them uniquely identifiable. If you add another APC and/or  
CyberPower device, you'll have to add additional regular expressions  
since the 'vendorid' alone will usually be the same for devices from  
the same vendor.

Best regards, Arjen

PS  Please honor the line below. Unless a consultation fee is  
involved, I won't reply to messages sent to me in private.
-- 
Please keep list traffic on the list