I apologize for intruding. I've been following this conversation and now I'm confused. Is the issue the use of keys to lock down access, or the use of rsync in general?
Have you tried to run the rsync without the use of keys? Are you aware that rsync can be resumed? If you haven't checked, the perms on the .ssh directory should be 700. Cathy -- Cathy L. Smith IT Engineer Pacific Northwest National Laboratory Operated by Battelle for the U.S. Department of Energy Phone: 509.375.2687 Fax: 509.375.4399 Email: [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Rich Shepard Sent: Tuesday, November 13, 2018 5:54 AM To: Portland Linux/Unix Group <[email protected]> Subject: Re: [PLUG] rsync: worked once now perms error On Mon, 12 Nov 2018, wes wrote: > You said "rather than ssh" - did you test ssh again after you started > getting this error? What command and parameters do you use to make the > ssh connection? wes, When rsync failed to connect Sunday I used 'ssh -vv ...' to test since adding the verbose switches to rsync did not provide useful output. Yesterday I tried rsync again; same failure. Today I will re-generate the public/private key pair (same pass phrase), copy the new public key to the old desktop's authorized_keys and expect that to resolve the issue. Perhaps there is no way to determine why rsync failed after spending a lot of time moving 89G across the cat5 cable. If a new key pair works perhaps it will keep working. Regards, Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
