Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
01-16-2019 09:56 PM
Hi,
I'm trying to load a machine agent on CentOS machine with AppD Saas controller. When I launch the agent, it gives out an error -
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the
console.
Looking into agent .zip package downloaded, there's no log4j2.xml file; just log4j.xml.
Any suggestions??
Thanks.
Solved! Go to Solution.
01-17-2019 09:11 PM
Hi Amol,
Thanks for posting the question on the Community.
I am sorry to say that this is a known bug for 4.5.x machine agent.
I will keep the progress information updated here in that case.
As the work around, could you try to add below option in machine agent command?
-Dappdynamics.agent.log4j2.disabled=true
If it does not work, could you try to use 4.4.X version machine agent?
Let me know if this helped you.
Many thanks,
Naoto
Thanks,
Naoto Yamamoto
05-22-2019 02:51 PM
I have this problem as well. Passing "-Dappdynamics.agent.log4j2.disabled=true" through the command line doesn't seem to have any effect:
$MACHINE_AGENT_HOME/jre/bin/java -jar $MACHINE_AGENT_HOME/machineagent.jar -Dappdynamics.agent.log4j2.disabled=true Using Java Version [1.8.0_162] for Agent Using Agent Version [Machine Agent v4.5.9.2096 GA compatible with 4.4.1.0 Build Date 2019-03-19 19:13:12] [INFO] Agent logging directory set to: [/home/ec2-user/machine-agent] ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
How does one get download verison 4.4 of the machine agent?
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form