11.6 Remote Login Problems

If Oracle ORAchk and Oracle EXAchk have problem locating and running SSH or SCP, then the tools cannot run any remote checks.

Also, the root privileged commands do not work if:

• Passwordless remote root login is not permitted over SSH

• Expect utility is not able to pass the root password

1. Verify that the SSH and SCP commands can be found.

   • The SSH commands return the error, No such file or directory, if SSH is not located where expected.

     Set the RAT_SSHELL environment variable pointing to the location of SSH. Note that you cannot export the RAT_SSHELL environment variable, set it in the conf_file. For more information, see Running Generic Compliance Framework (Oracle ORAchk and Oracle EXAchk) Commands.

   • The SCP commands return the error, /usr/bin/scp -q: No such file or directory, if SCP is not located where expected.

     Set the RAT_SCOPY environment variable pointing to the location of SCP. Note that you cannot export the RAT_SCOPY environment variable, set it in the conf_file. For more information, see Running Generic Compliance Framework (Oracle ORAchk and Oracle EXAchk) Commands.

2. Verify that the user you are running as, can run the following command manually from where you are running Oracle ORAchk and Oracle EXAchk to whichever remote node is failing.

   $ ssh root@remotehostname "id"
   root@remotehostname's password:
   uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)

   • If you face any problems running the command, then contact the systems administrators to correct temporarily for running the tool.

   • Oracle ORAchk and Oracle EXAchk search for the prompts or traps in remote user profiles. If you have prompts in remote profiles, then comment them out at least temporarily and test run again.

   • If you can configure passwordless remote root login, then edit the /etc/ssh/sshd_config file as follows:

     n to yes

     Now, run the following command as root on all nodes of the cluster:

     hd restart

3. Enable Expect debugging.

   • Oracle ORAchk uses the Expect utility when available to answer password prompts to connect to remote nodes for password validation. Also, to run root collections without logging the actual connection process by default.

   • Set environment variables to help debug remote target connection issues.

     • RAT_EXPECT_DEBUG: If this variable is set to -d , then the Expect command tracing is activated. The trace information is written to the standard output.

       For example:

       export RAT_EXPECT_DEBUG=-d

     • RAT_EXPECT_STRACE_DEBUG: If this variable is set to strace, strace calls the Expect command. The trace information is written to the standard output.

       For example:

       export RAT_EXPECT_STRACE_DEBUG=strace

   • By varying the combinations of these two variables, you can get three levels of Expect connection trace information.

Note:

Set the RAT_EXPECT_DEBUG and RAT_EXPECT_STRACE_DEBUG variables only at the direction of Oracle support or development. The RAT_EXPECT_DEBUG and RAT_EXPECT_STRACE_DEBUG variables are used with other variables and user interface options to restrict the amount of data collected during the tracing. The script command is used to capture standard output.

As a temporary workaround while you resolve remote problems, run reports local on each node then merge them together later.

On each node, run:

orachk -local

exachk -local

Then merge the collections to obtain a single report:

orachk –merge zipfile 1  zip file 2 > zip file 3 > zip file ...

exachk –merge zipfile 1  zip file 2 > zip file 3 > zip file ...