Our server has 2 UPS on 2 PSUs. At 8am, someone unplugged one UPS. At 8:10, they plugged it back in, but turned off the load - presumably to stop the beeping. So the system is still up on 1 PSU, and can talk to both UPS. Can't I turn on the load via USB? upsc output for the UPS that is off: battery.charge: 100 battery.charge.low: 15 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2012/02/18 battery.runtime: 20880 battery.runtime.low: 300 battery.type: PbAc battery.voltage: 22.0 battery.voltage.nominal: 24.0 device.mfr: American Power Conversion device.model: Back-UPS NS 1250G device.serial: 4B1207P41794 device.type: ups driver.flag.ignorelb: enabled driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.serial: 4B1207P41794 driver.parameter.vendorid: 051d driver.version: 2.6.5 driver.version.data: APC HID 0.95 driver.version.internal: 0.37 input.sensitivity: medium input.transfer.high: 139 input.transfer.low: 88 input.voltage: 118.0 input.voltage.nominal: 120 ups.beeper.status: disabled ups.delay.shutdown: 20 ups.firmware: 867.L6 .D ups.firmware.aux: L6 ups.load: 0 ups.mfr: American Power Conversion ups.mfr.date: 2012/02/18 ups.model: Back-UPS NS 1250G ups.productid: 0002 ups.realpower.nominal: 750 ups.serial: 4B1207P41794 ups.status: OL OFF ups.test.result: No test initiated ups.timer.reboot: 0 ups.timer.shutdown: -1 ups.vendorid: 051d -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20190101/4df7331e/attachment.html>
On Tue, 1 Jan 2019, Stuart D. Gathman wrote:> Our server has 2 UPS on 2 PSUs. At 8am, someone unplugged one UPS. At > 8:10, they plugged it back in, but turned off the load - presumably to stop > the beeping. > So the system is still up on 1 PSU, and can talk to both UPS. Can't I turn > on the load via USB?None of the supported commands seem to do the job. # upscmd -l aixapc Instant commands supported on UPS [aixapc]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper beeper.off - Obsolete (use beeper.disable or beeper.mute) beeper.on - Obsolete (use beeper.enable) load.off - Turn off the load immediately load.off.delay - Turn off the load with a delay (seconds) shutdown.reboot - Shut down the load briefly while rebooting the UPS shutdown.stop - Stop a shutdown in progress test.battery.start.deep - Start a deep battery test test.battery.start.quick - Start a quick battery test test.battery.stop - Stop the battery test test.panel.start - Start testing the UPS panel test.panel.stop - Stop a UPS panel test -- Stuart D. Gathman <stuart at gathman.org> "Confutatis maledictis, flamis acribus addictis" - background song for a Microsoft sponsored "Where do you want to go from here?" commercial.
On Jan 1, 2019, at 7:06 PM, Stuart D. Gathman wrote:> > On Tue, 1 Jan 2019, Stuart D. Gathman wrote: > >> Our server has 2 UPS on 2 PSUs. At 8am, someone unplugged one UPS. At >> 8:10, they plugged it back in, but turned off the load - presumably to stop >> the beeping. >> So the system is still up on 1 PSU, and can talk to both UPS. Can't I turn >> on the load via USB? > > None of the supported commands seem to do the job. > > # upscmd -l aixapc > Instant commands supported on UPS [aixapc]: > > beeper.disable - Disable the UPS beeper > beeper.enable - Enable the UPS beeper > beeper.mute - Temporarily mute the UPS beeper > beeper.off - Obsolete (use beeper.disable or beeper.mute) > beeper.on - Obsolete (use beeper.enable) > load.off - Turn off the load immediately > load.off.delay - Turn off the load with a delay (seconds) > shutdown.reboot - Shut down the load briefly while rebooting the UPSHi Stuart, I still haven't had a chance to make sense of all the logs from related reports, but there are at least two possibilities here: 1) NUT is missing a step (or bailing early) for multi-step commands like shutdowns. I would think that shutdown.reboot should work, though I have not tried it from a load-off state. 2) This may be one of the Modbus/Multilink devices, where the HID PDC interface (that usbhid-ups uses) is a subset of the full command set. Yours does show ups.load, but none of the output voltages. I can take a look at the debug logs if you want, though given the lack of progress on similar cases, I'm not optimistic that there is a simple fix. It's the usual thing of stopping the NUT services, starting the driver with "-DDD", and redirecting output to a log file. In your case, you can probably stop it after 5-10 seconds, since the command dump happens early (and we're not concerned about the polling loop). Given that we don't have a Back-UPS NS in the compatibility list, and that you have two of the three categories of information on the list already, would you mind if we added this to the DDL? The output of upsrw would be useful for completeness. Also, if you know any of the values from upsc are incorrect, we can note that. For instance, I'm assuming that "battery.date" is incorrect, and the real dates are under "battery.mfr.date" and "ups.mfr.date". Other reports: http://new.networkupstools.org/ddl/APC/