Hi all,
I have tracked the problem down: if rsyslog is configured to read
messages from a log file and the file does not exist, it does not
- refrain from starting
- place relevant messages somewhere
or anything sensible. It starts the weird behaviour I described even up
to TCP connections hanging in FIN_WAIT1 for ever.
Is this a known bug of 3.18.3? This is the RPM from SLES11.
Is this solved in a later release?
Or do I misunderstand something completely?
Dirk
Am 27.01.11 17:54, schrieb Dražen Kačar:
Dirk wrote:
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.
Can you run strace on the client when this happens? My guess is that it will
be hanging in the close() syscall.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
