Exadata General (MOSC)

MOSC Banner

Exachk daemon stops after checking for passwords

edited Jan 14, 2014 5:47AM in Exadata General (MOSC) 1 commentAnswered
While trying to run the exachk in daemon mode the daemon stops whenever it checks for passwords stating “Stopping daemon as the root password is changed on <hostname> after daemon was started” even though the root password has not changed.

 

Following is the output from  exachk_daemon.log:

 

Tue Dec 31 13:43:13 2013 - Daemon is started with PID : 63557

Wed Jan 01 06:00:58 2014 - Started exachk execution : args = -profile sysadmin

Wed Jan 01 06:16:50 2014 - Finished exachk execution

Wed Jan 01 13:44:18 2014 - Started checking passwords....

Wed Jan 01 13:44:28 2014 - Stopping daemon as the root password is changed on <hostname> after daemon was started

Wed Jan 01 13:44:40 2014 - Stopping daemon as the root password is changed on <hostname> after daemon was started

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center