In this Document

Applies to:

Symptoms

Checked for relevance on 29-JUL-2010

During installation of any Grid Control 10.2.0 install type on RHEL4, the Agent Configuration Assistant fails.

In spite of the installer display of the AgentCA failure, the agent product is started, targets have been properly discovered, targets have been displayed in the Grid Control view and routine uploads of data are succeeding.

The agent is not secured and the OMS was not locked as installed.

The logging shows the following:

To screen:
==========
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.


from installActions<>.log:
==========================
INFO: Command = oracle.sysman.emcp.agent.AgentPlugIn

Performing free port detection on host= 
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=

stty: standard input: Invalid argument
stty: standard input: Invalid argument
STDOUT=

Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Enter Agent Registration password :
Agent is already 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... Done.


INFO: Configuration assistant "Agent Configuration Assistant" failed


From oracle.sysman.top.agent_<>.log:
============================
INFO: oracle.sysman.top.agent:Internal PlugIn for {Micro Step state:step:1:configuration in CfmAggregateInstance: oracle.sysman.top.agent:10.2.0.1.0:common:family=CFM:oh=/u01/app/oracle/agent10g:label=0} failed with an unhandled exception:
java.lang.Exception:
The Management Agent Configuration Assistant has failed. The following failures were recorded:


STDERR=

stty: standard input: Invalid argument
stty: standard input: Invalid argument
STDOUT=

Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Enter Agent Registration password :
Agent is already 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... Done.

   at oracle.sysman.emcp.agent.AgentPlugIn.startProcessing(AgentPlugIn.java:242)
   at oracle.sysman.emcp.agent.AgentPlugIn.invoke(AgentPlugIn.java:217)
   at oracle.sysman.emCfg.core.PerformMicroStep.runJavaClass(PerformMicroStep.java:509)
   at oracle.sysman.emCfg.core.PerformMicroStep.executeMicroStep(PerformMicroStep.java:121)
   at oracle.sysman.emCfg.core.ActionPerformer.performMicroStep(ActionPerformer.java:917)
   at oracle.sysman.emCfg.core.ActionPerformer$Performer.run(ActionPerformer.java:1038)

INFO: oracle.sysman.top.agent:The plug-in Agent Configuration Assistant has failed its perform method

Changes

Installation of the Grid Control 10.2.0.1 or 10.2.0.2 agent by any means.

Cause

There is an environment parameter that has a semicolon (;) or a space ( ) in it.
This is preventing the AgentCA from completing successfully.
In one case, the problem parameters were defined as follows:

LS_COLORS=no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:
mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:
*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:
*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:
*.png=00;35:*.tif=00;35:
>>> NOTE THE MANY SEMICOLONS<
LESSOPEN=|/usr/bin/lesspipe.sh %
>>> NOTE THE SPACE<
VNCDESKTOP=:1 ()
>>> NOTE THE SPACE<

Solution

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.

In the described case, the LS_COLORS, LESSOPEN and VNCDESKTOP parameters were unset and the installer ran to completion without error.

These are default environment settings of an RHEL4/update 2 system (all packages selected) with telnet, vsftp and VNC configured to start automatically, with VNC configured to start by the user running the installation.

This issue should be resolved in the 10.2.0.3.0 version.

References