On Mon, 8 Dec 2014, Peter Viskup wrote:
Hi all,
we observed issues once setting InputTCPMaxSessions above the default
MaxOpenFiles process limits.
The rsyslog reached MaxOpenFiles limit and just crashed.
Setting the value of InputTCPMaxSessions should increase MaxOpenFiles or
rsyslog should not start or complain about it at least. There are more
configuration parameters which need some additional pre-start
checks/modifications (MaxListeners, ...).
It's not quite that simple.
I agree that it would be useful to detect that maxsessions is > maxopenfiles,
but if it is, figuring out what maxopenfiles needs to be increased to requires
knowing a lot more about what's going on. How many files is rsyslog going to be
writing to? and do you have dynafiles configured which makes this variable based
on the contents of the log messages? Are you using any modules that will require
filehandles? if so, how many will they need.
I think the best you can do is to complain and tell the admin that it looks bad.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
