<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">IMHO The best way to have redundant
logging it to log to multiple syslog servers from each source
server. For devices that can only log to one device I would log to
a dedicated log replicator that send a copy of the log event to
the multiple syslog servers just as if the client could have sent
to multiple syslog server on its own.<br>
<br>
Evan. <br>
<br>
On 08/11/2016 03:07 PM, Lupo, Joseph wrote:<br>
</div>
<blockquote
cite="mid:AEF18B86-D0E8-4500-BC32-CB96E633916A@t-mobile.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<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:12.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:Calibri;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">I am trying
to setup Syslog-ng to relay messages from one syslog server
to another with a load balancer in between. I am also using
TLS encryption. The issue I’m having right now is that when
the client intiates the connection, it seems to lock on to a
particular back end syslog server and send all of its
messages there instead of switching off to another one. On
its own this isn’t a big problem except that if that system
goes down, the client doesn’t seem to be aware. I also
haven’t found a good way to force syslog-ng to close and
re-establish its connections without fully shutting down the
relay system. We currently have no persistence setup on
the load balancer.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Is there a
way to tell the relay server to periodically reconnect?
Maybe send a certain amount of messages or data before
reconnecting so that the data is balanced across the backend
syslog-ng servers? Also, is there a better way to have the
relay system learn about the remote server going offline so
it can immediately reset its connection?<o:p></o:p></span></p>
</div>
</blockquote>
<br>
</body>
</html>