Unable to upgrade EPAgent 3.3 to 3.4 on API Gateway

book

Article ID: 197084

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management

Issue/Introduction

We get an exception when we try to install EPAgent to one of our API Gateways.


[[email protected]<hostname>]# ./install_epagent.sh
Enter path for EPAgent tar file: [./]
Enter name of EPAgent tar file: [EPAgent10.5.2.15unix.tar]
Enter EPAgent TCP port: [9090]
Enter EPAgent HTTP port: [9080]
Enter EPAgent OS_RESOURCE delay (in seconds): [60]
Enter EPAgent OPERATING_STATUS delay (in seconds): [900]
Enter Hostname:Port for Enterprise Manager (APM Server): [localhost:5001] <hostname>:5001
Does this Gateway Node have a Mysql Node: [false] true
MySQL_NODE : true
Enter Hostname for Mysql Server: [localhost] <hostname>
Enter Database name for Mysql: [ssg]
Enter Port for Mysql port: [3306]
Enter Gateway DB user name: [gateway]
Enter Gateway DB user password: [Mandatory,Please provide password] --------
=> Checking for .//EPAgent10.5.2.15unix.tar: OK
=> Found user apmusr
=> Creating home directory: /opt/apm105: OK
=> Extracting the archive: OK
=> Creating apim plugin directory: OK
OK
OK
=> Installing OS perl scripts:
==> gatewayOperatingStatus.pl: OK
==> gatewayOSResource.pl: OK
=> Modifying IntroscopeEPAgent.properties:
==> Setting introscope.epagent.config.networkDataPort to 9090: OK
==> Setting introscope.epagent.config.httpServerPort to 9080: OK
==> Setting introscope.epagent.plugins.stateless.names to OS_RESOURCE,OPERATING_STATUS: OK
==> Adding configurations for OS_RESOURCE and OPERATING_STATUS: OK
==> Adding configurations for Agent Properties OK
==> Checking for Enterprise Manager configuration style: 5.6.1
==> Setting up Enterprise Manager connection(s):===> Setting agentManager.url.1 to <hostname>:5001: OK
=> Changing ownership of files in /opt/apm105/epagent: OK
=> Determining home directory for apmusr: OK
=> Modifying /home/apmusr/.bash_profile:
==> JAVA_HOME already set in /home/apmusr/.bash_profile
==> $JAVA_HOME/bin already in PATH
=> Setting EPAgent to start on boot:
==> Installing modified EPACtrl.sh (EPACtrl-SSG.sh): OK
==> Found epagent in /etc/init.d. Not installing
==> Running chkconfig to start in boot: OK
epagent         0:off   1:off   2:off   3:on    4:on    5:on    6:off
=> Starting epagent:
cat: /opt/apm105/epagent/epa.pid: No such file or directory
==> PID=
==> Waiting for epagent to open ports: .Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
.Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
.

.

.
.Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
FAIL
ERROR: Could not find open EPAgent ports
[[email protected]<hostname>]#

Environment

Release : 10.7.0

Component : APM Agents

Resolution

The reason the agent would not start was because the /etc/init.d/epagent file had the statement below commented out.

su - $USER -c "$EPACTRL start"

Un-comment the above line in /etc/init.d/epagent file.