<p dir="ltr"><br>
On May 6, 2013 6:53 PM, "Matt Wise" <<a href="mailto:matt@nextdoor.com">matt@nextdoor.com</a>> wrote:<br>
><br>
> We're running Syslog-NG 3.3.4 in our mixed Ubuntu 10/12 environment. We use SSL for all of our syslog-to-syslog connections, and have logging going to two different data pipelines.<br>
><br>
> Data Dest #1: SyslogNG Client ----(SSL)----> SyslogNG Server ------> Logstash File-read-in-service<br>
> Data Dest #2: SyslogNG Client ----(SSL)----> Stunnel Service ------> Flume Syslog Service<br>
><br>
> The data streams work fine most of the time, but if we restart either the remote syslog-ng server, or the stunnel service, it seems that the syslog ng clients don't try to reconnect for a LONG time (or ever) to the endpoints again. I end up seeing the connection on the client go into a CLOSE_WAIT state, and syslog-ng keeps thinking that its sending log events through the connection, so it seems to never try to reconnect.<br>
><br>
> I've tried setting time_reopen() to 0, 1 and 5... no luck or change in behavior.<br>
></p>
<p dir="ltr">Hmmm it really sounds strange. 3.3.4 does seem old though. Can you give the latest 3.3 maintenance release a try? Algernon has s binaries for a large number of debian/Ubuntu releases.</p>
<p dir="ltr">> Any thoughts?<br>
><br>
> --Matt<br>
><br>
> ______________________________________________________________________________<br>
> Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
> Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
> FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
><br>
</p>