<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I have made changes but it is still the same. That is when the server gets the lowbat/noAC signal it does shut down as expected but the slave does not. <div><br></div><div>Perhaps it makes sense for me to list the present settings:</div><div><br></div><div><b>On the Master:</b></div><div><b><br></b></div><div><b> nut.conf</b></div><div> MODE=netserver</div><div><br></div><div><b> ups.conf</b></div><div><div> [sdrups]</div><div> driver = genericups</div><div> port = /dev/ttyS1</div><div> desc = "For Server & Backup"</div><div> upstype=9</div></div><div><br></div><div><b> upsd.conf</b></div><div> LISTEN 0.0.0.0</div><div><br></div><div><b> upsd.users</b></div><div> [root]</div><div> <span class="Apple-tab-span" style="white-space:pre"> </span> password = mypassword</div><div><span class="Apple-tab-span" style="white-space:pre"> </span> upsmon master</div><div><span class="Apple-tab-span" style="white-space:pre"> </span> instcmds = ALL</div><div><br></div><div><b> upsmon.conf</b></div><div> MONITOR root@192.168.0.7 1 sdrups autocadba2 master</div><div><br></div><div><b>On the Slave:</b></div><div><b><br></b></div><div><b> nut.conf</b></div><div><b> </b>MODE=netserver</div><div><br></div><div><b> upsmon.conf</b></div><div> MONITOR root@192.168.0.7 1 sdrups autocadba2 slave</div><div><b><br></b></div><div><b>Master: </b>192.168.0.7</div><div><b>Slave: </b>192.168.0.6</div><div><b><br></b></div><div>Dealing with the firewall I applied the following to both the master and slave:</div><div><br></div><div> <span style="font-size: 12.6666669845581px; text-align: justify; background-color: rgb(247, 249, 250);">sudo iptables -A INPUT -p tcp --dport 3493 -j ACCEPT</span></div><div><span style="font-size: 12.6666669845581px; text-align: justify; background-color: rgb(247, 249, 250);"><br></span></div><div><b><br></b></div><div>I have looked in the log files but have not seen anything to suggest a problem.</div><div><br></div><div><br></div><div>Steve</div><div><b><br></b><div><hr id="stopSpelling">Subject: Re: [Nut-upsuser] Master Works, Slave Does Not<br>From: clepple@gmail.com<br>Date: Sat, 8 Nov 2014 09:00:12 -0500<br>CC: nut-upsuser@lists.alioth.debian.org<br>To: sd_read@hotmail.com<br><br>[Please use reply-all to keep the discussion on the list, thanks]<br><br>On Nov 6, 2014, at 10:19 PM, Charles Lepple <<a href="mailto:clepple@gmail.com">clepple@gmail.com</a>> wrote:<br><br><blockquote>On Nov 6, 2014, at 12:48 PM, Steve Read <<a href="mailto:sd_read@hotmail.com">sd_read@hotmail.com</a>> wrote:<br><br><blockquote>I am presently upgrading my servers. The old ones are running Suse 10.1 and I am upgrading to the most recent Debian.<br></blockquote><br>What version of NUT on the new systems?<br><br>There are a few changes to the configuration files, mostly related to the ACL lines.<br></blockquote><br>You mentioned you got "driver.version: 2.6.4" from upsc. So it seems like you have Debian wheezy. Is that the case for both servers?<br><br>(What I was really interested in was the output of "dpkg -l nut", since it shows the Debian-specific version number as well, but wheezy hasn't changed much. There are a few things still being sorted out in Debian jessie.)<br><br><blockquote>Now this may be a problem but I don't think it is the only one. I really feel this is a permissions issue. <br><br>For example from the master, if I type:<br> root@backup2:~# sudo upsc sdrups@localhost ups.status<br> OL<br><br>Which is the response I expect, but if I type (also from the master):<br> root@backup2:~# sudo upsc <a href="mailto:sdrups@192.168.0.7">sdrups@192.168.0.7</a> ups.status<br> Error: Connection failure: Connection refused<br></blockquote><br>One thing that has changed since NUT 2.4.x is that the ACL options were removed, and the defaults for the LISTEN directive were changed to only bind to localhost. So a "netstat -ta" (trimmed to just show NUT) would look like this:<br><br><font face="Courier New">Active Internet connections (servers and established)<br>Proto Recv-Q Send-Q Local Address Foreign Address State </font><div><font face="Courier New">...<br>tcp 0 0 localhost:nut *:* LISTEN <br></font><br>Instead, you want to listen on the wildcard address, so you will want to add "LISTEN 0.0.0.0" to /etc/nut/upsd.conf. After restarting NUT, netstat should look like this:</div><div><br></div><div><font face="Courier New">Active Internet connections (servers and established)<br>Proto Recv-Q Send-Q Local Address Foreign Address State </font></div><div><font face="Courier New">...<br>tcp 0 0 *:nut *:* LISTEN <br></font><br></div><div>And at that point, you can use the firewall rules to restrict access to just localhost and your local network.</div><div><br></div><div>If you were able to get output from upsc, then it sounds like you got the driver working. Just in case, here is the UPGRADING document: <a href="https://github.com/networkupstools/nut/blob/master/UPGRADING" target="_blank">https://github.com/networkupstools/nut/blob/master/UPGRADING</a></div><div><br></div><div>Some drivers (apcsmart) have had under-the-hood changes that should be more beneficial than problematic.</div><div><br></div><div>Also, Stan mentioned the following off-list, and it holds true:</div><div><br></div><div><blockquote>upsmon.conf should have a line like this<br><br>MONITOR <a href="mailto:apcusb@192.168.1.235">apcusb@192.168.1.235</a> 1 upsmon pass slave<br><br>upsd.users should have a matching statement like this<br><br> [upsmon]<br> password = pass<br># upsmon master<br># or<br> upsmon slave<br></blockquote></div><div><br></div><div>The only configuration files that a slave needs are upsmon.conf, nut.conf to tell the init.system that it is a slave, and possibly an upssched.conf if you haven enabled that. The others are master-only.</div><div><br><div>-- <br>Charles Lepple<br>clepple@gmail<br><br><br></div><br></div></div></div> </div></body>
</html>