We are getting some pushback from our SA group regarding root having ssh user equivalence on the cluster where we run OCFS2. Is it required to have the ssh user equivalence setup for the root user when running OCFS2 ? Thanks in advance, Reid Reid McKinley ******************************************************************************************** This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please contact the sender immediately by reply e-mail and destroy all copies. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. TIAA-CREF ******************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20091020/7b84ef3d/attachment.html
Or do we need user equiv for root for any other functionality on OEM grid...outside OCFS2? ________________________________ From: McKinley, Reid Sent: Tuesday, October 20, 2009 2:45 PM To: ocfs2-users at oss.oracle.com Cc: Ramayani, Atul Subject: ssh user equivalence We are getting some pushback from our SA group regarding root having ssh user equivalence on the cluster where we run OCFS2. Is it required to have the ssh user equivalence setup for the root user when running OCFS2 ? Thanks in advance, Reid Reid McKinley ******************************************************************************************** This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please contact the sender immediately by reply e-mail and destroy all copies. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. TIAA-CREF ******************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20091020/8a84dc9c/attachment-0001.html
McKinley, Reid wrote:> > We are getting some pushback from our SA group regarding root having > ssh user equivalence on the cluster where we run OCFS2. > > > > Is it required to have the ssh user equivalence setup for the root > user when running OCFS2 ? > > >The only place this comes in handy is when one uses ocfs2console to propagate the cluster.conf to all nodes in the cluster. But it allows users to enter the password. There is nothing stopping you from propagating that config file manually too.
Sunil, Thanks. We observed the below error after blocking ssh root user equiv. -----Original Message----- From: Sunil Mushran [mailto:sunil.mushran at oracle.com] Sent: Tuesday, October 20, 2009 2:56 PM To: McKinley, Reid Cc: ocfs2-users at oss.oracle.com; Ramayani, Atul Subject: Re: [Ocfs2-users] ssh user equivalence McKinley, Reid wrote:>> We are getting some pushback from our SA group regarding root having> ssh user equivalence on the cluster where we run OCFS2.>>>> Is it required to have the ssh user equivalence setup for the root> user when running OCFS2 ?>>>The only place this comes in handy is when one uses ocfs2console to propagate the cluster.conf to all nodes in the cluster. But it allows users to enter the password. There is nothing stopping you from propagating that config file manually too. ******************************************************************************************** This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please contact the sender immediately by reply e-mail and destroy all copies. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. TIAA-CREF ******************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20091020/aea30c03/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 110973 bytes Desc: image001.jpg Url : http://oss.oracle.com/pipermail/ocfs2-users/attachments/20091020/aea30c03/attachment-0002.jpe -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 173352 bytes Desc: image002.jpg Url : http://oss.oracle.com/pipermail/ocfs2-users/attachments/20091020/aea30c03/attachment-0003.jpe
Unrelated errors. The ios are failing because of some problem in your io stack. Disconnect storage, perhaps. Ramayani, Atul wrote:> > Sunil, > > > > Thanks. > > > > We observed the below error after blocking ssh root user equiv. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > From: Sunil Mushran [mailto:sunil.mushran at oracle.com] > Sent: Tuesday, October 20, 2009 2:56 PM > To: McKinley, Reid > Cc: ocfs2-users at oss.oracle.com; Ramayani, Atul > Subject: Re: [Ocfs2-users] ssh user equivalence > > > > McKinley, Reid wrote: > > > > > > We are getting some pushback from our SA group regarding root having > > > ssh user equivalence on the cluster where we run OCFS2. > > > > > > > > > > > > Is it required to have the ssh user equivalence setup for the root > > > user when running OCFS2 ? > > > > > > > > > > > > > The only place this comes in handy is when one uses ocfs2console to > > propagate the cluster.conf to all nodes in the cluster. But it allows > users > > to enter the password. There is nothing stopping you from propagating > > that config file manually too. > > ******************************************************************************************** > This message, including any attachments, contains confidential information intended > for a specific individual and purpose, and is protected by law. If you are not the intended > recipient, please contact the sender immediately by reply e-mail and destroy all copies. > You are hereby notified that any disclosure, copying, or distribution of this message, or > the taking of any action based on it, is strictly prohibited. > > TIAA-CREF > ******************************************************************************************** >
Thanks... -----Original Message----- From: Sunil Mushran [mailto:sunil.mushran at oracle.com] Sent: Tuesday, October 20, 2009 3:10 PM To: Ramayani, Atul Cc: McKinley, Reid; ocfs2-users at oss.oracle.com Subject: Re: [Ocfs2-users] ssh user equivalence Unrelated errors. The ios are failing because of some problem in your io stack. Disconnect storage, perhaps. Ramayani, Atul wrote:> > Sunil, > > > > Thanks. > > > > We observed the below error after blocking ssh root user equiv. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > From: Sunil Mushran [mailto:sunil.mushran at oracle.com] > Sent: Tuesday, October 20, 2009 2:56 PM > To: McKinley, Reid > Cc: ocfs2-users at oss.oracle.com; Ramayani, Atul > Subject: Re: [Ocfs2-users] ssh user equivalence > > > > McKinley, Reid wrote: > > > > > > We are getting some pushback from our SA group regarding root having > > > ssh user equivalence on the cluster where we run OCFS2. > > > > > > > > > > > > Is it required to have the ssh user equivalence setup for the root > > > user when running OCFS2 ? > > > > > > > > > > > > > The only place this comes in handy is when one uses ocfs2console to > > propagate the cluster.conf to all nodes in the cluster. But it allows > users > > to enter the password. There is nothing stopping you from propagating > > that config file manually too. > >************************************************************************ ********************> This message, including any attachments, contains confidentialinformation intended> for a specific individual and purpose, and is protected by law. If youare not the intended> recipient, please contact the sender immediately by reply e-mail anddestroy all copies.> You are hereby notified that any disclosure, copying, or distributionof this message, or> the taking of any action based on it, is strictly prohibited. > > TIAA-CREF >************************************************************************ ********************>******************************************************************************************** This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please contact the sender immediately by reply e-mail and destroy all copies. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. TIAA-CREF ********************************************************************************************