I'm SSH'ing into each server and in turn SSH'ing into each server that is having a backup issue to determine if they can connect.
Some can, some can't. 'Strict checking' is currently enabled and I am getting a
. If I simply disabled 'strict checking' and determined that all systems could
Resolve new keys amongst themselves, then enable 'strict checking' again,
would this be an acceptable troubleshooting step to determine
Why Linux boxes can't backup?
The concept is a pull configuration, correct? The BUPC server requests the data from each server,
But the keys have been renewed and need to be generated again.
What I don't know is the process for basically starting over with the SSH keys.
Terry
-----Original Message-----
From: tschmid4 [
mailto:tschmid4 AT utk DOT edu]
Sent: Thursday, November 06, 2014 2:11 PM
To: General list for user discussion, questions and support
Subject: Re: [BackupPC-users] Unable to read 4 bytes
Interesting.
The command syntax worked, (Thanks Les)
But it returned:
Permanently added 'rsa.pub' (RSA) to the list of known hosts.
Write failed: Broken pipe
Terry
-----Original Message-----
Sent: Thursday, November 06, 2014 1:54 PM
To: General list for user discussion, questions and support
Subject: Re: [BackupPC-users] Unable to read 4 bytes
> Devils in the details.
> Now it returns 'ssh: Could not resolve host name .ssh/id_rsa.pub: Name or service not known
>
> I've altered the syntax as:
>
> Ssh-copy-id .ssh/id_rsa.pub root@server
>
> Have I missed the syntax somehow?
>
Yes the .ssh/id_rsa.pub is the argument to the -i (identity) option.
If you omit one you have to omit both.
--
Les Mikesell
------------------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
------------------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
