[Nut-upsuser] TrippLite OMNIVS1500XL Segmentation Fault

[Charles Lepple]

On 8/11/07, Junk Mail <junk at chassit.com> wrote:
> On Fri, 10 Aug 2007, Charles Lepple wrote:
>
> > On 8/10/07, Junk Mail <junk at chassit.com> wrote:
> >> The new version works, so far.
> >
> > Actually, for completeness' sake, would you mind posting the output of
> > 'upsc' for that UPS? (Just checking that things look reasonable.)
>
> Sure.
>
> # upsc tripplite at localhost
> battery.charge: 100
> battery.voltage: 14.50
> battery.voltage.nominal: 24
> driver.name: tripplite_usb
> driver.parameter.pollinterval: 2
> driver.parameter.port: hiddev0
> driver.version: 2.2.0-
> driver.version.internal: 0.11
> input.voltage: 99.33
> input.voltage.nominal: 120

input.voltage looks a little low.

> output.voltage: 114.5
> ups.debug.load_banks: 0
> ups.debug.V: 31 30 34 30 58 58 0d '1040XX.'
> ups.delay.shutdown: 64
> ups.firmware: F2211.A
> ups.firmware.aux: protocol 2001
> ups.mfr: Tripp Lite
> ups.model: UPS
> ups.power.nominal: 1500
> ups.status: OL
>
>
> Things have been working pretty well so far, but I have seen data stale
> errors in my syslog: (dates trimmed)
>
> tripplite_usb[12450]: Error reading B value: Device detached? (error 0: No error)

This piece of code is probably going overboard here - it tries to
reconnect after every error. The "error 0: No error" really means that
there was not a USB error, but somehow the message that came back was
not formatted as expected.

> upsd[12452]: Data for UPS [tripplite] is stale - check driver
> tripplite_usb[12450]: Reconnect attempt #1
> tripplite_usb[12450]: Successfully reconnected

I forget how MAXAGE works, but if you can fix this by increasing
maxage, you probably want to figure out the time difference between
the first tripplite_usb error above, and the "Sucessfully reconnected"
message.

Beyond that, debugging can get messy. It may not be worth it on these
models - they do occasionally miss sending back responses.

-- 
- Charles Lepple