Comment 5 for bug 631275

Revision history for this message
edso (ed.so) wrote : Re: 0.6.09: rsync url parsing broken, but only with python 2.6

Something else is wrong here. If rsyncbackend really would misinterpret the url the failing command shown would be like

Running "rsync -e 'ssh -oBatchMode=yes' luser@otherbox:module/somedir/" failed

For some reason the rsync wants to use ssh as remote shell. Can it be that the env var RSYNC_RSH=ssh is set in your environment?

At least that's what the error says

Running 'rsync rsync://otherbox::/module/somedir/' failed (attempt #1)
Error is:
rsync: Failed to exec ssh: No such file or directory (2)

Strangely though in you strace a ssh is found an executed.

However I can't reproduce the error until now. Even exporting RSYNC_RSH and excuting rsync on commandline does not sport similar issues. You should try yourself, does

rsync rsync://otherbox::/module/somedir/

also spit out the 'rsync: Failed to exec ssh' error?
Can you connect to you rsyncd with authentification? What commandline do you use for that?

--

Regarding your missing credentials. They are set in the backend as env vars USER, RSYNC_PASSWORD if rsync does not use ssh for security reasons. Rsync over ssh currently only works with keyauth and ssh is too stupid to read the USER var hence it is located in the url.
I cannot see an error that mentions a failed login. Did you occur one? What was the error message?

..so far
ede/duply.net