Failed to send join request to master on Centos7

Hi, I want to set up a ES cluster on my Centos7 pc, but there are some problems.
I have two nodes, and this is the config:
node1:

# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: Winoc_logger
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: Centos2
#
# 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.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):
#
#http.host: 192.168.0.243
network.host: 192.168.0.243
#transport.host: 127.0.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: ["192.168.0.244", "192.168.0.243"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
#discovery.zen.minimum_master_nodes: 2
#
# 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

node2:

# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: Winoc_logger
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: Centos3
#
# 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.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):
#
#http.host: 192.168.0.244
network.host: 192.168.0.244
#transport.host: 127.0.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: ["192.168.0.244", "192.168.0.243"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
#discovery.zen.minimum_master_nodes: 2
#
# 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

log:
[2018-01-15T22:04:02,596][INFO ][o.e.d.z.ZenDiscovery ] [Centos3] failed to send join request to master [{Centos2}{xRZYgk5bR1WTCdwd4rX3TA}{fVgrNRHZQwCuSKzxeLXfag}{192.168.0.243}{192.168.0.243:9300}], reason [RemoteTransportException[[Centos2][192.168.0.243:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[Centos3][192.168.0.244:9300] connect_exception]; nested: IOException[No route to host: 192.168.0.244/192.168.0.244:9300]; nested: IOException[No route to host]; ]

That's why, looks like you have networking issues.

1 Like

I check my firewalld and this is the log :

    Jan 15 11:25:21 localhost.localdomain firewalld[916]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.
    Jan 15 11:25:21 localhost.localdomain firewalld[916]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
    Jan 15 11:25:21 localhost.localdomain firewalld[916]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.
    Jan 15 11:25:21 localhost.localdomain firewalld[916]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
    Jan 15 11:25:21 localhost.localdomain firewalld[916]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.
    Jan 15 11:25:21 localhost.localdomain firewalld[916]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.

oh.... after I stop the firewall, and it can run now!

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