<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="auto">
<div>Thank you Roger, I appreciate the response. I'll have to check my commands, I believe I started it with those systemctl commands you provided. What I can say is that oddly enough after completing the server config and after two more reboots a reboot of
the Pi doesn't seem to be causing the UPS to reboot anymore. I have a bit more config to do on slave machines tomorrow but after that I'll do testing - including pulling the plug - and see what happens. </div>
<div dir="auto"><br>
</div>
<div dir="auto">I do recall from reading the documentation that the master can initiate a reboot of the UPS and that in a shutdown event I believe it's supposed to do actually trigger a delayed shutdown to occur after the master's own power-off. How that gets
mixed up with an OS reboot is odd to me...perhaps something scripted in relation to the NUT service stopping? </div>
<div dir="auto"><br>
</div>
<div dir="auto">Google searching did by the way yield one and only one other mention of something like what I experienced: https://serverfault.com/questions/858267/network-ups-tools-nut-causing-ups-to-reboot. So at least I'm not completely nuts, just partially. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Thanks again for your help. </div>
<div dir="auto">-James <br>
<div class="gmail_extra" dir="auto"><br>
<div class="gmail_quote">On Aug 15, 2020 10:44 PM, Roger Price <roger@rogerprice.org> wrote:<br type="attribution">
<blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><font size="2"><span style="font-size:11pt">
<div>On Sat, 15 Aug 2020, James Fischl wrote:<br>
<br>
> OS: Raspbian Lite 4.19 (Linux 5.4.51-v7l+ armv7l)NUT version: 2.7.4<br>
> Install Method: Package (apt-get)<br>
> Device Name: CyberPower CP1500PFCLCD, connected via USB<br>
> Problem: This is a brand-new installation; the only step I've taken is my initial edit of /etc/nut/ups.conf (which I'll post below). I started the driver<br>
> and after doing so issued a reboot command to my Raspberry Pi (sudo reboot). After doing so my UPS rebooted itself, quite a problem given all the other<br>
> equipment connected to it. How do I prevent that from happening?<br>
<br>
The usual way of starting NUT is<br>
<br>
systemctl start nut-server.service<br>
systemctl start nut-monitor.service<br>
<br>
The driver will be started automatically by upsd (nut-server). What happens if <br>
you start that way?<br>
<br>
what happens when you pull the wall power?<br>
<br>
Roger</div>
</span></font></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</body>
</html>