My Oracle Support Banner

EM 12c, EM 13c : 新しい Agent のデプロイが "emctl start agent on host Failed" で失敗する (Doc ID 2277398.1)

Last updated on JULY 22, 2019

適用範囲:

Enterprise Manager Base Platform - バージョン 12.1.0.1.0 以降
この文書の内容はすべてのプラットフォームに適用されます。
本文書利用上のご注意
  本文書は英語の文書 <Document 2177365.1> (最終メジャー更新日: 2016年12月19日) の日本語翻訳版です。
  英語の文書のメジャー更新に応じて本文書を随時更新いたします。

現象

EM コンソールよりの Agent デプロイが以下のエラーで失敗します:

Execution of command <AGENT_BASE_DIR>/agent_inst/bin/emctl start agent on host Failed 

Error Message:Not Available
Exit Code :1

Fix the cause of the error and retry the operation (or) manually run the following commands on the remote host
<AGENT_BASE_DIR>/agent_inst/bin/emctl start agent
<AGENT_BASE_DIR>/agent_inst/bin/emctl config agent addinternaltargets

-  ターゲットホストでの Agent の手動の起動も失敗します:

-  <AGENT_INST>/sysman/log/emagent.nohup は Agent が起動時にクラッシュしていることを出力します:

----- Sat Aug 20 07:31:00 2016::32047112::Auto tuning the agent at time Sat Aug 20 07:31:00 2016 -----
----- Sat Aug 20 07:31:03 2016::32047112::Finished auto tuning the agent at time Sat Aug 20 07:31:03 2016 -----
----- Sat Aug 20 07:31:03 2016::32047112::Launching the JVM with following options: -Xmx128M -server -Djava.security.egd=file:
///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -Xgcpolicy:gencon -----
----- Sat Aug 20 07:31:03 2016::32047112::Agent Launched with PID 33816634 at time Sat Aug 20 07:31:03 2016 -----
----- Sat Aug 20 07:31:03 2016::33816634::Time elapsed between Launch of Watchdog process and execing EMAgent is 6 secs -----
----- Sat Aug 20 07:31:03 2016::32047112::Previous Thrash State(-1,-1) -----
2016-08-20 07:31:03,899 [1:main] WARN - Missing filename for log handler 'wsm'
2016-08-20 07:31:03,929 [1:main] WARN - Missing filename for log handler 'opss'
2016-08-20 07:31:03,933 [1:main] WARN - Missing filename for log handler 'opsscfg'
----- Sat Aug 20 07:31:35 2016::32047112::Checking status of EMAgent : 33816634 -----
----- Sat Aug 20 07:36:35 2016::32047112::Checking status of EMAgent : 33816634 -----
----- Sat Aug 20 07:36:35 2016::32047112::Abnormality reported for EMAgent : 33816634 -----
----- Sat Aug 20 07:36:35 2016::32047112::Debugging component EMAgent -----
----- Sat Aug 20 07:36:35 2016::generate first thread dump file for diagnosis -----
JVMDUMP039I Processing dump event "user", detail "" at 2016/08/20 07:36:35 - please wait.
JVMDUMP032I JVM requested Java dump using '<AGENT_BASE_DIR>/agent_inst/sysman/emd/javacore.20160820.073635.33816634.0001.txt' in response to an event
JVMDUMP010I Java dump written to <AGENT_BASE_DIR>/agent_inst/sysman/emd/javacore.20160820.073635.33816634.0001.txt
JVMDUMP013I Processed dump event "user", detail "".
----- Sat Aug 20 07:36:45 2016::generate second thread dump file for diagnosis -----
JVMDUMP039I Processing dump event "user", detail "" at 2016/08/20 07:36:45 - please wait.
JVMDUMP032I JVM requested Java dump using '<AGENT_BASE_DIR>/agent_inst/sysman/emd/javacore.20160820.073645.33816634.0002.txt' in response to an event
----- Sat Aug 20 07:36:45 2016::generate Threads.33816634lsof.1 for diagnosis -----
----- Attempting to kill EMAgent : 33816634 -----
----- Sat Aug 20 07:36:50 2016::32047112::EMAgent exited at Sat Aug 20 07:36:50 2016 with signal 9 -----
----- Sat Aug 20 07:36:50 2016::32047112::EMAgent either hung or in abnormal state. -----

 

原因

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


本書の内容
現象
原因
解決策
参照情報

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