similar to: protocol error?

We're using rsync to mirror a web server. The rsync is initiated using ssh from a Red Hat Linux 7.2 box, the files are located on an Alpha running a version of Digital Unix 4. On the Alpha rsync is 2.5.2, The Linux box used to have a 2.4.6-X version, but with the map_ptr problems I built 2.5.2 on that as well. However, version incompatibility was not the problem, as they persist after the

Howdy, We occassionally get the following error when running our nightly backups: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) This happens more on one or two machines than on any of the others. We've looked high and low to see if we're mistakenly sending these signals, but nothing is that we can find. Does anyone know what this might be from? Is it the server

Hi, I've had some issues with rsync over ssh with version 2.4.4 which an update to 2.4.6 fixed. The problem I have now is that machines which do not have a valid reverse dns entry for their IP addresses get empty directory listings from the server, even though they can get the module list and the motd each time. This is what I see in the server's log file for each attempt from such hosts

Hi, I have configure rsync 2.4.6-2 on redhat 7.1 but i am facing a problem while synchronizing big directory tree between two linux system over the network. Even if i mount any volume either through (nfs or ncp or samba) this sync commands stops after copying few directorys. I have tried 2.5.0 version but that too shows a message saying bits overflow and it shows that it is copying file but

Rsync reports the status code of the remote command. So in some situations the status code is successful when the command fails. Rsync of a remote file to a local read-only directory fails, but exits with $status = 0. I'd like to get $status = 23. Is it possible? Local copy fails with status = 23 > mkdir /tmp/nowrite > chmod -w /tmp/nowrite > rsync /etc/group /tmp/nowrite || echo

Hi all, rsync-2.4.6 has been running for quite a while with no problems, until about a week ago when for some reason it blocked on the same host ever time. I use it to backup about thirty hosts to my backup server, but for some reason it's illiciting that blocking bug that some people experience with 2.4.6. So, I upgraded the client side with 2.4.7, but it complained of protocol differences.

Hi, I have some files size 400MB+ that my rsync ends on, error message is : "Write failed: Broken pipe". Without this "big files" everything works smoothe. I searched to find anything about this problem but so far without any luck. Source machine : Solaris 8, rsync-2.4.6 Destination machine : FreeBSD 4.1.1, rsync 2.4.6 Command run(from source machine): rsync

Hello, I'm having a problem doing a remote rsync over ssh - i'm using a script that has worked for quite a while, using rsync 2.4.6 on both ends. I upgraded the "client" to 2.5.5, and began seeing this error: rsync: connection unexpectedly closed (158246 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) At which time there is a

Dear rsync people, I have just started using rsync for backups. I have had a couple of issues. Note I'm trying to use rsync as user using ssh between two machines both running Debian GNU/Linux potato (2.2r3). The local machine is currently running 2.4.6-1 and the remote 2.3.2-1.2. 1) When I run rsync with the vv option, stuff scrolls of my screen faster than I can read it. I was wondering if

I was glad to see a new version of rsync because I though that it was kind of dead. :-) Anyway, I just checked and noticed that the following isn't fixed yet, or is considered a feature. When run in dry-run mode, rsync doesnt report diffs in permissions and ownership. IMHO this is not the expected and wanted behaviour, I want to see exactly what it would do without the '-n'. I have

I am trying to finalize the use of rsync for updatiung a new nfs server before we take the old one offline. I keep getting the following warning during the rsync process: Warning: unexpected rad size of 0 in map_ptr Any ideas where this comes from and how to make it go away? I am using rsync 2.5.2 on Solaris 8 to pull data from rsync 2.5.2 on Solaris 7. Bob roconnor@vectorpartners.com

New to the group! Which version is considered stable for redhat 7.2. I have attempted to compile 2.5.2 but recieve numerous compile warning. Once installed, I receive the following error but just keying rsync {return}. Please see the rsync(1) and rsyncd.conf(5) man pages for full documentation See http://rsync.samba.org/ for updates, bug reports, and answers rsync error: syntax or usage error

Hello, I have compiled rsync 2.5.0 cleanly on a Solaris 2.6 box, and can use the resultant binary as a client with no problem. However, when I try and start a daemon, it exits with exit code 0, and no daemon running. I have previously run 2.4.6 and other versions with the same rsyncd.conf file, but can't seem to get the daemon up with 2.5.0. A truss shows the following: # truss -f

I am getting the following error when mirroring part of the RedHat distribution tree over a slow connection (~T1 speed). When running over a faster network (100BaseT) the problem does not appear. Note, the problem file a large 600MB ISO image, whereas other small files appear to be fine. rsync: open connection using /path/ssh remote.host /path/rsync --server -vlHogDtprRz --timeout=600 --delete

rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(139) Also, on 2.4.6 I was getting this: access_log write failed on access_log : Success unexpected EOF in read_timeout THis is about an 800meg file I'm trying to copy. Thanks -jeremy -- The trouble with being poor is that it takes up all your time.

After installing nevest version of sync 2.4.6 from 2.4.1, sync --daemon wrote to logfile: 2001/11/13 12:27:46 [12261] rsyncd version 2.4.6 starting 2001/11/13 12:27:46 [12261] bind failed on port 873 2001/11/13 12:27:46 [12261] transfer interrupted (code 10) at socket.c(233) sync 2.4.1 worked normally... My question: Where i can find "WATHSNEW" or "CHANGES"

rsync-2.4.6-2mdk I ran an rsync into a file system that filled up. I got no error message out of rsync - it just stopped and exited sliently. I stuck an fprintf into the receiving code and verified that the proper error was being generated - it just never gets printed by the rsync sending process. I submitted a bug report about it; but, I can't believe that other people haven't had

https://bugzilla.mindrot.org/show_bug.cgi?id=2389 Bug ID: 2389 Summary: update the PROTOCOL.certkeys spec to avoid confusion regarding encoding of critical options fields Product: Portable OpenSSH Version: 6.8p1 Hardware: All OS: All Status: NEW Severity: enhancement

Hi list, Since upgrading rsync to version 2.5.2 on a Solaris 2.5.1 box, I see plenty of Warning: unexpected read size of 0 in map_ptr when doing my nightly backup (rsyncing some directories to an rsyncd on the same LAN). I have never seen this message before, and I only see it on the Solaris machine (I upgraded all my other machines to 2.5.2 as well). I hope this is not a FAQ... I did not find

Hi all. I'm writing an installation script that uses Cygwin's bash.exe to launch an rsync.exe process, which is passed arguments. This performs an rsync over the Internet. I'd like to capture stdout to one file, and stderr to another, so that I can have a clean log of any errors. However, rsync.exe's use of file descriptors isn't jiving with my understanding of them. If I