* Balazs Scheidler <bazsi@balabit.hu> [2006-06-21 13:10]:
On Wed, 2006-06-21 at 01:47 +0200, Wolfram Schlich wrote:
[Syslog-NG + STunnel setup] This works fine so far, logs are sent over the encrypted tunnel without problems. Except one situation: the STunnel or Syslog-NG itself on the logserver goes down. Then this happens on the logclient: --8<-- syslog-ng[30119]: EOF occurred while idle; fd='33' --8<-- There are *lots* of those messages, like 20 per second. Is it possible to prevent Syslog-NG of creating such messages?
I've fixed this after 1.9.11 was released, look for something like this in the NEWS file:
* In the case of a broken connection don't reconnect immediately, but wait some time specified by time_reopen() to match 1.6.x behaviour.
Tried 2.0rc1+20060621 -- much better: --8<-- 2006-06-21 23:24:05 +02:00; alpha; syslog.err; syslog-ng[32329]: EOF occurred while idle; fd='5' 2006-06-21 23:24:05 +02:00; alpha; syslog.err; syslog-ng[32329]: Connection broken; time_reopen='10' --8<-- Thanks :-) -- Wolfram Schlich