DX Application Performance Management

Hi All,

I am following below link to install epagent on linux machine.

Installing EPAgent on Policy Server and Web Agents (Windows and Linux) - CA APM for CA SSO - 13.0 - CA Technologies Docu… 

In above document one parameter is 

introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT= <apm SERVER Machine IP>

But I am not getting above parameter in my IntroscopeEPAgent.properties file.  I can see below parameter in my IntroscopeEPAgent.properties file.

agentManager.url.1=localhost:5001

Epagent Version : EPAgent10.7.0.90

Can someone help me with correct instructions to modify properties file.

Regards,

Vivek Thakur

Hi Vivek,

In EPAgent 10.7, the following property is correct :

agentManager.url.1=localhost:5001

Could you please modify the property in your IntroscopeEPAgent.properties file.

Thanks,

Takeshi

Hi Takeshi,

Thanks for reply. Other than that do we need to make any other changes in the file. And is it necessary to run EPACtrl.sh  as root user.

Hi Vivek,

You don't need any other changes in the property file.

You can run EPACtrl.sh with a user other than root user :

8. Change the owner to *** using, chown for all the files in epagent_10.x

9. Ensure the .bash_profile of the *** user has the path variable set to the Java JDK of the gateway .

10. Switch to *** user using super user .

11. Navigate to cd /opt/epagent_10.x/epagent/bin/

12. Start the agent, by executing the command:

   ./EPACtrl.sh start

Thanks,

Takeshi

Hi Takeshi,

I followed your instruction . I am getting below error while running EPACtrl.sh script.

$ ./EPACtrl.sh start
Starting CA APM Environment Performance Agent...
Waiting for CA APM Environment Performance Agent.....................
...ERROR: CA APM Environment Performance Agent has failed to start. See /opt/software/ca/EPAGENT/epagent/bin/wrapper.log for details.

Error in wrapper log:

$ cat /opt/software/ca/EPAGENT/epagent/bin/wrapper.log|grep -i "ERROR"
2018/08/07 10:00:48 | ERROR | JVM exited while loading the application.
2018/08/07 10:00:52 | ERROR | JVM exited while loading the application.
2018/08/07 10:00:52 | ERROR | Unable to start JVM: No such file or directory (2)
2018/08/07 10:00:52 | ERROR | Unable to start JVM: No such file or directory (2)
2018/08/07 10:00:57 | ERROR | JVM exited while loading the application.
2018/08/07 10:01:01 | ERROR | JVM exited while loading the application.
2018/08/07 10:01:01 | ERROR | Unable to start JV#M: No! #suWcrh AfpiPlee Rosr PdierCecitAorly# (!2#)
2018/08/07 10:01:06 | ERROR | JVM exited while loading the application.

In bash profile file there is a reference to JDK.

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/software/bea/java/jdk1.7.0_80/jre/bin:/software/bea/java/jdk1.7.0_80/jre/lib/ext
export LD_LIBRARY_PATH

Could you please help me to troubleshoot this error.

Regards,

Vivek Thakur

Hi Takeshi,

Thanks, After observing logs I am able to troubleshoot the issue.

Regards,

Vivek

Hi Vivek:

    Can you share what the logs showed you was the issue and how you were able to troubleshoot it to help others that may have this same issue. Thanks

Hal German

Hello Hallet,

From bash_profile file epagent installer was not able to pick JAVA_HOME value. So I gave JAVA_HOME value in EPAService.conf  file present under conf folder.

Added Below Lines in EPAService.conf

# Set to override the existing JAVA_HOME variable, if necessary.
set.JAVA_HOME=/software/bea/java/jdk1.7.0_80/jre/

After that I got below error in IntroscopeEPA.log  under logs folder.

8/07/18 10:18:13 AM BST [ERROR] [EPAgent] EPAgent failed to start because: Introscope EPAgent has no plugins configured and no network ports enabled. Exiting.
com.wily.introscope.epagent.IllegalConfigurationException: Introscope EPAgent has no plugins configured and no network ports enabled. Exiting.

To resolve above issue I enabled one default plugin in IntroscopeEPAgent.properties file and after this change I was able to start epagent process successfully.

Regards,

Vivek

Hi Vivek,

Good to hear you managed to resolve those problems.

The required JAVA_HOME configuration for EPAService.conf was a known problem when the *ix EPAgent running as a service was first delivered in 10.5.1: As a Java Wrapper Service, APM 10.5.1 Linux EPAgen - CA Knowledge 

It was my understanding it was going to be fixed in a later release, but it seems that is not yet been done.

Regards,

Lynn