On Tue, Feb 14, 2012 at 11:53 AM, Matt Schulte <[email protected]> wrote: > On Tue, Feb 14, 2012 at 7:10 AM, Charles Lepple <[email protected]> wrote: >> On Feb 14, 2012, at 3:42 AM, Arnaud Quette wrote: >> >>>> shutdown sequence testing results: >>>> Not sure exactly what you would like to see here, but after >>>> configuring everything and pulling the plug the system shut down >>>> correctly when the UPS dropped below 20%. >>> >>> we just need a confirmation as you did, plus the fact that the UPS was >>> powered off in the end. >> >> Not critical, but did the UPS power on automatically after you plugged it >> back in, or did you have to press the power button manually? > > I might have just powered back up if I had given it more time, but I > was sort of anxious to get my server back up. I plugged the UPS back > in, then reached over and turned on the server. It didn't like that > and dropped power to the server. Then I pressed the power button to > turn it off and then on again, then was able to power up my server > again. > >> >>>> /etc/log/daemon.log: >>>> Feb 13 10:11:47 backup upsmon[12058]: UPS tripplite@localhost battery is >>>> low >>>> Feb 13 10:11:47 backup upsd[11649]: Client [email protected] set FSD on UPS >>>> [trip >>>> plite] >>>> Feb 13 10:11:47 backup upsmon[12058]: Executing automatic power-fail >>>> shutdown >>>> Feb 13 10:11:47 backup upsmon[12058]: Auto logout and shutdown proceeding >>>> >>>> link: >>>> http://www.tripplite.com/en/products/model.cfm?txtModelID=21 >> >> Tripp Lite tends to reuse marketing names for products even when the inner >> workings have changed. That web page describes how the UPS works with the >> auto-shutdown code in Windows and OS X, but I don't think that applies to >> UPSes which work with the tripplite_usb driver (that would be more in line >> with usbhid-ups). Approximately when was this UPS manufactured? >> > It was purchased in 2004 so I would guess sometime around then. > >>> thanks for your report. >>> I've just added an entry to the HCL. >>> For the sake of completion, could you please also send upsrw and upscmd >>> outputs? >> >> Agreed, this would be good for verification. >> > Did the outputs that I sent just before this email have what you need? > >>> I leave up to Charles, the driver author, to ask more info for >>> potential driver improvement. >> >> At this point, I am not actively working on this driver, so any improvements >> would be contingent on your availability to test new code (and tolerating >> the potential downtime that would go with that testing). Also, I don't have >> a system with PowerAlert. >> > I am game for testing if you have anything you want to do. I just may > take a day or two to wait for an off peak time. I also do not have a > system with PowerAlert. > > Matt Schulte
I have a question for you guys, today after the UPS has come back to a full charge I get a red light on the front of the UPS and I get this from upsc: matt@backup:~$ upsc tripplite battery.charge: 100 battery.test.status: Battery bad - replace battery.voltage: 14.56 battery.voltage.nominal: 12 device.mfr: Tripp Lite device.model: OMNISMART500 device.type: ups driver.name: tripplite_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.internal: 0.20 input.voltage: 109.23 input.voltage.nominal: 120 output.voltage: 113.5 ups.debug.load_banks: 0 ups.debug.V: 31 30 32 30 58 58 0d '1020XX.' ups.delay.shutdown: 64 ups.firmware: F0966.A ups.firmware.aux: protocol 2001 ups.mfr: Tripp Lite ups.model: OMNISMART500 ups.power.nominal: 500 ups.productid: 0001 ups.status: OL ups.vendorid: 09ae Why does it say "battery.test.status: Battery bad - replace?" _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
