Mike Tremaine wrote:
On Wed, 2005-08-10 at 07:21, Stephan Hendl wrote:
the lines with values "STATS: dropped <!=0>" are very annoying. How can I prevent the syslog-ng from dropping lines??? I put the line "log_fifo_size(1000);" into the global section - hope that helps ;-)))
If the hosts only job is syslog-ng go for broke and kick it up to something higher then 1000.
log_fifo_size (128056);
[I used that when I was doing some testing with an old AMD-k62 500mhz 256MB and FC3, it ran with 5 hosts sending as fast as the could to it. Didn't drop anything.]
I have about 15 systems logging to my syslog-ng server and some of them are routers which send a ton of messages about up/down link state. This server is getting smashed with logs and I have not received any dropped messages other than the 'DROPPED 0' which is a good thing that the syslog-ng host is saying it has not dropped any log packets. I would think something else is going on here and the fifo would not need to be increased as my fifo setting is only at 1024. In your first message you pasted something from the host 'pns1' which was complaining about dropping multiple packets. What is this system and is it running syslog-ng, also what connection is it using? tcp/udp? Are there other hosts which are sending out dropped log messages or only pns1? - Ken