Re: [BackupPC-users] Fatal error (bad version): OpenSSH_5.0p1

[Holger P. <wb...@pa...>]

Hi,

brunal wrote on 2008-07-29 13:03:00 +0200 [[BackupPC-users] Fatal error (bad version): OpenSSH_5.0p1]:
> [...]
> What is strange is that I can ssh without problem nor error from the  
> backup server to the server to backup (192.168.1.2).
> I also can run a command like
> [Code]
> rsync -t 192.168.1.2:~/truc.txt ./tmp/
> [/Code]
> wihtout any problem, which use ssh and a public key.

ah, but that is *not exactly* what BackupPC does. Can you

	backuppc@backuppc-server% rsync root@192.168.1.2:truc.txt tmp/

without any problem, manual interaction or extraneous output?

brunal wrote on 2008-07-30 11:49:12 +0200 [Re: [BackupPC-users] Fatal error (bad version): OpenSSH_5.0p1]:
> [...]
> So I deleted the message in /etc/issue.net and also comment the
> "banner /etc/issue.net" line in /etc/ssh/sshd_config.

Well, removing the "banner" directive should have been enough, I guess ...

> Now the ssh+date command *only* output the date.

Good. That was necessary in any case.

> [...]
> But when I get :
> /ffp/bin/ssh -q -x -l root 192.168.1.2 rsync --server --sender -- 
> numeric-ids --perms --owner --group -D --links --hard-links --times -- 
> block-size=2048 --recursive --ignore-times . /home/temp/
> 
> Nothing happend and the command just freeze. (crying again).

Yes. That is what you asked for. You started an rsync server, so you'll have
to be an rsync client ... start typing ;-).

rsync basics in brief:
The way rsync works is by exchanging a special protocol between the rsync
client and an rsync server. The server can be an rsyncd or an invocation of
"rsync --server" automatically started over a remote shell. The client can be
an invocation of "rsync" (without "--server") or File::RsyncP.

You aren't running rsyncd, so the server is "rsync --server" in both cases.
BackupPC uses File::RsyncP and starts the server over an ssh connection (see
your log excerpt above). "rsync root@bla:truc.txt tmp/" automatically runs
"rsync --server ..." over "ssh root@bla". If you want to test the command
BackupPC runs, try, *as the backuppc user on the BackupPC server*,

	% rsync --numeric-ids --perms --owner --group -D --links --hard-links
--times --block-size=2048 --recursive --ignore-times root@192.168.1.2:/home/temp/ /tmp/anywhere-you-like

Does that work as expected? Does it ask any questions? Does it output anything
strange? Anything at all?

brunal wrote on 2008-08-01 11:20:47 +0200 [Re: [BackupPC-users] Fatal error (bad version): OpenSSH_5.0p1]:
> Can somebody explain me why source and destination are inverted in  
> the backuppc command, compare to the usual rsync use?

See "rsync basics" above. The command you are referring to starts the server.
The rsync server command line syntax is of little interest to us. BackupPC
knows which order the parameters have to be in, so we don't.

> I did the following on 192.168.1.2 :
> - stop all firewall and protection
> - allow root to connect by ssh

Please verify that backuppc can 'ssh -l root' without password prompt.
The rsync command I gave you above does that, but once more: you need to run
it as the backuppc user.

> I've tried this command in bash :
> /ffp/bin/ssh -q -x -l root 192.168.1.2 /usr/bin/rsync --server -- 
> sender --numeric-ids --perms --owner --group -D --links --hard-links  
> --times --block-size=2048 --recursive --ignore-times . /home/racine/ 
> wikiinterne/
> 
> Nothing happend and the command freeze. Why?

See above.

> I tried this command in a bash, (same as above, wihtout --server -- 
> sender) :
> /ffp/bin/ssh -q -x -l root 192.168.1.2 /usr/bin/rsync --verbose -- 
> numeric-ids --perms --owner --group -D --links --hard-links --times -- 
> block-size=2048 --recursive --ignore-times . /home/racine/wikiinterne
> 
> It copies all the content of the /root/ folder to the /home/racine/ 
> wikiinterne folder, all of this happend on the client, nothing is  
> transfered on the backup server.

That's what it is supposed to do. Neither source (".") nor destination
("/home/racine/wikiinterne") are remote, so it's a local copy you requested.

Hope that helps.

Regards,
Holger