On Wed, 2006-06-21 at 01:47 +0200, Wolfram Schlich wrote:
I'm currently trying out this setup:
Here are the STunnel configs:
--8<--[ stunnel.conf on logserver (excluding cert/key stuff) ]--8<-- [syslog-ng] client = no accept = 192.168.0.1:514 local = 127.0.0.1 connect = 127.0.0.1:514 --8<--
--8<--[ stunnel.conf on logclient (excluding cert/key stuff) ]--8<-- [syslog-ng] client = yes accept = 127.0.0.1:514 local = 172.16.0.1 connect = 192.168.0.1:514 --8<--
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. -- Bazsi