My Oracle Support Banner

13.3 EM : Solaris Agent Failed To Start After Installation With Custom Script (Doc ID 2881563.1)

Last updated on JULY 25, 2022

Applies to:

Enterprise Manager Base Platform - Version 13.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

13.3 EM Solaris Agent failed to start

$<AGENT_INST>/bin> ./emctl start agent

Oracle Enterprise Manager Cloud Control 13c Release 3
Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved.
Starting agent .......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................failed.
Consult emctl.log and emagent.nohup in: /../agent_inst/sysman/log

$<AGENT_INST>/sysman/log/emagent.nohup has below errors

----- 2022-07-04 17:37:20,579::11110::Time elapsed between Launch of Watchdog process and execing EMAgent is 995 secs -----

Unrecognized VM option 'UseCompressedOops'

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

----- 2022-07-04 17:37:23,715::19454::Checking status of EMAgent : 11110 -----

----- 2022-07-04 17:37:23,715::19454::EMAgent exited at 2022-07-04 17:37:23,715 with return value 1. -----

----- 2022-07-04 17:37:23,716::19454::Restarting EMAgent. -----

----- 2022-07-04 17:37:24,588::19454::Auto tuning the agent at time 2022-07-04 17:37:24,588 -----

Unrecognized VM option 'UseCompressedOops'

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

----- 2022-07-04 17:37:24,706::19454::Finished auto tuning the agent at time 2022-07-04 17:37:24,706 -----

 

2022-06-27 16:20:43,921::13783::Auto tuning the agent at time 2022-06-27 16:20:43,920 -----

Unrecognized VM option 'UseLinuxPosixThreadCPUClocks'

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

----- 2022-06-27 16:20:44,028::13783::Finished auto tuning the agent at time 2022-06-27 16:20:44,028 -----

----- 2022-06-27 16:20:44,039::13783::Launching the JVM with following options: -server -Djava.security.egd=file:///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -XX:-UseLargePages -XX:+UseLinuxPosixThreadCPUClocks -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops -DHTTPClient.dontSeekTerminatingChunk=true -----

----- 2022-06-27 16:20:44,059::13783::Agent Launched with PID 27371 at time 2022-06-27 16:20:44,059 -----

----- 2022-06-27 16:20:44,059::27371::Execing EMAgent process is taking longer than expected 900 secs -----

----- 2022-06-27 16:20:44,059::27371::Time elapsed between Launch of Watchdog process and execing EMAgent is 1464 secs -----

Unrecognized VM option 'UseLinuxPosixThreadCPUClocks'

Changes

 

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
Changes
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.