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!

Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps

It’s Monday morning, and your phone is buzzing with alert escalations – your customer-facing portal is running ...

What’s New in Splunk Observability – September 2025

What's NewWe are excited to announce the latest enhancements to Splunk Observability, designed to help ITOps ...

Fun with Regular Expression - multiples of nine

Fun with Regular Expression - multiples of nineThis challenge was first posted on Slack #regex channel ...