So, if I have a tls incoming server that I expect to see thousands, or tens of thousands of clients, what should I set my flow-control parameters to? I assume that I'll want max-connections to the number of clients. So, let's say 50k. What would the other paramters need to be set to? log_fifo_size, log_fetch_limit, log_iw_size? thx On 1/11/10 8:38 AM, Doug Warner wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/05/2010 11:53 AM, Doug Warner wrote:
On 12/21/2009 09:41 AM, Doug Warner wrote:
On 12/21/2009 02:50 AM, Balazs Scheidler wrote:
Periodically when syslog-ng seems to be working fine we'll see syslog-ng using
a bit of CPU (~20%), but more commonly right now we see it using very little and the recv-q building up.
Non of our src/dest in syslog-ng have any flags set other than the above global options; so whatever is the default for 3.0.4 OSE should be what we're using.
Strange. Can you start strace on the syslog-ng process, preferably with timestamps (-ttT -s 256 -p<pid>) options to see what it is doing?
Just as a follow-up, I was able to solve this by setting flow-control on my log path and increasing my log_fetch_limit() and log_iw_size() on my tcp source and increasing log_fifo_size() globally. Doing these 4 things brought my memory consumption back in line and syslog-ng seems to be processing the logs at the proper pace again.
- -Doug -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFLS1QAJV36su0A0xIRAk9FAJ9Yx4Zg+FIWkKJsC3/WVXx+GFmz4wCgrrNm +9hWZbmWh/3b3A/3O24MMi4= =cMv3 -----END PGP SIGNATURE----- ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html