PRKC-1044

I ran into this issue on one of our RAC clusters.

The error is:The user “oracle” does not have user equivalence setup on nodes. Please setup the user equivalence before proceeding. PRKC-1044 : Failed to check remote command execution setup for node dbserver-010 using shells /usr/local/bin/ssh and /usr/bin/rsh dbserver-010: Connection refused.

The fix was to ssh to all the names by which the computers were known as (all the interfaces) and answer the ssh question about adding the new identity.

dbserver-010% ssh dbserver-010-vip uname -nThe authenticity of host ‘dbserver-010-vip (10.0.0.53)’ can’t be established.RSA key fingerprint is 57:3b:fd:e7:b8:e8:a2:8a:81:f8:b0:19:fc:68:20:17.Are you sure you want to continue connecting (yes/no)? yesWarning: Permanently added ‘dbserver-010-vip,10.0.0.53′ (RSA) to the list of known hosts.dbserver-010

Then I also had to enable rlogin on all the cluster nodes with the following command:

dbserver-010# svcadm enable svc:/network/login:rlogin

While the above solutions helped the final problem turned out to be the way my VNC server session was rejecting the Xauth and ssh/rsh was sending a warning back to the Oracle check script which verifies ssh/rsh and has nothing to do with X but the Warning is ignorantly treated like an outright failure. From the console this is the output of a simple ssh command:

dbserver-010% ssh dbserver-012
Warning: No xauth data; using fake authentication data for X11 forwarding.

During installation check, oracle runs following command to check node connectivity:

/usr/local/bin/ssh -o FallBackToRsh=no -o PasswordAuthentication=no -o StrictHostKeyChecking=yes -o NumberOfPasswordPrompts=0 node1.domaina.com /usr/bin/true

Reference Metalink Note:338045.1

This entry was posted on Saturday, September 1st, 2007 at 11:24 am and is filed under Oracle. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One Response to “PRKC-1044”

  1. roger pack says:

    Wow. Another possible help would be to change ~/.ssh/config to include the line StrictHostKeyChecking no
    (sometimes helps with key checking).
    R out.

Leave a Reply