[SOLVED] RSYNC TCP ZeroWindow

designator · 02-10-2011, 01:26 PM

I'm trying to run an RSYNC job that keeps hanging without any error messages. When I started monitoring traffic with WireShark, I found that RSYNC runs without problems for a few minutes, then starts generating endless TCP ZeroWindow warnings and eventually dies with TCP Window Full error.

Has anyone seen this before? Any suggestions?

PS: I should mention that I don't know much about remote system and I'm not using SSH, just pure RSYNC.

unSpawn · 02-12-2011, 04:54 AM

Have a look at this old article: http://www.novell.com/connectionmaga...h_talk_11.html as it shows you some things to check as well as why talking about monitoring (without actually posting any packet logs) leads nowhere.

designator · 02-18-2011, 11:45 AM

Quote:

Originally Posted by unSpawn

Have a look at this old article: http://www.novell.com/connectionmaga...h_talk_11.html as it shows you some things to check as well as why talking about monitoring (without actually posting any packet logs) leads nowhere.

That article, as well as a few others I found, points to not having enough processing power to handle the traffic. I'm sure that was relevant in 1980. Since article is from 2007, I think he was working with REALLY old hardware.

And I'm sure that packet logs carry very deeply hidden meta data which would make my problem trivial and a solution perfectly obvious, but I thought that posting the exact description of the ONLY TCP error messages that show up in the logs would be sufficient. Rest were RSYNC commands and actual data.

Workaround that solved my problem:
I solved my problem with an infinite loop and a timeout setting:

Code:

while true; rsync -az --timeout=10 --password-file=~/.psswd /media/Backup/ user@server::user/Backup/; do