Bug 4611 - i always get "rsync error: some files could not be transferred (code 23)" even when there is nothing to transfer
i always get "rsync error: some files could not be transferred (code 23)" eve...
Product: rsync
Classification: Unclassified
Component: core
x64 Linux
: P3 minor
: ---
Assigned To: Wayne Davison
Rsync QA Contact
Depends on:
  Show dependency treegraph
Reported: 2007-05-10 08:22 UTC by Karlis Kisis
Modified: 2007-10-14 16:23 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Karlis Kisis 2007-05-10 08:22:21 UTC
here is my output:
[root@timber root]$ rsync -azvv --password-file=/etc/tinydns/root/parole /etc/tinydns/root/*.cdb rsync://debija@
opening tcp connection to port 873
opening connection using --server -vvlogDtprz . timberdns 
RSYNC_PASSWORD environment variable ignored
building file list ... 
total: matches=0  hash_hits=0  false_alarms=0 data=0

sent 47 bytes  received 16 bytes  126.00 bytes/sec
total size is 3065  speedup is 48.65
rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9]
here is the log on the remote server:
2007/05/10 16:21:02 [8239] name lookup failed for Name or service not known
2007/05/10 16:21:02 [8239] connect from UNKNOWN (
2007/05/10 16:21:02 [8239] rsync to timberdns from debija@UNKNOWN (
2007/05/10 13:21:02 [8239] receiving file list
2007/05/10 13:21:02 [8239] sent 85 bytes  received 121 bytes  total size 3065

the point is I want to transfer one file. if the file is updated it transfers OK but it always displays the transfer error. why?
Comment 1 Wayne Davison 2007-10-14 16:23:38 UTC
The reason for the error-exit value is that rsync output that message about not using the RSYNC_PASSWORD environment variable as an error, which makes rsync think that something went wrong with the file transfer.

I could have changed the message from an "FERROR" to an "FINFO" message, but I don't see the purpose in having rsync comment on the presence of an environment variable when it was explicitly told to use a file on the command-line.  I have fixed in this in CVS by removing the message.