<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Clayton,<br>
    <br>
    the failover time is steered by the time_reopen() global option (60
    sec by default), so setting it to a much lower value should do the
    trick.<br>
    <br>
    From the admin guide:<br>
    "To list several failover servers, separate the address of the
    servers with comma. The time syslog-ng PE waits for the a server
    before switching to the next failover server is set in the <em
      class="parameter"><code>time_reopen()</code></em> option. For
    details about how client-side failover works, see <a class="xref"
href="http://www.balabit.com/sites/default/files/documents/syslog-ng-pe-v4.0-guide-admin-en.html/index.html-single.html#concepts_failover"
      title="2.15.&nbsp;Client-side failover">Section 2.15, Client-side
      failover</a>."<br>
    <br>
<a class="moz-txt-link-freetext" href="http://www.balabit.com/sites/default/files/documents/syslog-ng-pe-v4.0-guide-admin-en.html/index.html-single.html#example-failover-server-tcp">http://www.balabit.com/sites/default/files/documents/syslog-ng-pe-v4.0-guide-admin-en.html/index.html-single.html#example-failover-server-tcp</a><br>
    <br>
    I assume that the TCP connection breakdown is detected by syslog-ng
    in a timely manner, pls correct me if I misunderstood the problem.<br>
    <br>
    Balint<br>
    <br>
    On 10/04/2011 12:18 PM, Clayton Dukes wrote:
    <blockquote
cite="mid:CAANP6QcEFZPtKSw2viAVSx_1otUQ0b8jYxA33O6XOwPZrSQXqQ@mail.gmail.com"
      type="cite">Hi Folks,
      <div>We have a team doing testing on the PE edition and they are
        finding that the timeout for the failover trigger takes 60
        seconds:</div>
      <div><br>
      </div>
      <div>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">It
            was observed that it takes anytime between 10 to 60 seconds
            to detect connection is broken. We found out it by running
            syslog-ng in debug
            mode. I guess it relies on connection timeout. This 60
            second is large interval
            compared to the default interval that we have (15 sec).</span></p>
      </div>
      <div><br>
      </div>
      <div>My question: Is there a way to tune this parameter down to 15
        seconds in the config?</div>
      <div><br clear="all">
        ______________________________________________________________ <br>
        <br>
        Clayton Dukes<br>
        ______________________________________________________________<br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">______________________________________________________________________________
Member info: <a class="moz-txt-link-freetext" href="https://lists.balabit.hu/mailman/listinfo/syslog-ng">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a>
Documentation: <a class="moz-txt-link-freetext" href="http://www.balabit.com/support/documentation/?product=syslog-ng">http://www.balabit.com/support/documentation/?product=syslog-ng</a>
FAQ: <a class="moz-txt-link-freetext" href="http://www.balabit.com/wiki/syslog-ng-faq">http://www.balabit.com/wiki/syslog-ng-faq</a>

</pre>
    </blockquote>
  </body>
</html>