On 1/18/2007 9:36 PM, Charles Lepple wrote: > On 1/18/07, Eric A. Hall <[EMAIL PROTECTED]> 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...
> Some of the SMARTPRO models seem to work right off the bat, but there > have been reports of timeouts. It's a SMART2200RMXL2U (man I hate typing that out). I run KNut on the server's gnome console, which complains whenever the signal is lost, and it hasn't complained except when I break nut. > Can you post the output of 'upsc' for that UPS? There are some debug > strings in there that will help track this down. [ 21:40:42 -- bulldog:/root/ ] [ root# ] upsc [EMAIL PROTECTED] battery.voltage: 13.60 battery.voltage.nominal: 12 driver.name: tripplite_usb driver.parameter.port: auto driver.version: 2.0.4 driver.version.internal: 0.6 input.voltage: 119 input.voltage.nominal: 120 ups.debug.D: 37 37 38 38 0d 00 00 '7788...' ups.debug.M: 30 30 37 44 0d 00 00 '007D...' ups.debug.S: 31 30 30 00 64 30 0d '100.d0.' ups.debug.T: 39 45 32 35 37 31 0d '9E2571.' ups.delay.shutdown: 64 ups.firmware: F1115.B ups.load: 19 ups.mfr: Tripp Lite ups.model: SMART2200RMXL2U ups.power.nominal: 2200 ups.status: OL Thanks -- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/ _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
