On Wed, 7 Oct 2009, Jonathan Bond-Caron wrote: > The client 'sends the message over tcp' and actually empties the queue! > > Is this expected behavior? rsyslogd was shutdown 'cleanly' on the server. > Shouldn't it force the client to close the TCP connection? > > > > Using netstat, the two servers are : > > > > Proto Recv-Q Send-Q Local Address Foreign Address (state) > > tcp4 0 0 client.10514 server..60726 FIN_WAIT_2 > > > > Proto Recv-Q Send-Q Local Address Foreign Address > State > > tcp 1 36 server:60726 client:10514 CLOSE_WAIT > > > > Have I misunderstood something? I've read Rainer's blog and issues with TCP > "unreliability" / case of a power failure but don't think this related
I think it's the same problem, one side thinks the connection is closed, the other doesn't and so the one that doesn't happily sends the data out. try reconfiguring to use relp and things should work as expected. now, I don't know why the close isn't getting through from the one system to the other rapidly. is there any sort of firewall in between them? David Lang _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
