Hi all, just would like to understand TCP keepaliving option in more details.
Seems to be effective/sufficient on server side only. We have issue with increasing number of open filehandles of our rsyslog server and dicovered the number of open TCP connections from some hosts is increasing on server side. The root cause is the firewall just mark the TCP session as invalid after some time of inactivity and send RST to client once it is trying to use that TCP session. Unfortunately server side is not notified about it and it just accept another connection with previous still keeping open. Seems like the KeepAlive on server side will solve the issue. With one side effect - even not used connections are kept open. Just discovered the omfwd (client side) has RebindInterval option available which seems to cover some sort of connection recycling. From my point of view it would be helpful to perform connection close on server side in case no data were transmitted during configured time interval. Does that make sense? -- Peter Viskup _______________________________________________ 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.
