Elastic search is running BUT I GOT curl: (7) Failed to connect to 127.0.0.1 port 9200: Connection refused

Elastic Stack Elasticsearch
1

[root@ip-XXX-XX-XX-XXX elasticsearch]# sudo /etc/init.d/elasticsearch restart
Stopping elasticsearch: [FAILED]
Starting elasticsearch: [ OK ]
[root@ip-XXX-XX-XX-XXXelasticsearch]# curl -XGET "127.0.0.1:9200"
curl: (7) Failed to connect to 127.0.0.1 port 9200: Connection refused

2

Hi,

What's your configuration file ? (/etc/elasticsearch/elasticsearch.yml I believe)
How long have you waited after trying to curl elasticsearch ? Try to wait ~60sec before curling after starting it (curl 127.1:9200 is a shorter way to proceed btw)
What's in your log files ?

3

Path to log files:

path.logs: /var/log/elasticsearch

----------------------------------- Memory -----------------------------------

Lock the memory on startup:

#bootstrap.memory_lock: true

Make sure that the heap size is set to about half the memory available

on the system and that the owner of the process is allowed to use this

limit.

Elasticsearch performs poorly when the system is swapping the memory.

---------------------------------- Network -----------------------------------

Set the bind address to a specific IP (IPv4 or IPv6):

#network.host: 192.168.0.1

Set a custom port for HTTP:

#http.port: 9200

For more information, consult the network module documentation.

--------------------------------- Discovery ----------------------------------

Pass an initial list of hosts to perform discovery when new node is started:

The default list of hosts is ["127.0.0.1", "[::1]"]

#discovery.zen.ping.unicast.hosts: ["host1", "host2"]

Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):

#discovery.zen.minimum_master_nodes:

For more information, consult the zen discovery module documentation.

---------------------------------- Gateway -----------------------------------

Block initial recovery after a full cluster restart until N nodes are started:

#gateway.recover_after_nodes: 3

For more information, consult the gateway module documentation.

---------------------------------- Various -----------------------------------

Require explicit names when deleting indices:

#action.destructive_requires_name: true

network.host: 0.0.0.0

http.port: 9200

this is configuration file i know it should be different but i only found this way to check and run for ES
for log i found some log files but inside is to long should i put here ?

4

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