My Oracle Support Banner

OMC: Starting Cloud Agent Is Failed With Error "NET HELPMSG 3534" (Doc ID 2585173.1)

Last updated on MARCH 02, 2021

Applies to:

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

Symptoms

omcli start agent is failing with error "NET HELPMSG 3534"

 From AgentInstall_20190904144428.log

2019-09-04 14:46:26 INFO AgentSetupHandler:511 - Starting Cloud Agent...
2019-09-04 14:46:26 DEBUG ProcessBuilderUtil:63 - Command to execute is {<AGENT_INST>\bin\omcli.bat start agent}
2019-09-04 14:46:53 DEBUG ProcessBuilderUtil:109 - Command {<AGENT_INST>\bin\omcli.bat start agent} execution completed with exit value [2] and ouput as
{Oracle Management Cloud Agent
Copyright (c) 1996, 2019 Oracle Corporation. All rights reserved.
OMCAgent191220 ???????????? ......
OMCAgent191220 ?????????????

??????§Ò????¦Ê¦Ä???

????? NET HELPMSG 3534 ?????????????

2019-09-04 14:46:53 WARN JsonUtil:88 - errormessages_zh_CN.json file does not exists, will check for the default file [errormessages_en_US.json].
2019-09-04 14:46:53 DEBUG JsonUtil:105 - Error messages read successfully.

2019-09-04 14:46:53 DEBUG ExceptionUtil:326 - Error Messages successfully loaded to memory.
2019-09-04 14:46:53 ERROR AgentInstallerMain:499 -
[OMCAGNT-0000]: The execution of command [<AGENT_INST>\bin\omcli.bat start agent] resulted in error with exit code [2].

oracle.sysman.installer.exception.AgentSetupException: The execution of command [<AGENT_INST>\bin\omcli.bat start agent] resulted in error with exit code [2].

 From emagent.nohup

--- EMState agent
----- 2019-09-04 14:46:51,985::964::Mismatch detected between timezone in env (Picked up JAVA_TOOL_OPTIONS: -Djava.vendor="Sun Microsystems Inc.") and in <AGENT_INST>/sysman/config/emd.properties (Asia/Shanghai). Forcing value to latter.. -----
----- 2019-09-04 14:46:51,985::964::The agentTZRegion value in <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. -----

From emctl.log

968 :: 2019-09-04 14:45:56,570::AgentStatus.pm:emdctl status agent returned 1
968 :: 2019-09-04 14:45:56,570::Status Output:Status agent Failure:Unable to connect to the agent at https://<hostname>:port/emd/lifecycle/main/ [Connection refused: connect]

Picked up JAVA_TOOL_OPTIONS: -Djava.vendor="Sun Microsystems Inc."

1524 :: 2019-09-04 16:02:58,915::Cleaning up agent command lock
1524 :: 2019-09-04 16:02:58,915::AgentCommandLock:closed file handle of emctl lockfile
408 :: 2019-09-04 16:02:59,320::fetched EMAAS MODE=lama from emd.properties
408 :: 2019-09-04 16:02:59,403::TZ = Asia/Shanghai, Read = Asia/Shanghai. Found = 1.
408 :: 2019-09-04 16:02:59,976::validateTZAgainstAgent: Asia/Shanghai, Picked up JAVA_TOOL_OPTIONS: -Djava.vendor="Sun Microsystems Inc."
408 :: 2019-09-04 16:02:59,977::_checkPastTZMappings: Asia/Shanghai Picked up JAVA_TOOL_OPTIONS: -Djava.vendor="Sun Microsystems Inc."

 

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


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