Can not connect from different machine


(tomer zaks) #1

From some reason after building new ES machine I am unable to connect to it from a different machine. 'While checking connection between machines using ping shows that they are connected

Here is my yml:

/# ========= ============== Elasticsearch Configuration =========================
/#
/# NOTE: Elasticsearch comes with reasonable defaults for most settings.
/#       Before you set out to tweak and tune the configuration, make sure you
/#       understand what are you trying to accomplish and the consequences.
/#
/# The primary way of configuring a node is via this file. This template lists
/# the most important settings you may want to configure for a production cluster.
/#
/# Please consult the documentation for further information on configuration options:
/# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
/#
/# ---------------------------------- Cluster -----------------------------------
/#
/# Use a descriptive name for your cluster:
/#
cluster.name: new
/#
/# ------------------------------------ Node ------------------------------------
/#
/# Use a descriptive name for the node:
/#
/#node.name: node-1
/#
/# Add custom attributes to the node:
/#
/#node.attr.rack: r1
/#
/# ----------------------------------- Paths ------------------------------------
/#
/# Path to directory where to store the data (separate multiple locations by comma):
/#
/#path.data: /path/to/data
/#
/# Path to log files:
/#
/#path.logs: /path/to/logs
/#
/# ----------------------------------- Memory -----------------------------------
/#
/# Lock the memory on startup:
/#
bootstrap.system_call_filter: false
/#
/#bootstrap.memory_lock: false
/#
/# 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.1.116
/#network.host: localhost
network.bind_host: 0
/#
/# 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: 3
/#
/# 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

When checking what port ES is listening to:

sudo lsof -iTCP -sTCP:LISTEN | grep elasticsearch

I get:

java    1375 elasticsearch  100u  IPv6  12397      0t0  TCP *:vrace (LISTEN)
java    1375 elasticsearch  108u  IPv6  12467      0t0  TCP *:wap-wsp (LISTEN)

#Here is connection from localhost:

#Here is connection from other machine:

           curl -XGET '192.168.1.116:9200/_cluster/health?pretty'
           curl: (7) couldn't connect to host

Any help will be very appreciated


(Christian Dahlqvist) #2

Can you telnet to Elasticsearch on port 9200 from the remote machine?


(Craig Castle-Mead) #3

Given you've changed the network.host and can connect to the right IP locally, it appears as if the issue is most likely related to a firewall or network level issue.

Firewall - eg: if it's and AWS EC2 box, check the Security Group and ensure that TCP:9200 is allowed from your source IP

Network level - eg: if it's a Virtualbox or a VM, check that the guest network is in bridged mode and not NAT mode

If you can provide some more information about how your source and destination machines are configured there might be some more specific checks people can feed back with for you


(tomer zaks) #4

Yes this was a very silly mistake of mine!

This really was a new machine that I built and forgot to change the configuration.


(Craig Castle-Mead) #5

Happens to all of us! :slight_smile:


(system) #6

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