Hi syslog-ng pro's, I always get messages like these: Oct 2 09:28:05 nobaq syslog-ng[2207]: STATS: dropped 548 I searched google but I could not find a solution or a good explanation why this happens. If this is true and syslog dropped 548 (!) log messages this would be bad. I think a syslog daemon is an important thing that should NOT just drop messages. I can't imagine that my system is not strong enough. 512MB RAM, 1.7Ghz. I've already set the FIFO size to a high value: $ grep size /etc/syslog-ng/syslog-ng.conf # log_fifo_size(2048); log_fifo_size(32768); log_msg_size(2048); But it does not help. Then I grepped the source to see where the problem comes from. There is a variable pktbuf_dropped_pkts and in the whole source I can not find any reference that increments this var. Is this warning uncritical? Is there any solution on this? Best regards, Niki PS: Debian sarge, v. 1.6.5
Niki Hammler wrote:
Hi syslog-ng pro's,
I always get messages like these:
Oct 2 09:28:05 nobaq syslog-ng[2207]: STATS: dropped 548
I searched google but I could not find a solution or a good explanation why this happens.
It happens because the configuration contains an erronous xconsole destination, this is a bug/feature in the debian package. Remove it, and reload syslog-ng. -- Sandor Geller wildy@balabit.hu
Sandor Geller schrieb:
Niki Hammler wrote:
Hi syslog-ng pro's,
I always get messages like these:
Oct 2 09:28:05 nobaq syslog-ng[2207]: STATS: dropped 548
I searched google but I could not find a solution or a good explanation why this happens.
It happens because the configuration contains an erronous xconsole destination, this is a bug/feature in the debian package. Remove it, and reload syslog-ng.
Hi! Thanks for your quick response! If this is really the solution it would be great! As this is a server I don't need xconsole anyway :-) I've removed every entry with xconsole and hope that the messages will disappear :-) Best Regards, Niki
participants (2)
-
Niki Hammler
-
Sandor Geller