currently I'm having problems with version 3.0.6 which I don't have with version 3.0.5.
This is what happens:
bin/rsync -vvauxSpz rsync://xxx.xxx.com:11000::cadappl_sde/cadappl_sde/ictools/tetramax .
opening connection using: ssh rsync rsync --server --sender -vvulogDtprxSze.is . "//xxx.xxx.com:11000::cadappl_sde/cadappl_sde/ictools/tetramax"
ssh: Could not resolve hostname rsync: host/servname not known
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [receiver=3.0.6]
Obviuosly there is a problem extracting the hostname from the rsync://... expression. I tried this on both Solaris and Linux.
Double-colon syntax is used when you don't use an rsync:// prefix. So you should either use a valid URL, or double-colon syntax, not try to combine them:
Older rsync versions would ignore the strange "::cadappl_sde" suffix on the hostname, but the improved parser in 3.0.6 won't let you get away with supplying such a weird string -- since it's not a valid URL, it assumes you're trying to connect to host "rsync" via ssh.
The reason I reopened the bug is that parsing of rsync:// handles fails even under simpler circumstances, not involving a double colon.
~$ rsync -vv /var/tmp/test.bz2 rsync://automatiks@localhost:1873:/automatiks
opening connection using: ssh rsync rsync --server -vve.s . "//automatiks@localhost:1873:/automatiks"
ssh: Could not resolve hostname rsync: Name or service not known
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6]
I have an ssh tunnel opened from local port 1873 to port 873 on a remote host (it is behind a firewall) and I obviously need to specify port in the command line.
I'm running v3.0.6 on ARM, Linux.
Thanks for your help,
You have a superfluous colon after the port number.