EM 12c : Agent Unreachable 'DEBUG - TMMain sending signal: SHUTDOWN' Clock Mismatch Reported in emctl.log
(Doc ID 2075200.1)
Last updated on NOVEMBER 17, 2019
Applies to:
Enterprise Manager Base Platform - Version 12.1.0.1.0 and laterInformation in this document applies to any platform.
Symptoms
Agent is getting stopped. Receiving agent unreachable alert.
/AGENT_INST/sysman/log/emctl.log
18559 :: Tue Oct 20 17:03:10 2015::AgentLifeCycle.pm: Processing start agent
/AGENT_INST/sysman/log/gcagent.log report following shutdown signal
2015-10-29 17:01:39,643 [1:3305B9] INFO - Agent is starting up
................
2015-10-29 17:03:20,470 [1:3305B9] DEBUG - agent is writing status RUNNING
2015-10-29 17:01:50,391 [1:3305B9] INFO - Agent is up and running.
2015-10-29 17:01:50,392 [1:3305B9] DEBUG - agent is writing status RUNNING
2015-10-29 17:01:50,532 [141:980F9148] DEBUG - agntstmp.txt successfully written
................
2015-10-29 17:03:36,929 [34:4C12D99A:HTTP Listener-34 - /emd/lifecycle/main/ (~Task-free~ emdctl@6113@IBL083P1=>[144611120570001])] INFO - >>> Dispatching request: StopAgentRequest (DON'T KILL (self-destruct in 120 seconds)) <<<
2015-10-29 17:03:36,930 [34:4C12D99A] DEBUG - Issuing shutdown signal on TMMain: KillSubProcs=false
......
2015-10-29 17:03:36,930 [34:4C12D99A] DEBUG - TMMain sending signal: SHUTDOWN
2015-10-29 17:03:36,930 [1:3305B9] INFO - Agent is shutting down
Agent being stopped in ~3 min
/AGENT_INST/sysman/log/emctl.log reports following clock mismatch entries
2446 :: Thu Oct 29 17:01:30 2015::validateTZAgainstAgent: Asia/Shanghai, UTC
2446 :: Thu Oct 29 17:01:30 2015::_checkPastTZMappings: Asia/Shanghai UTC
2446 :: Thu Oct 29 09:01:32 2015::validateTZAgainstAgent: Asia/Shanghai, Asia/Shanghai
2446 :: Thu Oct 29 09:01:32 2015::AgentTuning.pm: Launching emdctl with -Xmx1024m
2446 :: Thu Oct 29 09:01:37 2015::AgentStatus.pm:emdctl run_autotune returned 0
2438 :: Thu Oct 29 17:01:29 2015::AgentLifeCycle.pm: Launched the watchdog process pid=2446
2438 :: Thu Oct 29 17:01:29 2015::AgentLifeCycle.pm: StartCEMD start retryCount=120
Clock is moving to 09.01.32 from 17.01.30
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 |