[syslog-ng] STATS: high amount of dropped messages

Jeffrey Chandler jeffrey.chandler at gmail.com
Wed Apr 9 23:12:19 CEST 2008


Hello,

I am using syslog-ng 1.6.12 on Solaris 10 (sparc).  I am seeing a large
amount of dropped message every time

Apr  9 20:14:18 syslog syslog-ng[16754]: STATS: dropped 1068470
Apr  9 20:24:18 syslog syslog-ng[16754]: STATS: dropped 1031716
Apr  9 20:34:18 syslog syslog-ng[16754]: STATS: dropped 997105
Apr  9 20:44:18 syslog syslog-ng[16754]: STATS: dropped 943151
Apr  9 20:54:18 syslog syslog-ng[16754]: STATS: dropped 1016377
Apr  9 21:04:18 syslog syslog-ng[16754]: STATS: dropped 992911

In previous posts, I have seen that this does not relate to log entries
written to disk, but rather to a different destination, ie a pipe.  In the
case of our environment, we pipe all of the data which comes into syslog-ng
to a pipe which is then forwarded to ArcSight through an agent running on
the system.  With the number of entries showing up as "dropped," would you
recommend a different method to achieve this same task?  Is this also a 1 to
1 correlation of messages that are not sent to the pipe?

Thanks,

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20080409/17e044b6/attachment.htm 


More information about the syslog-ng mailing list