With the default configuration, syslog gets spammed with loads of: <snip> syslog-ng[7749]: Number of allowed concurrent connections exceeded; num='10', max='10' </snip> and logging is of course broken. Apparently upstream folks made the connection limit actually working, but the default settings suck. 2.0.4 Mon, 14 May 2007 11:47:48 +0200 IMPORTANT NOTES: * This version of syslog-ng fixes a bug in enforcing the max-connections() limit for various stream-like sources (unix-stream and tcp). Previously this limit was not enforced, thus production environments may use an inadequate value. Validate your max-connection() settings before upgrading and check your logs for rejected connections. http://forums.gentoo.org/viewtopic-t-561044.html http://forums.gentoo.org/viewtopic-t-563515.html Haven't seen the message since changing the config to: source src { unix-stream("/dev/log" max_connections(20)); internal(); pipe("/proc/kmsg"); }; but this is mostly a single-user desktop, more busy servers will require definitely a higher limit. Can we change the defaults in syslog-ng.conf to something more reasonable? Thanks.
This will be changed to 256 in future syslog-ng releases. I've updated the default config to max-connections(256) in CVS in any case. If you need more connections, please remerge syslog-ng-2.0.4. Thanks for the bug report.
