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"

(Doc ID 1663561.1)

Last updated on APRIL 22, 2014

Applies to:

Exadata Database Machine X2-8 - Version All Versions to All Versions [Release All Releases]
Exadata X4-2 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata X3-2 Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Engineered System Utilities
For Exachk versions exachk 2.2.3 and above

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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms