<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Thanks Charles,</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Looks like setting LISTEN to 0.0.0.0 did the trick. I use iptables so no worries on the filtering.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">
Mail</a> for Windows 10</p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="border:none;padding:0in"><b>From: </b><a href="mailto:clepple@gmail.com">Charles Lepple</a><br>
<b>Sent: </b>Sunday, October 22, 2017 8:39 AM<br>
<b>To: </b><a href="mailto:GRUNGELIZARD9@HOTMAIL.COM">Daniel Shields</a><br>
<b>Cc: </b><a href="mailto:nut-upsuser@lists.alioth.debian.org">nut-upsuser@lists.alioth.debian.org</a><br>
<b>Subject: </b>Re: [Nut-upsuser] nut-server service fails to start at boot</p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">On Oct 22, 2017, at 2:39 AM, Daniel Shields <grungelizard9@hotmail.com> wrote:<br>
> <br>
> Oct 22 05:57:37 nut.tklapp.com upsd[341]: not listening on 192.168.213.189 port 3493<br>
> Oct 22 05:57:37 nut.tklapp.com upsd[341]: not listening on 192.168.213.189 port 3493<br>
> Oct 22 05:57:37 nut.tklapp.com upsd[341]: listening on 127.0.0.1 port 3493<br>
> Oct 22 05:57:37 nut.tklapp.com upsd[341]: no listening interface available<br>
> <br>
I think you're hitting this race condition: <a href="https://github.com/networkupstools/nut/issues/393">
https://github.com/networkupstools/nut/issues/393</a><br>
<br>
Using the LISTEN directive to selectively ignore certain interfaces worked a lot better when 1) we didn't have to worry about interfaces being removed and added at runtime and 2) when NUT was guaranteed to start after all of the network interfaces were already
up.<br>
<br>
Can you just use "LISTEN 0.0.0.0"? If there is one particular interface you are excluding, can you handle that with firewall rules?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>