The broken pipe could have been my haste to sudo -s after SSH into the box. 

If I go into known_hosts and # out the specific line of the server with the 
issue, so I can have the data for reference,
is that the same as deleting the line or do I really have to remove the entire 
line from the known_hosts file?

Terry


-----Original Message-----
From: Les Mikesell [mailto:lesmikesell AT gmail DOT com] 
Sent: Friday, November 07, 2014 1:56 PM
To: General list for user discussion, questions and support
Subject: Re: [BackupPC-users] Unable to read 4 bytes

On Fri, Nov 7, 2014 at 12:30 PM, tschmid4 <tschmid4 AT utk DOT edu> wrote:
>
> 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.

Your screen shot has a pretty good description of what you need to do.
  When you install ssh on a host it generates a host key fingerprint and on 
your first connection to that target it stores a copy  in ~/.ssh/known_hosts 
after you respond to the prompt about it.
Subsequent connections verify that the value is the same and fail if not.  If 
know the OS has been reinstalled or the host key replaced for some other 
reason, you must remove that line (conveniently noted after the : in the error 
message) from the known_hosts file, and then manually connect to that host so 
you can answer the prompt about accepting the new value.  This is separate 
from, and in addition to what you have to do with the user level public key 
that goes in the target  authorized_hosts file.

I didn't understand the context of that:
Write failed: Broken pipe
message in your previous post though.  That could mean that you have the wrong 
owner/permissions on one of the files in question.

-- 
   Les Mikesell
     lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

------------------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/