Java (Java Agent, Installation, JVM, and Controller Installation)

cancel
Showing results for 
Search instead for 
Did you mean: 

JavaAgent start failed on Docker-Container

SOLVED

JavaAgent start failed on Docker-Container

Hello together,

 

I created a Docker container with the Java AppAgent (4.5.0.23604) inside. Also I uncomment the line "<appender-ref ref="AgentLogAppender"/>" in the file log4j-unknown.xml and the line "<AppenderRef ref="Console"/>" in the file log4j2-unknown.xml.

The container started in a kubernetes environment.

 

Logoutput:

Full Agent Registration Info Resolver using node name [unknown]
Install Directory resolved to[/opt/appdynamics]
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
[Thread-0] Fri Aug 24 11:39:51 CEST 2018[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver is running
[Thread-0] Fri Aug 24 11:39:51 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_APPLICATION_NAME] for application name [docker-poc]
[Thread-0] Fri Aug 24 11:39:51 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_TIER_NAME] for tier name [meins-navigation]
[Thread-0] Fri Aug 24 11:39:51 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [false]
[Thread-0] Fri Aug 24 11:39:51 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [false]
[Thread-0] Fri Aug 24 11:39:51 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using application name [docker-poc]
[Thread-0] Fri Aug 24 11:39:51 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using tier name [meins-navigation]
[Thread-0] Fri Aug 24 11:39:51 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using node name [unknown]
[Thread-0] Fri Aug 24 11:39:51 CEST 2018[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver finished running
[Thread-0] Fri Aug 24 11:39:51 CEST 2018[INFO]: AgentInstallManager - Agent runtime directory set to [/opt/appdynamics/ver4.5.0.23604]
[Thread-0] Fri Aug 24 11:39:52 CEST 2018[INFO]: AgentInstallManager - Agent node directory set to [unknown]
[Thread-0] Fri Aug 24 11:39:52 CEST 2018[INFO]: JavaAgent - Using Java Agent Version [Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release]
[Thread-0] Fri Aug 24 11:39:52 CEST 2018[INFO]: JavaAgent - Running IBM Java Agent [No]
Could not start Java Agent because unable to determine Tier Name or Node Name
Agent Logging Directory [/opt/appdynamics/ver4.5.0.23604/logs/unknown]
2018-08-24 11:39:52,869 INFO Log4j appears to be running in a Servlet environment, but there's no log4j-web module available. If you want better web container support, please add the log4j-web JAR to your web archive or server lib directory.
2018-08-24 11:39:52,922 ERROR Cannot access RandomAccessFile {}) java.io.FileNotFoundException: /opt/appdynamics/ver4.5.0.23604/logs/unknown/agent.2018_08_24__11_39_52.log (No such file or directory)

 

What am I doing wrong here?

 

With kind regards

Raphael

 

JavaAgent start failed on Docker-Container
1 REPLY 1
Employee

Re: JavaAgent start failed on Docker-Container

Hi Raphael,
Nodename seems to be missing in the above code.
-Dappdynamics.agent.nodeName=<node name> This property seems to be missing when starting the Java Agent.
Could you try adding this property and running the code again. May be this could help.

Regards,
Megha


Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.