This is RHEL 5.5 x86_64

Linux lio-db8 2.6.18-194.11.4.el5xen #1 SMP Fri Sep 17 05:17:00 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48)

In the meantime, do you know a version that doesn't have this bug, so I can work with it until youre working on a fix ?

Thanks.


On Wed, Feb 2, 2011 at 5:42 PM, Gergely Nagy <algernon@balabit.hu> wrote:
On Wed, 2011-02-02 at 17:29 +0300, Mailing Lists wrote:
> Not sure if syslog-ng has a bug tracker, but I couldn't find one
> anyway, so posting this here.

We have a bugzilla at http://bugzilla.balabit.com/ (although I agree, it
could be more visibly advertised that it exists), for future reference.

> Here is the problem: I have source file that is a log file that is
> been truncated periodically (by log rotate).
> When the truncation happens syslog-ng process starts taking 100% CPU,
> and not doing any logging. This behavior remains until source file
> receives a write.

This sounds very, very familiar to me.

May I ask what platform this is on (OS, architecture, etc)?

--
|8]


______________________________________________________________________________
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