Also, the permissions of the .ssh directory have to be a specific setting as well- I don't recall the exact setting but doing something like 777 or 775 on the .ssh for the db user (grid, oracle whatever) will cause odd failures in trusted ssh. I think, but cannot swear to it, that 700 should be the .ssh perms. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Marcin Przepiorowski Sent: Friday, July 26, 2013 11:16 AM To: andy@xxxxxxxxxxxxxxx Cc: lyallbarbour@xxxxxxxxxxxxxxx; oracle-l Subject: Re: slightly OT: passwordless ssh and Clusterware ssh -vvv user@host - will provide you some information about errors during password less authentication. Marcin On Fri, Jul 26, 2013 at 2:38 PM, Andy Klock <andy@xxxxxxxxxxxxxxx> wrote: > One thing to double check is the permissions on the home directory. If > this has been set to something like 770 passwordless ssh won't work. > On Fri, Jul 26, 2013 at 8:36 AM, Lyall Barbour < > lyallbarbour@xxxxxxxxxxxxxxx > > wrote: > > > Here's another hook to this craziness. I can, since i started this, > > usually, ssh from node1 to node2 ... and from node2 to node2, no problem. > > The problem is going to node1. Is there some parameter file that i need > to > > look at? The ssh versions are the same between these servers. What else > do > > i need to look at, other then ssh-keygen and ssh-copy-id, anybody? Maybe > > something doesn't link up between how the two servers are configured? > > > > > -- > //www.freelists.org/webpage/oracle-l > > > -- Marcin Przepiorowski http://oracleprof.blogspot.com -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l