hmm, in looking at the list of FDs in the select giving -EAGAIN, they all look like they are TCP connections, not file outputs. so I think the problem is not in the dynafiles output, but in the input moduleyou are using (although i won't rule out the possibilitythat a huge number of open files triggered the problem)

David Lang

On Tue, 9 Nov 2010, John Feuerstein wrote:

Date: Tue, 09 Nov 2010 17:54:50 +0100
From: John Feuerstein <[email protected]>
Reply-To: rsyslog-users <[email protected]>
To: rsyslog-users <[email protected]>
Subject: Re: [rsyslog] One thread eating up infinite CPU time (spinlock?)

On 11/09/2010 05:34 PM, [email protected] wrote:
On Tue, 9 Nov 2010, John Feuerstein wrote:

BTW, thinking more about it... since the problem always occurs after
some days - perhaps it is related to using %$now% within the filename
templates in combination with the $DynaFileCacheSize?
The lsof shows a lot of open FDs ("REG") for "(deleted)" files of
previous days. FD leaking?

does a kill -HUP (which tells rsyslog to close and re-open all output
files) clear up the problem?

This does indeed do a *LOT* to lsof output. The differencte between the
pre- and post- lsof outputs is huge. I guess that we are on the right
track here, the old FDs marked as "(deleted)" are not closed properly by
rsyslogd?

lsof output before sending SIGHUP:

http://biz.baze.de/debug/rsyslog/pre-post-SIGHUP/pre-lsof.txt


lsof output after sending SIGHUP:

http://biz.baze.de/debug/rsyslog/pre-post-SIGHUP/post-lsof.txt

Note that I'm using rsyslogd's %$now% dynamic file template only to
rotate logs without the need of any external helper. So I never send
SIGHUP, because I expect rsyslogd to handle that internally?

However, the original problem of the permanent 100% CPU thread is still
there, see the pre- and post-process-tree.txt files at:

http://biz.baze.de/debug/rsyslog/pre-post-SIGHUP/
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to