X-Spam-Check-By: sourceware.org Message-ID: <2f78bdb40702211422t443335b7ma1b3becc7d3cad4e@mail.gmail.com> Date: Wed, 21 Feb 2007 23:22:08 +0100 From: "Roald Hendriks" To: cygwin AT cygwin DOT com Subject: Rsync stops responding via SSH In-Reply-To: <2f78bdb40702200839g226a8c09u47e994e401e7df4d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2f78bdb40702200839g226a8c09u47e994e401e7df4d AT mail DOT gmail DOT com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Dear reader(s), First, I'll state the goal: Synchronizing data using rsync on CygWin (win2k3 servers) via a data 'pull' and ssh On a remote system, data is exported to files, and rsync is used to synchronize the data from a remote server to our local server (so a data 'pull'). When synchronizing the data (rsync -e "ssh -p 1500" --progress -v --timeout=600 --compress --times user AT localserver:/folder/*.* /localfolder/.), after some files being updated, rsync stops responding and a timeout occurs. On the remote server, rsync remains running as a process as if it 'hangs'. Note that the connection via port 1500 works fine, directory contents can be retrieved via rsync without problems. When using the '--whole-file' option, no problems occur, data is transfered perfectly, however, this is ignoring one of the key features of rsync. I've noticed some mails with regard to this issue in this mailing list on August 14th 2006 ( http://cygwin.com/ml/cygwin/2006-08/msg00487.html ). A follow-up, mentions the following: --- begin of copy from follow up message --- Yes its a known issue for the exact situation you explain. Pulling files from a hosting using ssh+rsync under CYGWIN. My current understanding of the situation is with the non-blocking implementation of pipes under CYGWIN does not return EAGAIN even the pipe buffer is full and starts to block. This causes rsync to become blocked on a write call to send data to ssh, and ssh becomes blocked also on a write call sending data to rsync. This causes a deadlock. Since rsync can work in blocking and non-blocking mode its really SSH that end that has the problem. --- end of copy from follow up message --- Is it possible that I'm suffering from this known issue? Is there a patch available? I'm using OpenSSH 4.5p1-1 and rsync 2.6.6. I have even compiled rsync 2.6.9, but this has not resolved the issue. In order to rule out a server issue, I was able to reproduce the problem on another server as well (using a fresh install of CygWin). With kind regards, Roald Hendriks -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/