X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:from:date:message-id:subject:to :content-type; q=dns; s=default; b=ueofmyD7eZGNsQ2iYViOudZXZENof 9f1tlWW/s2VgkOv9Kt9b6ZxLM5T8b75Uq07S17ozzbuSpNB2PowSnAGTUIu7foUy Bfq8imYPwpyPTNK+5Iwd7NtJlNRVFWeA0YMWpS4GgkZ0E0Mp8IyYG2MbidxL3nAB z906Lqb00nv9oI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:from:date:message-id:subject:to :content-type; s=default; bh=si42tZBDB2KWUZfJHKFwe6kskak=; b=Tw1 OFA5RTvQl1bmnv/fgOV+wdbuOvMbMEWWBaXsO6d0p7Sv8s2/0+g36tPkto/YbV3g jzcFgY1M2lgXSOdisBq/XOsr4sqMx87v5/fRajslza8exO1zWvRvN+LYI9YDxFFp FO0Veus7crOqDUgpM0fNAUHTAoKWSIenjYOmTAlM= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-HELO: s87.webhostingserver.nl X-Received: by 10.50.28.8 with SMTP id x8mr72230097igg.19.1426155155184; Thu, 12 Mar 2015 03:12:35 -0700 (PDT) MIME-Version: 1.0 From: Frank Fesevur Date: Thu, 12 Mar 2015 11:12:04 +0100 Message-ID: Subject: rsync still broken To: "cygwin AT cygwin DOT com" Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Hi Jari, It looks like rsync is still broken. When you released 3.1.0 it had an upstream bug that made it extremely slow on cygwin. Other then that it also had another problem that I reported here: https://www.cygwin.com/ml/cygwin/2014-08/msg00440.html Yaakov made 3.1.0 test and we all automatically reverted to 3.0.9. Recently 3.1.1 was released leaving the broken test version 3.1.0 as previous. I didn't update my servers yet, The day before yesterday I did, so I went from 3.0.9 to 3.1.1. And yesterday I saw that my backup *completely* failed because of these errors: @ERROR: setgid failed rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.0] ERROR: /usr/bin/rsync returned 5 while processing rsync://192.168.200.208/backup-d/DataShares/ @ERROR: setgid failed rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.0] ERROR: /usr/bin/rsync returned 5 while processing rsync://192.168.200.208/backup-d/DataGit/ @ERROR: setgid failed Very similar error as I reported for 3.1.0. FYI, I run the cygwin based rsync daemon on my Windows servers and have a Ubuntu server that backups the data with rsnapshot (which utilizes rsync to do the transfers). The errors above are shown on the Ubuntu server. Luckily I still had a 3.0.9 executable on one machine and I've put that exe on all the updated servers to make sure the backup worked again last night. So those systems new think they have 3.1.1 but the actually have the exe of good old properly working 3.0.9 Note that 3.0.9 is not available on the mirrors anymore. I hope that it can be restored on the mirrors and made current again for the time being and that this you have time to look into this problem. But the bottom line is that 3.1.x breaks my backup. Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple