# Coordinator node authentication problem

**URL:** <https://discuss.elastic.co/t/coordinator-node-authentication-problem/133332>\
**Category:** Elasticsearch\
**Created:** [May 25, 2018, 2:28pm UTC](https://discuss.elastic.co/t/coordinator-node-authentication-problem/133332 "2018-05-25T14:28:00Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![mkemalm](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@mkemalm](https://discuss.elastic.co/u/mkemalm)\
**Post date:** [May 25, 2018, 2:28pm UTC](https://discuss.elastic.co/t/coordinator-node-authentication-problem/133332/1 "2018-05-25T14:28:01Z")

</div>

Hi,

I have a multi-node elasticsearch installation(3 master nodes at the same time data nodes) and a coordinator node with kibana instance on it.

I executed setup\_passwords script on master node, I can authenticate with generated passwords in master and data nodes but couldn't in coordinator node. So coordinator node doesn't work. I did configuration in kibana.yml as;

```
elasticsearch.url: "http://localhost:9200"
elasticsearch.username: "kibana"
elasticsearch.password: "generated_password"

```

Authentication test;

```
$ curl -u kibana 'http://localhost:9200/_xpack/security/_authenticate?pretty'
Enter host password for user 'kibana': generated_password
{
  "error" : {
    "root_cause" : [
      {
        "type" : "security_exception",
        "reason" : "failed to authenticate user [kibana]",
        "header" : {
          "WWW-Authenticate" : "Basic realm=\"security\" charset=\"UTF-8\""
        }
      }
    ],
    "type" : "security_exception",
    "reason" : "failed to authenticate user [kibana]",
    "header" : {
      "WWW-Authenticate" : "Basic realm=\"security\" charset=\"UTF-8\""
    }
  },
  "status" : 401
}

```

Also in master node;  
`curl -X GET "localhost:9200/_nodes"`

displays node number as 3, it doesn't count coordinator node. Is it normal?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 26, 2018, 5:54am UTC](https://discuss.elastic.co/t/coordinator-node-authentication-problem/133332/2 "2018-05-26T05:54:04Z")

</div>

It sounds like the coordinator node may not have joined the cluster. What is the configuration of the coordinating node? Does `discovery.zen.ping.unicast.hosts` contain the IP addresses of all master eligible nodes?

---

<div class="post-metadata">

**Author:** ![mkemalm](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@mkemalm](https://discuss.elastic.co/u/mkemalm)\
**Post date:** [May 26, 2018, 9:48am UTC](https://discuss.elastic.co/t/coordinator-node-authentication-problem/133332/3 "2018-05-26T09:48:05Z")

</div>

Yes discovery.zen.ping.unicast.hosts contains master eligables. Coordinator node config;

```
cluster.name: elkcluster
node.name: ${HOSTNAME}
discovery.zen.ping.unicast.hosts: ["master01", "master02", "master03"]
http.port: 9200
transport.tcp.port: 9300
bootstrap.memory_lock: true
node.master: false
node.data: false
node.ingest: false
node.ml: false
search.remote.connect: false
path:
  data:
    - /confdir
path.logs: /var/log/elasticsearch
network.host: 0.0.0.0
xpack.security.enabled: true
```

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 26, 2018, 11:26am UTC](https://discuss.elastic.co/t/coordinator-node-authentication-problem/133332/4 "2018-05-26T11:26:33Z")

</div>

What does the config of the other nodes look like? Any firewall preventing access between the nodes?

---

<div class="post-metadata">

**Author:** ![mkemalm](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@mkemalm](https://discuss.elastic.co/u/mkemalm)\
**Post date:** [May 28, 2018, 5:30am UTC](https://discuss.elastic.co/t/coordinator-node-authentication-problem/133332/5 "2018-05-28T05:30:36Z")

</div>

master01;

```
cluster.name: elkcluster
node.name: ${HOSTNAME}
discovery.zen.ping.unicast.hosts: ["master01", "master02", "master03"]
http.port: 9200
transport.tcp.port: 9300
bootstrap.memory_lock: true
node.master: true
node.data: true
search.remote.connect: false
node.ingest: false
node.ml: false
xpack.ml.enabled: true
discovery.zen.minimum_master_nodes: 2
node.attr.box_type: warm
path:
  data:
    - /data01
    - /data02
    - /data03
    - /data04
path.logs: /var/log/elasticsearch
network.host: 0.0.0.0
xpack.security.enabled: true

```

master02;

```
cluster.name: elkcluster
node.name: ${HOSTNAME}
discovery.zen.ping.unicast.hosts: ["master01", "master02", "master03"]
http.port: 9200
transport.tcp.port: 9300
bootstrap.memory_lock: true
node.master: true
node.data: true
search.remote.connect: false
node.ingest: false
node.ml: true
xpack.ml.enabled: true
discovery.zen.minimum_master_nodes: 2
node.attr.box_type: hot
path:
  data:
    - /data01
    - /data02
    - /data03
    - /data04
path.logs: /var/log/elasticsearch
network.host: 0.0.0.0
xpack.security.enabled: true

```

master03;

```
cluster.name: elkcluster
node.name: ${HOSTNAME}
discovery.zen.ping.unicast.hosts: ["master01", "master02", "master03"]
http.port: 9200
transport.tcp.port: 9300
bootstrap.memory_lock: true
node.master: true
node.data: true
search.remote.connect: false
node.ingest: false
node.ml: true
xpack.ml.enabled: true
discovery.zen.minimum_master_nodes: 2
node.attr.box_type: hot
path:
  data:
    - /data01
    - /data02
    - /data03
    - /data04
path.logs: /var/log/elasticsearch
network.host: 0.0.0.0
xpack.security.enabled: true

```

They are all in same subnet, there is no firewall issue.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 28, 2018, 6:02am UTC](https://discuss.elastic.co/t/coordinator-node-authentication-problem/133332/6 "2018-05-28T06:02:46Z")

</div>

As far as I can see that looks fine. Can you try telnet to port 9300 of the master nodes from the coordinating node?

---

<div class="post-metadata">

**Author:** ![mkemalm](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@mkemalm](https://discuss.elastic.co/u/mkemalm)\
**Post date:** [May 28, 2018, 6:29am UTC](https://discuss.elastic.co/t/coordinator-node-authentication-problem/133332/7 "2018-05-28T06:29:08Z")

</div>

They can do telnet. Are there any cluster join procedure in elasticsearch? Or is config yml file enough?

---

<div class="post-metadata">

**Author:** ![mkemalm](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@mkemalm](https://discuss.elastic.co/u/mkemalm)\
**Post date:** [May 28, 2018, 7:30am UTC](https://discuss.elastic.co/t/coordinator-node-authentication-problem/133332/8 "2018-05-28T07:30:14Z")

</div>

Problem was about a second non-routable interface at fourth node. It is fixed now. Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 25, 2018, 7:30am UTC](https://discuss.elastic.co/t/coordinator-node-authentication-problem/133332/9 "2018-06-25T07:30:15Z")

</div>

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