This is an edited version of a previous post
Thanks so much for your help!
> Can you
>
> backuppc < at > backuppc-server% rsync root < at > 192.168.1.2:truc.txt
> tmp/
>
> without any problem, manual interaction or extraneous output?
>
Yes, it works perfect. No particular ou
on my MainServer...
Anyway thank you so much for your help!
I will keep experiencing after my vacation and I will fill the wiki
with an "howto install backuppc on a DNS-323 with rsync".
Best regards,
Bruno.
>
> brunal wrote on 2008-08-01 11:20:47 +0200 [Re: [BackupPC-users]
>
Holger Parplies wrote:
> 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/s
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
> [C
> I notice that you had to provide the full path to rsync in your
> /usr/bin/rsync --version example, but you don't have the full path in
> the backuppc rsync command. Maybe that's a clue (although I would be
> surprised that /usr/bin isn't in root's path).
Thanks John, but it doesn't change anyt
On Wed, Jul 30, 2008 at 11:49:12AM +0200, brunal wrote:
> But still doesn't work, same old story with "Unable to read 4 bytes".
> (crying).
>
> So after filling a few kleenex, I tried these commands :
>
> /ffp/bin/ssh -q -x -l root 192.168.1.2 /usr/bin/rsync --version
>
> Answer :
> rsync ver
Hi,
first of all, thanks all for your help!
>>> server --sender --numeric-ids --perms --owner --group -D --links --
>>> hard-links --times --block-size=2048 --recursive --ignore-times . /
>>> home/racine/archives/
>>> Xfer PIDs are now 624
>>> Got remote protocol 1852141647
>>> Fatal error (bad
Hi,
Rob Owens wrote on 2008-07-29 10:55:39 -0400 [Re: [BackupPC-users] Fatal error
(bad version): OpenSSH_5.0p1]:
> There was a Debian/Ubuntu bug in ssh a few months back.
that is unrelated in this case.
> Before that, brunal had written:
> >
> > Everything is fine but when
There was a Debian/Ubuntu bug in ssh a few months back. Update your ssh
server and client software and then try again to see if you get the same
error. Note that the update will recreate your server keys, and you'll
need to create new public/private keypairs for your users (backuppc
user, in
Hi all,
I'm using backuppc on a Dlink DNS-323 with fun_plug.
Everything is fine but when I try to launch a (full and first) backup
I get this error :
[Code]
full backup started for directory /home/racine/archives
Running: /ffp/bin/ssh -v -x -l root 192.168.1.2 /ffp/bin/rsync -v --
server --sen
10 matches
Mail list logo
