[Syslog-ng-maintainers] Bug#750056: does not recover from network loss on freebsd

[Peter Palfrader]

Package: syslog-ng
Version: 3.5.4.1-1
Severity: normal

Hi,

we run syslog-ng on all debian.org hosts, including the kfreebsd
systems.

We have configured our syslog-ngs to send messages to two loghosts:

| destination loghost-lotti {
|         tcp("lotti.debian.org" port (5140)
|                 tls( key_file("/etc/ssl/debian/keys/thishost.key")
|                      cert_file("/etc/ssl/debian/certs/thishost.crt")
|                      ca_dir("/etc/ssl/debian/certs/")
|                 )
|         );
| };
| destination loghost-lully {
|         tcp("lully.debian.org" port (5140)
|                 tls( key_file("/etc/ssl/debian/keys/thishost.key")
|                      cert_file("/etc/ssl/debian/certs/thishost.crt")
|                      ca_dir("/etc/ssl/debian/certs/")
|                 )
|         );
| };
| 
| log {
|         source(s_local);
|         destination(loghost-lotti);
|         destination(loghost-lully);
| };

Unfortunately, if syslog-ng loses its connectivity with a log server, it
will not recover from that, making admin interaction necessary.  This
seems kfreebsd specific -- we do not have that issue on our Linux hosts.

syslog-ng should probably recover from temporary network loss.

Cheers,
weasel