*That* command would shut it down, same as `upsdrvctl shutdown` but with a better chance to debug what actually happens in the dialog.
Actually with NUT v2.8.2 you can also request debug of drivers via `upsdrvctl -d -DDDDDD shutdown ups_bottom` or some such (`-d` tells it to pass debug flags to driver programs it launches). Jim On Tue, Dec 17, 2024 at 9:35 PM Lee Damon <[email protected]> wrote: > Will that shut the UPS down or just set up the driver to allow it? > > nomad > > On Tue, Dec 17, 2024 at 11:59 AM Jim Klimov <[email protected]> > wrote: > >> Also, is the write-capable community set in the config (and enabled on >> SNMP UPS side)? With SNMP (over UDP at least) it is hard to tell by lack of >> reply if the device/service is missing or unwilling (e. g. bad auth). >> Possibly the socket error >> ZjQcmQRYFpfptBannerStart >> ... >> Try starting the driver command with debug, e.g. >> >> snmp-ups -a ups-bottom -DDDDDD -k >> >> (-k is for shutdown/killpower). >> >>
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
