I am trying out with APM,
In have two test instance of the same versions, OS and mode of installation
one in my virtualbox
one in my aws account
In virtualbox for making apm-service available to all, I edited the
I restart it works fine, I am able to restart the service, status shows the apm-server running and I am able to telnet to the service 192.168.10.104:8200, Good
But for a demo I preparing at my aws account (I am aware of the security group and had done the necessary settings)
then I stop the service and start, check the service, then service status shows it is down
when I check the logs I see
Sep 16 13:02:43 ip-1XX-1X-1x-1xx apm-server: 2019-09-16T13:02:43.018Z#011ERROR#011[beater]#011beater/beater.go:191#011failed to listen:listen tcp 1X.1X.x.x:8200: bind: cannot assign requested address
This IP “ 1X.1X.1x.1xx” is the elasticIP address given to the instance
APM Server version:
APM Agent language and version:
Original install method (e.g. download page, yum, deb, from source, etc.) and version:
Fresh install or upgraded from other version?
Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
Steps to reproduce:
- install in AWS ec2 instance
- assign elastic IP
- edit the
/etc/apm-server/apm-server.yml and give the "host: "elaticIP:8200"
- restart it and check the status
Note:- from morning on wards I am only doing this, it is not related with the aws security group or acl or anything, because I am checking for the service running or not with localhost:8200 it works, but wont work with the assigned elasticIP address assigned to the instance