Exadata X4-2 Hardware
 
Exadata Database Machine X2-8
 
Exadata X3-2 Hardware
 

PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_EST
 

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-8260232601>

Applies to:

Symptoms

Exachk running in daemon mode checking for password stops with message "Stopping daemon as the root password is changed on <hostname> after daemon was started" even though the root password has not been changed

exachk_daemon.log which is created in the directory from which exachk in daemon mode is launched has following entries:

Thu Dec 29 09:25:00 2013 - Daemon is started with PID : 3781

Thu Dec 30 09:25:08 2013 - Started checking passwords....

Thu Dec 30 09:25:18 2013 - Stopping daemon as the root password is changed on <host_name> after daemon was started

Thu Dec 30 09:25:29 2013 - Stopping daemon as the root password is changed on <host_name> after daemon was started

Thu Dec 30 09:25:32 2013 - Finished checking passwords....

Cause

 This is caused due to the transient issues with long login times  due to DNS names server delay in customer environment.
 

Solution

Solution:

The correct solution is to minimize the DNS server login delay in customer environment.

Workaround:

The workaround is to set the timers in a given environment to be long enough to counter the local environment DNS login delay.

Set the following to sufficiently large value for the environment from which exachk in daemon mode is launched.

export RAT_TIMEOUT=120

export RAT_ROOT_TIMEOUT=600 

export RAT_PASSWORDCHECK_TIMEOUT=30 

References

This solution has no attachment