No subject


Tue Sep 25 05:13:28 CEST 2007


Hi,

I'm using syslog-ng to have a bunch of webservers log to remote
syslog-servers. I have defined them on the webservers like this;

destination remote_logging { tcp("10.10.10.1" port(1999)); };
destination remote_logging { tcp("10.10.10.2" port(1999)); };

Which works fine as long as both the remote servers are reachable.
The moment one of them is unreachable, syslog-ng starts complaining
about it in the logging:

Nov 21 11:46:34 web01 syslog-ng[9892]: Connection broken to AF_INET(10.10.10.2:1999), reopening in 10 seconds

But at this moment it doesn't log to the other remote syslog-ng server
either, which makes the setup useless.

I could not find a configuration-feature to prevent this from happening,
am I overlooking something?

thanks a lot,

Roel.


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.17-mp20070417
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages syslog-ng depends on:
ii  libc6                 2.3.2.ds1-22sarge5 GNU C Library: Shared libraries an
ii  util-linux            2.12p-4sarge1      Miscellaneous system utilities

-- no debconf information


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.


More information about the syslog-ng mailing list