Not able to connect my apm-agent to my apm-server and data transfer from hosted on same server

Elastic Stack Elastic Agent
1

I have deployed elasticsearch, kibana, apm-server on same server
ip: 10.8.30.220
output for http://10.8.30.220:8200
{
"build_date": "2023-01-31T04:33:06Z",
"build_sha": "71a8b4c241eb5b4609862c8354d2aa2270f6c568",
"publish_ready": true,
"version": "7.17.9"
}
I'm getting below error
ERROR co.elastic.apm.agent.configuration.ApmServerConfigurationSource - Connection refused
2023-04-24 13:04:20,331 [elastic-apm-server-reporter] ERROR co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Error trying to connect to APM Server at http://10.8.30.220:8200/intake/v2/events. Although not necessarily related to SSL, some related SSL configurations corresponding the current connection are logged at INFO level.
2023-04-24 13:04:20,332 [elastic-apm-server-reporter] ERROR co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Failed to handle event of type JSON_WRITER with this error: Connection refused
2023-04-24 13:04:20,332 [elastic-apm-server-reporter] INFO co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Backing off for 36 seconds (+/-10%)
2023-04-24 13:04:57,311 [elastic-apm-server-reporter] ERROR co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Error trying to connect to APM Server at http://10.8.30.220:8200/intake/v2/events. Although not necessarily related to SSL, some related SSL configurations corresponding the current connection are logged at INFO level.
2023-04-24 13:04:57,311 [elastic-apm-server-reporter] ERROR co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Failed to handle event of type JSON_WRITER with this error: Connection refused
2023-04-24 13:04:57,311 [elastic-apm-server-reporter] INFO co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Backing off for 36 seconds (+/-10%)

2

Hi @Tataelastic

What ip addresses are all the server configured to listen on, 10.8.30.220, 0.0.0.0, 127.0.0.1?
My hunch is maybe the apm-server is listening on the localhost (127.0.0.1) and therefor not listening on 10.8.30.220. Baring that it could be a firewall setting (often seen with RHEL).

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.