Hi folks,
we are running Rsyslog 3.18.x on SLES10 and have stumbled upon a weird
phenomenon.
Our client rsyslog sent messages to a central rsyslog using tcp. They
are configured to buffer locally if the central is not available.
Now, if the tcp connection does not leave FIN_WAIT1 state (may be the
TCP ACK does not reach the client for network reasons) the client
rsyslog stops all activity (writing to local logs, importing local logs,
etc.) and does not write anything into the queue buffer files. In fact
it seems dead until rebooted.
To my understanding this is not the exptected/intended behaviour, so the
question is: Is this a known bug of this version? Is there a version
that can handle frozen FIN_WAIT1 states (I know they should not appear
at all but that is a different issue)?
Any hint to docs and understanding is greatly appreciated.
Dirk
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
