[syslog-ng]TCP reliability
Chris Sibbitt
CSibbitt@jetnet.ca
Mon, 14 May 2001 16:45:47 -0400
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C0DCB6.DAA5C730
Content-Type: text/plain;
charset="iso-8859-1"
Greetings. I'm running syslog-ng 1.4.11 and am having trouble getting the
tcp destination to work reliably. My major concern is with what happens when
the receiving end of the tcp link is reset. In my scenario I have one
syslog-ng machine forwarding messages to another syslog-ng machine using a
tcp() destination on one end and a tcp() source on the other. All works fine
until I interrupt the socket on the receiving machine. Rebooting, HUP'ing
syslog-ng, etc all cause the logs to stop coming in. I assume that the
sender is simply trying to write the messages to an existing TCP socket and
failing. What happens to these messages (are they queued anywhere for later
delivery?), and is there anything that I can do to ensure that messages
continue to flow when the receiver comes back up? Losing messages while the
receiving end if offline is an acceptable loss, but when it comes back up, I
would really like it to continue to receive. In the current scenario I have
to restart every syslog-ng machine that is forwarding messages to my central
logger when I change its configuration, this is definitely not sane.
Anyone with hints/tips for setting up TCP based messaging, please contact
me.
Chris Sibbitt
JetNet Internetworking Services Inc.
Providing Secure Internet Communications
Phone 613-271-6220x228
FAX 613-271-6229
Email csibbitt@jetnet.ca
Web www.jetnet.ca <http://www.jetnet.ca/>
------_=_NextPart_001_01C0DCB6.DAA5C730
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=256204020-14052001> Greetings. I'm
running syslog-ng 1.4.11 and am having trouble getting the tcp destination to
work reliably. My major concern is with what happens when the receiving end of
the tcp link is reset. In my scenario I have one syslog-ng machine forwarding
messages to another syslog-ng machine using a tcp() destination on one end and a
tcp() source on the other. All works fine until I interrupt the socket on the
receiving machine. Rebooting, HUP'ing syslog-ng, etc all cause the logs to stop
coming in. I assume that the sender is simply trying to write the messages to an
existing TCP socket and failing. What happens to these messages (are they queued
anywhere for later delivery?), and is there anything that I can do to ensure
that messages continue to flow when the receiver comes back up? Losing messages
while the receiving end if offline is an acceptable loss, but when it comes back
up, I would really like it to continue to receive. In the current scenario I
have to restart every syslog-ng machine that is forwarding messages to my
central logger when I change its configuration, this is definitely not
sane.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=256204020-14052001></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=256204020-14052001> Anyone with
hints/tips for setting up TCP based messaging, please contact
me.</SPAN></FONT></DIV>
<P><FONT face=Arial size=2>Chris Sibbitt</FONT> <BR><FONT face=Arial
size=2>JetNet Internetworking Services Inc.</FONT> </P>
<P><FONT face=Arial size=2>Providing Secure Internet Communications</FONT>
<BR><FONT face=Arial size=2> </FONT> <BR><FONT face=Arial size=2>Phone
613-271-6220x228</FONT> <BR><FONT face=Arial size=2>FAX
613-271-6229</FONT> <BR><FONT face=Arial
size=2>Email csibbitt@jetnet.ca</FONT> <BR><FONT face=Arial
size=2>Web <A
href="http://www.jetnet.ca/">www.jetnet.ca</A></FONT></P>
<DIV> </DIV></BODY></HTML>
------_=_NextPart_001_01C0DCB6.DAA5C730--