Hi All, We found lots of rsyslog clients that had several ESTABLISHED port open with rsyslog collectors. They will not go away until client or collector restart the rsyslog process. Because of that it quickly consume TCP socket resources on the collector side which made it not available to accept any new events.
Anybody experienced the same issue before? Is there any parameter to specify to timeout the connection if it runs too long or a bug fix necessary to resolve the issue? Thanks Victor _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/
