This may be a similar situation to the one we ran into. Syslog-ng allows 10 connections from a single source max (appears to be hardcoded into afinet.c). So you could be hitting this limit. In order to fix it, we started by making sure that each server returning syslog only made one connection (some of ours were making 5) by editing the config files and now we are testing a new compile where we have changed the max connections to 1000. We've managed to make the 1000 connections with no ill effects but have not yet stress tested it with these 1000 connections. Has anyone else run into a similar situation btw? I'd be interested to find out if there was a reason that the max connections was hardcoded to such a low number. Thanks, Mike
-----Original Message----- From: Roman Ernst [mailto:roman_ernst@at.ibm.com] Sent: Friday, November 16, 2001 7:05 AM To: syslog-ng@lists.balabit.hu Subject: [syslog-ng]TCP Connection Problem
Hi!
I have configured about 10 Host logging directly to another one (TCP!!!).
Unfortunately I have the following problem:
When I reboot this logging server then syslog-ng on all the other hosts crashes...
Is there any work around or do you already know this bug?
I think normal behavour should be trying to reconnect to the logging server...
Thanks a lot for your help in advance!
Roman Ernst
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng
Mike Kelland writes:
This may be a similar situation to the one we ran into. Syslog-ng allows 10 connections from a single source max (appears to be hardcoded into afinet.c). ... we are testing a new compile where we have changed the max connections to 1000. We've managed to make the 1000 connections with no ill effects but have not yet stress tested it with these 1000 connections.
Patches? Patches? Please share...
participants (2)
-
Ed Ravin
-
Mike Kelland