what version of rsyslog is this?

I don't remember seeing anything like this before. Rainer is out (presenting at Linuxtag I believe) this week

TCP should only be able to drop messages when the connection is cut. Do you have a firewall in between your source and destination that may have some sort of timeout or other limit?

David Lang

On Wed, 22 May 2013, Robert Navarro wrote:

Date: Wed, 22 May 2013 17:38:49 -0700
From: Robert Navarro <[email protected]>
Reply-To: rsyslog-users <[email protected]>
To: [email protected]
Subject: [rsyslog] Dropped Log Debug

Hello,

I'm trying to debug some log dropping issues and I notice lines like this
in the debug output:

3119.633279579:7ff32b5d5700: TCP sent 16384 bytes, requested 25903
3119.633300017:7ff32b5d5700: message not completely (tcp)send, ignoring
16384

3119.669879126:7ff32b5d5700: TCP sent 16384 bytes, requested 63433
3119.669908446:7ff32b5d5700: message not completely (tcp)send, ignoring
16384

3121.689679357:7ff32b5d5700: TCP sent 16384 bytes, requested 105302
3121.689780045:7ff32b5d5700: message not completely (tcp)send, ignoring
16384

is that cause for concern?

What other things should I be looking at to help debug this?

The output above was generated using the following command:
rsyslogd -c5 -dn > log.txt


_______________________________________________
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.

Reply via email to