Hello, is there a way to query from the cmdline if the UPS data is stale?
"upsc" outputs a lot of information, but not if the data is stale. Example output from a "stale" UPS on the server: (nut version: nut-2.7.2-3.el7) # upsc apcsmart battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.mfr.date: 2014/09/01 battery.runtime: 1320 battery.runtime.low: 300 battery.temperature: 36.0 battery.type: PbAc battery.voltage: 25.7 battery.voltage.nominal: 24.0 device.mfr: American Power Conversion device.model: Smart-UPS 1500 device.serial: ASXXXXXXXXXX device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.7.2 driver.version.data: APC HID 0.95 driver.version.internal: 0.38 input.sensitivity: high input.transfer.high: 253 input.transfer.low: 208 input.transfer.reason: input voltage out of range input.voltage: 233.2 output.frequency: 50.0 output.voltage: 233.2 output.voltage.nominal: 230.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.firmware: 601.1.I ups.firmware.aux: 1.3 ups.load: 38.3 ups.mfr: American Power Conversion ups.mfr.date: 2002/02/05 ups.model: Smart-UPS 1500 ups.productid: 0002 ups.serial: ASXXXXXXXXXX ups.status: OL ups.test.result: No test initiated ups.timer.reboot: -1 ups.timer.shutdown: -1 ups.timer.start: -1 ups.vendorid: 051d If there's a way to query this from the cmdline, this could be monitored from an external system. The information seems to be part of the network protocol already, since "client" machines connected to this UPS server reported the data is stale in the logs. That's how I noticed it in the first place :) Thanks, Thomas _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
