Rsync 2.6.9 Error Code 23

Question

Rsync 2.6.9 Error Code 23

Hello all,

I am trying to understand how to fix this error I am getting when I am attempting to rsync files to remote systems.

013/12/06 14:55:01 [6684] receiving file list

2013/12/06 14:55:01 [6684] rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-42/rsync/main.c(887) [generator=2.6.9]

From what I can see when I look at the remote server, none of the files were updated (or at least the ones I have changed) and this is happening on every single server that I a try to sync files to. My set up is that I a source directory that houses a set of files that need to be sync'd over to various servers. The source location is always the same and the destination for each client is always the same. Yet regardless of which client I am syncing to, the log files spews out this error and nothing appears to happen, despite the output making it look like something did.

Does anyone know how I can fix this? Maybe a way that I can reset something or a flag that I need to set to get this to work?

My current rsync command is: rsync -avzeu --log-file='some_directory/rsync.log' /some/source/directory/ username@system.domain.com:/some/directory

Any ideas would be greatly appreciated.

MacBook Pro, OS X Mountain Lion (10.8.4), 8GB RAM

Posted on Dec 6, 2013 1:46 PM

Reply

Answer 1

Dec 6, 2013 3:05 PM in response to Lovell Mcilwain

Add --progress and --checksum to the switches, and see if that shows anything.

Reply

Answer 2

BobHarris

Level 9

53,003 points

Dec 6, 2013 4:43 PM in response to Lovell Mcilwain

I'm just guessing, but...

Does your remote system ssh login shell initialization script echo things to the screen while logging in?

Do you suppress this when making an ssh connection to run a command?

If you do echo stuff to the display, then you would be feeding that stuff to rsync and it could cause it to think the remote rsync is sending it junk, hence the 'syntax' error.

Try adding the following to the beginning all your shell initialization files on your remote system:

[[ ${-#*i}  = ${-} ]] && return

.bash_profile

.bash_login

.profile

.bashrc

None of the above files may exist, so only update the ones that do exist.

If your remote system using csh or tcsh, then add the following to the beginning of the csh/tcsh shell initialization file(s):

if ( ! $?prompt ) exit

.cshrc

.tcshrc

.login

Message was edited by: BobHarris

Reply

Answer 3

Dec 8, 2013 10:51 AM in response to BobHarris

I realized that this might have been an issue with the mac os x client being to old to communicate with the remote systems that I wanted to sync to.

While mac os x comes with 2.6.9 the servers are using 3.1.0. I compiled a 3.1.0 version and pointed my script to use that and things seem to sync without any issue. Certainly would be nice for rsync to tell me when I am using an rsyc that is too old for what i am trying to connect to.

Reply