> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of John Feuerstein > Sent: Tuesday, November 09, 2010 5:37 PM > To: rsyslog-users > Subject: Re: [rsyslog] One thread eating up infinite CPU time > (spinlock?) > > >> 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? > > > > ah! this is interesting. How have you set your dynafile cache sizes? > > Yes, I've set: > > $DynaFileCacheSize 500
Keep in mind that this setting is ona per-action (!) level. So if you have 20 actions, you have a total limit of 500*20 = 10,000 files that can be open at any time (but not more than 500 for a single action). This is action-specific so that you can tune the size of the cache to what is expected for the action. Rainer > > ... because with %$now% in the filenames, I expect around 500 active > logfiles per day (plus some low-traffic ones that may get closed). > _______________________________________________ > 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
