My Oracle Support Banner

OMC Agent Service Could Not Start - Mismatch Detected Between Timezone in Env (Doc ID 2479341.1)

Last updated on MARCH 14, 2021

Applies to:

Oracle Management Cloud - Version N/A and later
Information in this document applies to any platform.

Symptoms

Agent version: 1.32.
Platform: Windows

OMC Agent service is not starting and following errors are seen in the agent log.


<AGENT_INST>\sysman\log\emagent.nohup
=============
--- EMState agent
----- 2018-11-09 17:21:26,150::1108::Auto tuning the agent at time 2018-11-09 17:21:26,150 -----
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Invalid maximum heap size: -Xmxm
----- 2018-11-09 17:21:26,180::1108::Finished auto tuning the agent at time 2018-11-09 17:21:26,180 -----
----- 2018-11-09 17:21:26,193::1108::Launching the JVM with following options: -server -Djava.security.egd=file:///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops -----
----- 2018-11-09 17:21:26,209::1108::Time elapsed between Launch of Watchdog process and execing EMAgent is 1 secs -----
----- 2018-11-09 17:21:26,209::1108::Agent Launched with PID 1788 at time 2018-11-09 17:21:26,209 -----
----- 2018-11-09 17:21:26,210::1108::Previous Thrash State(-1,-1) -----
2018-11-09 17:21:27,140 [1:main (@ 2018-11-09 17:21:27 UTC)] WARN - Missing filename for log handler 'opss'
2018-11-09 17:21:27,172 [1:main (@ 2018-11-09 17:21:27 UTC)] WARN - Missing filename for log handler 'wsm'
2018-11-09 17:21:27,172 [1:main (@ 2018-11-09 17:21:27 UTC)] WARN - Missing filename for log handler 'opsscfg'
Terminating on signal SIGTERM(15)
--- EMState agent
----- 2018-11-10 07:17:27,557::1064::Mismatch detected between timezone in env (Asia/Singapore) and in c:\OMC\agent_inst/sysman/config/emd.properties (GMT). Forcing value to latter.. -----
----- 2018-11-10 07:17:27,557::1064::The agentTZRegion value in c:\OMC\agent_inst/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(<agent_name>, <new_tz_rgn>) to get the value propagated to repository. -----

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.