<html><head></head><body>Looks like you did - "OL" is shorthand for "On Line"<br>
<br>
- Tim<br><br><div class="gmail_quote">On December 3, 2016 11:31:46 AM CST, Jack McGee <jack@greendesk.net> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 12/03/2016 10:55 AM, Jack McGee wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> On 12/03/2016 10:35 AM, Charles Lepple wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> On Dec 3, 2016, at 11:16 AM, Jack McGee <jack@greendesk.net> wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"> Dec 3 08:38:16 amethi upsd[18234]: not listening on ::1 port 3493<br /> Dec 3 08:38:16 amethi upsd[18234]: listening on <a href="http://127.0.0.1">127.0.0.1</a> port 3493<br /> Dec 3 08:38:16 amethi upsd[18234]: no listening interface available<br /></blockquote> I can't say I fully understand the logic behind the IPv6 code, but <br /> the first line indicates a problem binding to the IPv6 localhost <br /> address. The "LISTEN <a
href="http://127.0.0.1">127.0.0.1</a> 3493" line in upsd.conf is sufficient <br /> for local control and monitoring, and you can remove "LISTEN ::1 3493".<br /></blockquote><br /> OK, did that restarted services and:<br /><br /> mythuser@amethi:/etc/nut$ upscmd -l CyberUPS1<br /> Instant commands supported on UPS [CyberUPS1]:<br /><br /> beeper.disable - Disable the UPS beeper<br /> beeper.enable - Enable the UPS beeper<br /> beeper.mute - Temporarily mute the UPS beeper<br /> beeper.off - Obsolete (use beeper.disable or beeper.mute)<br /> beeper.on - Obsolete (use beeper.enable)<br /> load.off - Turn off the load immediately<br /> load.off.delay - Turn off the load with a delay (seconds)<br /> load.on - Turn on the load immediately<br /> load.on.delay - Turn on the load with a delay (seconds)<br /> shutdown.return - Turn off the load and return when power is back<br /> shutdown.stayoff - Turn off the load and remain off<br /> shutdown.stop - Stop a shutdown in progress<br />
test.battery.start.deep - Start a deep battery test<br /> test.battery.start.quick - Start a quick battery test<br /> test.battery.stop - Stop the battery test<br /><br /> so this is progress. Thanks! Anything else to check to know it is <br /> working as it should?<br /><br /> My next step will be to point NUT client on another machine to this <br /> one. They are both plugged into this UPS. <br /></blockquote><br />Maybe still a problem:<br /><br />mythuser@amethi:/etc/nut$ sudo upsc CyberUPS1@localhost ups.status<br />[sudo] password for mythuser:<br />Init SSL without certificate database<br />OL<br /><br />But if I read this<br /><a href="https://askubuntu.com/questions/468632/nut-ups-and-ssl-certificates#565740">https://askubuntu.com/questions/468632/nut-ups-and-ssl-certificates#565740</a><br />correctly, it is just a warning?<br />But shouldn't I see a status?<br /><br /><br /><br /><hr /><br />Nut-upsuser mailing list<br />Nut-upsuser@lists.alioth.debian.org<br /><a
href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser</a><br /></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>