Nut upsdev - Jan 2007 - tripplite_usb interrupt errs

I keep getting this kind of stuff in /var/log/messages

Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt()
returned -110 instead of 8

Should I be worried about it? upsc seems to work fine...

I tried building the 2.0.5 but none of the included spec files seemed to
work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem to
work out well either. Building from source made a mess on install (had to
restore from backup to clean it up), so... going to wait a bit on that.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/

On 1/18/07, Eric A. Hall <ehall@ehsco.com> wrote:
>
> I keep getting this kind of stuff in /var/log/messages
>
> Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt()
> returned -110 instead of 8
>
> Should I be worried about it? upsc seems to work fine...
It depends on the UPS model.

OMNIVS1000 units actually need to be polled several times with a short
timeout because of the odd way that their USB-to-serial system works.

Some of the SMARTPRO models seem to work right off the bat, but there
have been reports of timeouts.

Can you post the output of 'upsc' for that UPS? There are some debug
strings in there that will help track this down.
> I tried building the 2.0.5 but none of the included spec files seemed to
> work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem
to
> work out well either. Building from source made a mess on install (had to
> restore from backup to clean it up), so... going to wait a bit on that.
If you are worried about making a mess on install, just build with
'./configure --prefix=$HOME/nut' or something similar.

Also, feel free to post the errors from the RPM build system, and we
can take a look. No promises, because I haven't heard of many people
using opensuse, but it can't hurt to ask on the nut-upsdev list.

-- 
- Charles Lepple

2007/1/19, Charles Lepple <clepple@gmail.com>:
> On 1/18/07, Eric A. Hall <ehall@ehsco.com> wrote:
> >
> > On 1/18/2007 9:59 PM, Charles Lepple wrote:
> >
> > > All in all, the tripplite_usb driver for 2.0.5 should be all
benefits
> > > and no drawbacks, mostly due to some testing on several different
> > > SMARTPRO 2U models (knock on wood).
> >
> > Can I replace the driver without replacing the whole kit?
> >
> > Compiling is no problem, it's the mess afterwards...
>
> I think there was a change in some of the driver-to-upsd socket
> communication between 2.0.4 and 2.0.5, but it may only affect
> newhidups.
>
> Arnaud, do you remember when that change happened?
Sun Nov 06 20:14:10 UTC 2005 / Arnaud Quette <aquette.dev@gmail.com>

 - the state socket, used for the communication between the drivers
   and upsd, are now named using the upsname, as defined between brackets
   in ups.conf, by default. The same applies to drivers .pid file, now
   named using drivername-upsname. The old naming behavior is kept for
   debug purpose, allowing to start drivers only by specifying a port name.

so post 2.0.4.
This affect all drivers and upsd. So a full update of your installed
tree is required, along with a driver start with "-a upsname"

Arnaud
-- 
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/

On 1/18/07, Eric A. Hall <ehall@ehsco.com> wrote:
>
> On 1/18/2007 9:59 PM, Charles Lepple wrote:
>
> > All in all, the tripplite_usb driver for 2.0.5 should be all benefits
> > and no drawbacks, mostly due to some testing on several different
> > SMARTPRO 2U models (knock on wood).
>
> Can I replace the driver without replacing the whole kit?
>
> Compiling is no problem, it's the mess afterwards...
I think there was a change in some of the driver-to-upsd socket
communication between 2.0.4 and 2.0.5, but it may only affect
newhidups.

Arnaud, do you remember when that change happened?

-- 
- Charles Lepple