Splunk AppDynamics

Cannot start Machine Agent - Could not resolve local hostname

CommunityUser
Splunk Employee
Splunk Employee

Any suggestions?

Amazon EC2 Linux server. 

$MACHINE_AGENT_HOME/jre/bin/java -jar $MACHINE_AGENT_HOME/machineagent.jar
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.
Could not start up the machine agent due to: Could not resolve local hostname
Please see startup.log in the current working directory for details.

startup.log:

[Redaced for privacy reasons]

^ Edited by @Ryan.Paredez . Please do not share or attach log files to community posts

Labels (1)
0 Karma
1 Solution

CommunityUser
Splunk Employee
Splunk Employee

I was able to resolve this issue by changing the hostname to something that resolved properly through a DNS resolution. 

View solution in original post

CommunityUser
Splunk Employee
Splunk Employee

I was able to resolve this issue by changing the hostname to something that resolved properly through a DNS resolution. 

Get Updates on the Splunk Community!

Developer Spotlight with Brett Adams

In our third Spotlight feature, we're excited to shine a light on Brett—a Splunk consultant, innovative ...

Index This | What can you do to make 55,555 equal 500?

April 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...

Say goodbye to manually analyzing phishing and malware threats with Splunk Attack ...

In today’s evolving threat landscape, we understand you’re constantly bombarded with phishing and malware ...