Error In Rsync Protocol Data Stream Code 12 At Io.c189
warnings now in 2.6.2 Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Standard newbie issue. rsh host command (or ssh host command in your case) does so in a fairly stripped environment, for instance, a small $PATH, which is your issue (unless rsync isn't even installed on smmk39). rsync has aneasy workaround for it. add " --rsync-path=/path/on/the/remote/host/to/rsync " commonly " --rsync-path=/usr/local/bin/rsync ". You can also link it into someplace in your path, if you're the admin, and are going to be having a lot of users doing their own rsync commandlines. The stuff you're doing with services and inetd.conf are irrelevant, unless you're going to run an inetd-managed rsyncd, which is NOT what you are doing or accessing in the commandline given. Also your inet hupping is a bit scary. If you have anything that has the word "inetd" in the ps line, it's going to get a HUP, and many things react to a HUP like to a TERM. I'd suggest a pattern like " /usr/sbin/in[eE]td -s$", as you're on Solaris 8. To call that rsync server, forget the "-e ssh". have this in your /etc/rsyncd.conf: ++++++++++++++++++++++++++++++++++ [home] path = /home ++++++++++++++++++++++++++++++++++ Or tighter yet: ++++++++++++++++++++++++++++++++++ [homeforbob] path = /home/a078479/bob ++++++++++++++++++++++++++++++++++ rsync -va /export/home/a078479/bob smmk39::homeforbob I see, having read to the bottom of your message, that you did the linking thing. That's cool, and well-documented. Glad you figured it out. It's not an rsync issue, but an environmental one. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 conway at us.ibm.com Rsync Issue Solaris8 When performing a simple rsync between servers I was getting the following error: root:#> rsync -e ssh -va /export/home/a078479/bob s
servers I was getting thefollowing error:root:#> rsync -e ssh -va /export/home/a078479/bobsmmk39:/export/home/a078479/ksh: rsync: not foundrsync: connection unexpectedly closed (0 bytes read so far)rsync error: error in rsync protocol data stream (code 12) at io.c(189)root:#>I was thorghrough in setting up rsync to be used between servers and wasstill getting errors , I did the following to Setup Rsync.Added each host into the /etc/hosts file.Added each users ssh keys from each node to their ./.ssh/authorized_keysso I https://lists.samba.org/archive/rsync/2004-May/009390.html dont have to use password files or anything of the sort.Added rsync Port Alias to /etc/services:echo "rsync 873/tcp" >> /etc/servicesAdded rsync Daemon to /etc/inetd.conf:echo "rsync stream tcp nowait root /usr/bin/rsync rsyncd --daemon" >>/etc/inetd.confRecycle (HUP) inetd daemon:for i in `ps -ef |grep inetd | grep -v grep | awk '{print $2}'dokill -HUP $idoneAnd still http://rsync.samba.narkive.com/h2sXe6Kr/rsync-error-error-in-rsync-protocol-data-stream-code-12-at-io-c-189 got the error as indicated below.So I tried to do some debugging with the syntax below.root:#> rsync -e 'ssh -vv -x' -ra /export/home/a078479/bobsmmk39:/export/home/a078479/OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602fdebug1: Reading configuration data /fisc/openssh/etc/ssh_configdebug1: Applying options for *debug1: Rhosts Authentication disabled, originating port will not betrusted.debug1: ssh_connect: needpriv 0debug1: Connecting to smmk39 [172.25.108.30] port 22.debug1: Connection established.debug1: identity file /export/home/a078479/.ssh/identity type 0debug2: key_type_from_name: unknown key type '-----BEGIN'debug2: key_type_from_name: unknown key type '-----END'debug1: identity file /export/home/a078479/.ssh/id_rsa type 1debug1: identity file /export/home/a078479/.ssh/id_dsa type -1debug1: Remote protocol version 1.99, remote software versionOpenSSH_3.4p1debug1: match: OpenSSH_3.4p1 pat OpenSSH*debug1: Local version string SSH-1.5-OpenSSH_3.4p1debug1: Waiting for server public key.debug1: Received server public key (1152 bits) and host key (1024 bits).debug1: Host 'smmk39' is known and matches the RSA1 host key.debug1: Found key in /export/home/a078479/.ssh/known_hosts:1debug1: Encryption type: 3desdebug1: Sent encrypted session key.debug1: cipher_init: set keylen (16 -> 32)debug1: cipher_init: set keylen (16 -> 32)debug1: Installing crc compensation attack detector.debug1: Received encrypted confirmation.debug1: Trying RSA authentication with key'/export/home/a078479/.ssh
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company http://stackoverflow.com/questions/23899080/error-in-rsync-protocol-data-stream-code-12-at-io-c605-receiver-3-0-9 Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up error in rsync protocol data stream (code 12) at io.c(605) [Receiver=3.0.9] up vote 5 down vote favorite I'm trying to rsync data error in from one ubuntu box to another, but whenever I try to run the command, I get the error, error in rsync protocol data stream (code 12) at io.c(605) [Receiver=3.0.9] I've seen people get io.c(600) and 610 errors in various other places around the web, but nothing about a 605 error. What's the cause of this issue? How can it be fixed? The command i'm running is /usr/bin/rsync -az -e /usr/bin/ssh user@remote:filename /path/to/local/filename ubuntu rsync error in rsync share|improve this question asked May 27 '14 at 21:15 Jules 3,90163168 add a comment| 4 Answers 4 active oldest votes up vote 2 down vote accepted According to this it's an official bug. At the bottom of the page, one victim of the bug mentions he doesn't get it when the file he's trying to send is < 100 GB or when he uses the -W flag on the client (which indicates whole file copy, rather than rsync delta resolution; basically, turns rsync into little better than scp). share|improve this answer answered May 27 '14 at 21:22 Parthian Shot 588414 Would've spent much more time trying to fix this than implementing an alternative. Thanks! –Jules May 27 '14 at 22:51 add a comment| up vote 1 down vote I found that this error occurred when the hard disk drive of the target machine was full. I found this after trying the accepted answer and getting the same error, so it might help someone for whom the accepted answer does not work. Clearly this is quite a specific answer and very easy to diagnose, so I do not presume that this error message is directly connected to a lack of space on the target. share|improve this answer answered Jan 27 '15 at 11:59 M1ke 2,59811433 This was th