EM 13c : Agent Start Fails After Host Reboot
(Doc ID 3056801.1)
Last updated on OCTOBER 31, 2024
Applies to:
Enterprise Manager Base Platform - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
EM 13c : Agent Start Fails After Host Reboot
emctl.log
---------------
15925 :: 2024-10-07 05:37:29,500::Calling acquireGlobalLock (1)
15925 :: 2024-10-07 05:37:29,500::AgentCommandLock:Acquiring a lock(type=1)on emctl lockfile
15925 :: 2024-10-07 05:37:29,500::AgentCommandLock:lockFile returns 1
15925 :: 2024-10-07 05:37:29,500::acquireGlobalLock returned: 1
15925 :: 2024-10-07 05:37:29,501::EM_SECURE_HOSTNME: <AGENT HOSTNAME>
15925 :: 2024-10-07 05:37:29,501::EM_SECURE_PORT: 3872
15925 :: 2024-10-07 05:37:29,502::EM_LISTEN_ON_ALL_NICS: true
15925 :: 2024-10-07 05:38:30,309::AgentLifeCycle.pm:status agent returned with retCode=2
15925 :: 2024-10-07 05:38:30,310::AgentLifeCycle.pm: Exiting with retCode=1: Could not determine the status of the agent process
15925 :: 2024-10-07 05:38:30,310::TZ: EmctlLogAvailabilityMarker Operation=start Diag=2(status could not be determined)
15925 :: 2024-10-07 05:38:30,310::Calling releaselobalLock
15925 :: 2024-10-07 05:38:30,310::AgentCommandLock:released lock on emctl lockfile
15925 :: 2024-10-07 05:38:30,310::Released agent command lock
15925 :: 2024-10-07 05:38:30,310::Cleaning up agent command lock
15925 :: 2024-10-07 05:38:30,310::AgentCommandLock:closed file handle of emctl lockfile
---------------
15925 :: 2024-10-07 05:37:29,500::Calling acquireGlobalLock (1)
15925 :: 2024-10-07 05:37:29,500::AgentCommandLock:Acquiring a lock(type=1)on emctl lockfile
15925 :: 2024-10-07 05:37:29,500::AgentCommandLock:lockFile returns 1
15925 :: 2024-10-07 05:37:29,500::acquireGlobalLock returned: 1
15925 :: 2024-10-07 05:37:29,501::EM_SECURE_HOSTNME: <AGENT HOSTNAME>
15925 :: 2024-10-07 05:37:29,501::EM_SECURE_PORT: 3872
15925 :: 2024-10-07 05:37:29,502::EM_LISTEN_ON_ALL_NICS: true
15925 :: 2024-10-07 05:38:30,309::AgentLifeCycle.pm:status agent returned with retCode=2
15925 :: 2024-10-07 05:38:30,310::AgentLifeCycle.pm: Exiting with retCode=1: Could not determine the status of the agent process
15925 :: 2024-10-07 05:38:30,310::TZ: EmctlLogAvailabilityMarker Operation=start Diag=2(status could not be determined)
15925 :: 2024-10-07 05:38:30,310::Calling releaselobalLock
15925 :: 2024-10-07 05:38:30,310::AgentCommandLock:released lock on emctl lockfile
15925 :: 2024-10-07 05:38:30,310::Released agent command lock
15925 :: 2024-10-07 05:38:30,310::Cleaning up agent command lock
15925 :: 2024-10-07 05:38:30,310::AgentCommandLock:closed file handle of emctl lockfile
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |