Troubleshooting oracle.sysman.emcp.agent.AgentPlugIn has failed error_734981.1

rongshiyuan發表於2014-08-07

Troubleshooting the 'oracle.sysman.emcp.agent.AgentPlugIn has failed' error (Doc ID 734981.1)


In this Document

Purpose
Troubleshooting Steps
References

Applies to:

Enterprise Manager Base Platform - Version 10.1.0.2 to 11.1.0.1 [Release 10.1 to 11.1]
Information in this document applies to any platform.
Enterprise Manager Grid Control - Version: 10.1.0.2 to 10.2.0.4
Checked for relevance on 29-Jul-2013

Purpose

The purpose of this document is to fast track the debugging of the "oracle.sysman.emcp.agent.AgentPlugin has failed" error.

Troubleshooting Steps

Symptoms:

Grid control is failing at the agent installation with the following error:
The installActions.log files shows:
INFO: Command = oracle.sysman.emcp.agent.AgentPlugIn ... ...
Performing targets discovery and agent configuration
Command =
oracle.sysman.emcp.agent.AgentPlugIn has failed
Exception :
java.lang.Exception: 6
INFO: Configuration assistant "Agent Configuration Assistant" failed
-----------------------------------------------------------------------------
*** Starting OUICA ***
Oracle Home set to
/usr/local/oracle/product/agent10g
Configuration directory is set to
/usr/local/oracle/product/agent10g/cfgtoollogs. All xml files under the
directory will be processed
INFO: The "/usr/local/oracle/product/agent10g/cfgtoollogs/configToolFailedCommands"
script contains all commands that failed, were skipped or were cancelled.
This file may be used to run these configuration assistants outside of OUI.
Note that you may have to up date this script with passwords (if any)
before executing the same.
-----------------------------------------------------------------------------
SEVERE: OUI-25031:Some of the configuration assistants failed. It is strongly
recommended that you retry the configuration assistants at this time. Not successfully
running any "Recommended" assistants means your system will not be correctly configured.
1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the failures.
2. Fix the errors causing these failures.
3. Select the failed assistants and click the 'Retry' button to retry them.
-------------------------------------------------------------------------

LOG FILES:
The best log files to get the root cause of these failures are the following:

/cfgtoollogs/cf**/oracle.sysman.top.agent_log/cfgtoollogs/cf**/CfmLogger_.log/cfgtoollogs/oui/installActions.log

The following are the most common reasons for this failure:

1. System Pre-requisites for installing the Agent are not met. In order to check whether you meet the required system pre-requisites, please refer to the "System Requirements" section in the following documents:

Enterprise Manager Grid Control Quick Installation Guide for Linux x86

Enterprise Manager Grid Control Quick Installation Guide for Solaris (SPARC)

Enterprise Manager Grid Control Quick Installation Guide for HP-UX PA-RISC (64-bit)

Enterprise Manager Grid Control Quick Installation Guide for Windows

Enterprise Manager Grid Control Quick Installation Guide for AIX 5L Based Systems (64-bit)

Enterprise Manager Grid Control Quick Installation Guide for Linux x86-64

Enterprise Manager Grid Control Quick Installation Guide for HP-UX Itanium

2. Ensure that Grid Control is not being installed into a symbolic link directory (Refer to Note 352357.1)

3. If you receive the following error:

'fuser' is used by OPatch to detect active processes. So presence of 'fuser' executable is essential. It should be present in /sbin or /usr/sbin or should be present in the PATH. Another workaround is to set OPATCH_NO_FUSER environment variable to FALSE. This will bypass the active process checks by OPatch.

Then perform the following workaround (Refer to Note 352507.1):

Cleanup from the old install of the 10.2 Grid.
set OPATCH_NO_FUSER environment variable to FALSE.
Install the 10.2 Grid with OPATCH_NO_FUSER environment variable to FALSE

4. Ensure that there are no environment parameters which contain a semicolon or space in the value. If so then remove or alter any user environment parameters which contain a semicolon or space in the value. This can be done in the session which runs the installer and does not need to be permanent (Note 380507.1).

5. The agent does not upload information to OMS (Refer to Note 367355.1)

emagent.trc contains the following:

2006-04-03 10:57:27 Thread-118517 ERROR http: 258:
Unable to initialize ssl connection with server, aborting connection attempt 2006-04-03 10:57:27
Thread-118517 ERROR pingManager: nmepm_pingReposURL:
Cannot connect to https://:1159/em/upload: retStatus=-1 2006-04-03 10:57:27
Thread-118517 ERROR ssl: 258: Common Name = Does not Match Hostname =

Solution:

a. Stop the agent
AGENT_HOME/bin > emctl stop agent

b. Unsecured the agent
AGENT_HOME/bin >emctl unsecure agent

c. Resecure the agent
AGENT_HOME/bin > emctl secure agent

d. Check the agent status
AGENT_HOME/bin > emctl status agent

e. Check and correct the hostname in $AGENT_HOME/sysman/config/emd.properties for: REPOSITORY_URL

f. Restart the agent

6. Ensure that the hostname entry in /etc/hosts does not have any TABs in the line and is correctly formatted as follows (Refer to Note 358640.1):

a. ,
e.g. 192.168.0.2 myserver.mydomain.com myserver
(Also ensure that there are no duplicating entries for either the host or the IP
address that the hostname is preferably in lowercase). or In the given /etc/hosts
there are two entries for same IP, you should keep only one.

b. Rerun Agent configuration assistant by using either of the following 2 methods:
b.1 If Possible clicked on the "Retry" button in the OUI. or
b.2 Retry the failed Agent configuration assistant by running the following command:
/oui/bin/runConfig.sh ORACLE_HOME= ACTION=configure MODE=perform
b.2.1 or alternatively run agent reconfigure to complete the configuration assistant:

agentca -f
NOTE: If fails please upload files from /sysman/log/*
and/cfgtoollogs/oui/configActions*.log

7. While installing the agent you get the following error due to an invalid agent registration password being provided (Refer to Note 393383.1):

 

Oracle Enterprise Manager 10g Release 10.2.0.2.0.
Copyright (c) 1996, 2006
Oracle Corporation. All rights reserved.
Enter Agent Registration password :
Agent successfully stopped... Done.
Securing agent... Started.
Requesting an HTTPS Upload URL from the OMS... Done.
Requesting an Oracle Wallet and Agent Key from the OMS... Failed.
Invalid Agent Registration Password. The Agent has not been secured.
INFO: Configuration assistant "Agent Configuration Assistant" failed

Solution:

Either of the following 3 methods should work:

a. Retry the agent installation using the correct password

b. If the password is unknown or it is desired to change it, access Grid Control's
Setup link and then the Registration Password link on the left of the resulting page,
and use the Edit option in order to change the securing password, then retry the
agent installation with the one entered. Note that the second option may result in
access problems with existing and properly secured agents. It is also possible to
unlock the OMS, verify the agent is installed and uploading properly via http and then
secure at a later time to allow uploading via https.

c. But a better option is to click on the "Add Registration Password" button in
Grid Control's "Registration Password" link. This way you will simply define a
new *additional* registration password which can be used to secure the agent.

8. Agent configuration failed while securing the agent with following errors in installActions*.log

Performing free port detection on host=hostname Securing the agent
Performing targets discovery and agent configuration
Starting the agent Command = oracle.sysman.emcp.agent.AgentPlugIn has failed Exception :
java.lang.Exception: The Management Agent Configuration Assistant has failed.
The following failures were recorded:
STDERR= Enter Agent Registration password :
*********
STDOUT= Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent successfully stopped... Done. Securing agent... Started.
Requesting an HTTPS Upload URL from the OMS... Done.
Requesting an Oracle Wallet and Agent Key from the OMS... Done.
Check if HTTPS Upload URL is accessible from the agent... Failed.
The Agent has not been secured. INFO: Configuration assistant
"Agent Configuration Assistant" failed

Solution:

Ensure that port 1159 is opened for communication in the firewall (not just port 4889). The port that is opened (4889) is for unsecure communication, if the agent is secured the REPOSITOR_URL will change to upload on the secure port which is 1159 by default.
+ The agent will be started in the non secure mode. In order to start the agent in secure mode you need to open the port 1159. 1159 is the default secure port.

Check what is the https port in your case.

OMS_HOME/bin/emctl secure status oms

This command will give the secure status of the OMS as well as the https
port the OMS is listening on. Once you get the https port open this port
for the agent to communicate.

+ Once the port is opened you need to resure the agent usign following steps;

1. Unlock the OMS
OMS_HOME/bin/emctl secure unlock

2. now secure the Agent
AGENT_HOME/bin/emctl secure agent

3. Check the status of the agent
AGENT_HOME/bin/emctl agent

9. "DEFAULT WEBSITE EM Website CREATION FAILED" error experienced (Refer to Note 419886.1)

Performing targets discovery and agent configuration
Command = oracle.sysman.emcp.agent.AgentPlugIn has failed
Exception : java.lang.Exception: 6
INFO: Configuration assistant "Agent Configuration Assistant" failed
From the CfmLogger_*.log: SQL*Plus: Release 10.1.0.4.2 - Production on Sat Mar 17 17:41:31 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected.
DEFAULT WEBSITE EM Website CREATION FAILED : ORA-01403:
no data found ORA-01403:
no data found
BEGIN
*
ERROR at line
1:
ORA-20999: CREATE DEFAULT WEBSITE FAILED : ORA-01403: no data found
ORA-06512: at line 224
This can happen if the machine is to slow/busy for the Agent to upload data to OMS during installation.
The log clearly says that "no data found" as the Agent was not able to upload data during the configuration phase.

Solution:

a. Backup the following files:
$AGENT_HOME/sysman/emd/targets.xml
$AGENT_HOME/sysman/config/emd.properties

b. Then run "$AGENT_HOME/bin/agentca -f" command.
(Under heavy load it may take some time to create the website target)

10. "hosttgt.out" error (Refer to Note 353836.1)

Performing targets discovery and agent configuration
Command = oracle.sysman.emcp.agent.AgentPlugIn has failed
Exception :
java.lang.Exception: OPS:Exception while processing cluster node=linux1.
Failed to copy file $ORACLE_HOME/agent10g/sysman/install/hosttgt.out to destination
$ORACLE_HOME/agent10g//sysman/emd/hosttgt.out.
ExceptionMessage=scp:$ORACLE_HOME/agent10g/sysman/install/hosttgt.out:
No such file or directory :failed. Terminating...

Cause: SSH latency is not allowing the push of the agent configuration to the other nodes in this rac cluster.

Solution:

a. Install 10.2 Grid control Agents on local storage - shared Agent installations on SAN devices are not currently supported.

b. Install on a cluster that is not experiencing any ssh latency problems.
Consider using a faster, more robust cluster hardware environment. Consult with your system administrator on how to check for ssh latency problems.

c. Remove all spaces (" "), semicolons (";") and double colons ("::") from the environment variable values of the user initiating the agent installation. This change is only required for the duration of the installation session itself. (refer Note.352140.1)

11. "Failed to Allocate Free Port" error

Command = oracle.sysman.emcp.agent.AgentPlugIn has failed
Exception : java.lang.Exception: Failed to allocate port = Failed to allocate free
Enterprise Manager Central Console Port from Default Range 1830 to 1849.
Please free a port from the Range and re-try the installation.

Solution:

Ensure the your "/etc/services" file does not contain any ports that are in the range of 1830 to 1849 and being used by other services. If so then work with your sys admin to free a port for the agent plugin to work. Then click on re-try in the OUI for Agent Configuration Assistant. NOTE: This error can also occur if there is an incorrect entry or IP address in the machine's hosts file.

12. "stty: tcgetattr: A specified file does not support the ioctl system call" error :

Configuration assistant "Agent Configuration Assistant" failed.
From installActions.log
Command = oracle.sysman.emcp.agent.AgentPlugIn has failed The following exception occurred:
java.net.UnknownHostException: : . . stty: tcgetattr:
A specified file does not support the ioctl system call.

Solution:

a. Check for read permissions on /etc/services for the installing user.
b. Check for correct entries in /etc/hosts.

13. "Host discovery failed" error.

The Management Agent Configuration Assistant has failed. The following failures were recorded:
configureAgent:discovery on non RAC: Host discovery failed. Oracle Database discovery failed.
INFO: oracle.sysman.top.agent:Internal PlugIn for
{Micro Step state:step:1: configuration in CfmAggregateInstance: oracle.sysman.top.agent:10.2.0.2.0:
common:family=CFM:oh=/aplicaciones/oracle/grid/agent10g:label=2} failed with an unhandled exception: 
java.lang.Exception:

Cause: Host Discovery Fails due some entries in the /etc/host file needing to be corrected.

Set the ORACLE_HOSTNAME environment variable to the correct host value.
Correct entries in the /etc/hosts file This will allow the agent configuration assistant
to complete successfully and upload its data correctly to the OMS.

14. How to Configure Grid Control Agents to Monitor Virtual Hostname in HA environments
Please refer to Note 406014.1

References

NOTE:352140.1 - Problem: 10.2.0.1 Agent install for RAC fails with: Failed to copy file hosttgt.out
NOTE:352357.1 - Problem: Agent Installation Fails with Error 'Exception: java.lang.Exception: 6' and 'OUI-25031' Due to Symbolic Link
NOTE:352507.1 - Problem: Agent Installation Fails with Error 'OUI-25031' Due to OPATCH_NO_FUSER Setting
NOTE:353836.1 - Problem: Install 10.2 Grid Agent On Rac Cluster Nodes Fails When Copying Hosttgt.Out to Secondary Nodes of the Cluster.
NOTE:358640.1 - Problem: Agent Installation Fails with Error 'Exception : java.lang.Exception: 6' Due to Improper Hosts File Entry
NOTE:367355.1 - Problem: Agent Installation Fails with Error 'Exception : java.lang.Exception: 6'
NOTE:380507.1 - Problem: Agent Installation Fails with Error 'OUI-25031' Due to Environment Settings
NOTE:393383.1 - Problem: Agent Installation Fails with Error 'OUI-25031' Due to Incorrect Secure Password
NOTE:406014.1 - How to Configure Grid Control Agents to Monitor Virtual Hostname in HA environments
NOTE:419886.1 - Problem: Agent Installation Fails with Error 'Exception : java.lang.Exception: 6' Due to Slow Response Time

來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/17252115/viewspace-1247131/,如需轉載,請註明出處,否則將追究法律責任。

相關文章