# Adding third node from subnet **URL:** \ **Category:** Elasticsearch\ **Created:** [January 6, 2017, 10:36am UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770 "2017-01-06T10:36:58Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![Grenouille06](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@Grenouille06](https://discuss.elastic.co/u/Grenouille06)\ **Post date:** [January 6, 2017, 10:36am UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/1 "2017-01-06T10:36:58Z")
Hi, I have a cluster on the same subnet that works VM1 [cluster.name](http://cluster.name): NCA-CLUSTER [node.name](http://node.name): logwarehouse\_master1 network.host: 192.168.18.15 discovery.zen.ping.unicast.hosts: ["192.168.18.18:9300", "172.16.207.33:9300"] VM2 [cluster.name](http://cluster.name): NCA-CLUSTER [node.name](http://node.name): logwarehouse\_master2 network.host: 192.168.18.18 discovery.zen.ping.unicast.hosts: ["192.168.18.15:9300", "172.16.207.33:9300"] This cluster works. I prepared a third VM on another subnet, and I can't connect it to my cluster VM3 [cluster.name](http://cluster.name): NCA-CLUSTER [node.name](http://node.name): logwarehouse\_data1 network.host: 172.16.207.33 discovery.zen.ping.unicast.hosts: ["192.168.18.15:9300", "192.168.18.18:9300"] Telnet works on 192.168.18.15 9300 and for 192.168.18.18 9300 Telnet works for 172.16.207.33 9300 for 192.168.18.15 and 192.168.18.18 I donn't know what I must add for my cluster to work Thank you for your help ---
**Author:** ![xavierfacq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavierfacq/32/8744_2.png) [@xavierfacq](https://discuss.elastic.co/u/xavierfacq)\ **Post date:** [January 6, 2017, 11:06am UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/2 "2017-01-06T11:06:58Z")
Hi, can you provide your master logs ? ---
**Author:** ![chenjinyuan87](https://avatars.discourse-cdn.com/v4/letter/c/bb73d2/32.png) [@chenjinyuan87](https://discuss.elastic.co/u/chenjinyuan87)\ **Post date:** [January 6, 2017, 11:10am UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/3 "2017-01-06T11:10:06Z")
What about telnet from 192.168 to 172.16? ---
**Author:** ![Grenouille06](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@Grenouille06](https://discuss.elastic.co/u/Grenouille06)\ **Post date:** [January 6, 2017, 12:08pm UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/4 "2017-01-06T12:08:47Z")
Hi. It works, that's why I don't underdtand why third node won't connect Envoyé de mon iPhone ---
**Author:** ![xavierfacq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavierfacq/32/8744_2.png) [@xavierfacq](https://discuss.elastic.co/u/xavierfacq)\ **Post date:** [January 6, 2017, 12:30pm UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/5 "2017-01-06T12:30:56Z")
Do you have this properties: ``` discovery.zen.ping.multicast.enabled: false ``` EDIT: if version \< 5.0 ---
**Author:** ![Grenouille06](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@Grenouille06](https://discuss.elastic.co/u/Grenouille06)\ **Post date:** [January 6, 2017, 6:16pm UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/6 "2017-01-06T18:16:32Z")
I have this line in my elastic.yml but it is not active. # discovery.zen.ping.multicast.enabled: false ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 6, 2017, 10:41pm UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/7 "2017-01-06T22:41:58Z")
Are these in the same datacentre/location? ---
**Author:** ![xavierfacq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavierfacq/32/8744_2.png) [@xavierfacq](https://discuss.elastic.co/u/xavierfacq)\ **Post date:** [January 7, 2017, 10:39pm UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/8 "2017-01-07T22:39:07Z")
can you provide log of your VM3 ? /var/log/elasticsearch/\*.log ---
**Author:** ![Grenouille06](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@Grenouille06](https://discuss.elastic.co/u/Grenouille06)\ **Post date:** [January 9, 2017, 9:46am UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/9 "2017-01-09T09:46:53Z")
Hi, yes they are on the same Datacentre ---
**Author:** ![Grenouille06](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@Grenouille06](https://discuss.elastic.co/u/Grenouille06)\ **Post date:** [January 9, 2017, 9:47am UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/10 "2017-01-09T09:47:57Z")
And the elasticsearch logs are empty. On /var/log/elasticsearch/ I have an elastic.log but it is empty ---
**Author:** ![Grenouille06](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@Grenouille06](https://discuss.elastic.co/u/Grenouille06)\ **Post date:** [January 9, 2017, 10:07am UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/11 "2017-01-09T10:07:02Z")
I found that information in a new log file : [logwarehouse\_data1] initialized [2017-01-09T11:01:26,995][INFO][o.e.n.Node] [logwarehouse\_data1] starting ... [2017-01-09T11:01:27,209][INFO][o.e.t.TransportService] [logwarehouse\_data1] publish\_address {172.16.207.33:9300}, bound\_addresses {172.16.207.33:9300} [2017-01-09T11:01:27,214][INFO][o.e.b.BootstrapCheck] [logwarehouse\_data1] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks [2017-01-09T11:01:27,450][WARN][o.e.d.z.UnicastZenPing] [logwarehouse\_data1] [1] failed send ping to {#zen\_unicast\_1#}{wqGH5S7qSamfkLQ2QDmMOQ}{192.168.18.15}{192.168.18.15:9300} java.lang.IllegalStateException: handshake failed with {#zen\_unicast\_1#}{wqGH5S7qSamfkLQ2QDmMOQ}{192.168.18.15}{192.168.18.15:9300} at org.elasticsearch.transport.TransportService.handshake(TransportService.java:370) ~[elasticsearch-5.1.1.jar:5.1.1] at org.elasticsearch.transport.TransportService.connectToNodeLightAndHandshake(TransportService.java:345) ~[elasticsearch-5.1.1.jar:5.1.1] at org.elasticsearch.transport.TransportService.connectToNodeLightAndHandshake(TransportService.java:319) ~[elasticsearch-5.1.1.jar:5.1.1] at org.elasticsearch.discovery.zen.UnicastZenPing$2.run(UnicastZenPing.java:473) [elasticsearch-5.1.1.jar:5.1.1] at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:458) [elasticsearch-5.1.1.jar:5.1.1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0\_111] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0\_111] at java.lang.Thread.run(Thread.java:745) [?:1.8.0\_111] Caused by: org.elasticsearch.transport.RemoteTransportException: [logwarehouse\_master1][192.168.18.15:9300][internal:transport/handshake] Caused by: org.elasticsearch.ElasticsearchSecurityException: failed to verify signed authentication information ---
**Author:** ![xavierfacq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavierfacq/32/8744_2.png) [@xavierfacq](https://discuss.elastic.co/u/xavierfacq)\ **Post date:** [January 9, 2017, 10:19am UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/12 "2017-01-09T10:19:05Z")
> [@Grenouille06](#): > > bound\_addresses {172.16.207.33:9300} But: > [@](#): > > failed send ping to {#zen\_unicast\_1#}{wqGH5S7qSamfkLQ2QDmMOQ}{192.168.18.15}{192.168.18.15:9300} Are your certain that you can telnet from VM3 (172.16.207.33) to 2 others VM using the 9300 port ? ---
**Author:** ![Grenouille06](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@Grenouille06](https://discuss.elastic.co/u/Grenouille06)\ **Post date:** [January 9, 2017, 10:21am UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/13 "2017-01-09T10:21:00Z")
Yes it works : root@vmnt2042tech:~\>telnet 192.168.18.15 9300 Trying 192.168.18.15... Connected to 192.168.18.15. Escape character is '^]'. root@vmnt2042tech:~\>telnet 192.168.18.18 9300 Trying 192.168.18.18... Connected to 192.168.18.18. Escape character is '^]'. ---
**Author:** ![xavierfacq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavierfacq/32/8744_2.png) [@xavierfacq](https://discuss.elastic.co/u/xavierfacq)\ **Post date:** [January 9, 2017, 10:25am UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/14 "2017-01-09T10:25:11Z")
Another question : VM3 use the same ES version that VM1 & VM2 ? ---
**Author:** ![Grenouille06](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@Grenouille06](https://discuss.elastic.co/u/Grenouille06)\ **Post date:** [January 9, 2017, 10:34am UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/15 "2017-01-09T10:34:20Z")
Yes, same version. But I found something : VM3 don't use the system\_key file generated by VM1. The authentification problem may comes from that ---
**Author:** ![Grenouille06](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@Grenouille06](https://discuss.elastic.co/u/Grenouille06)\ **Post date:** [January 9, 2017, 12:25pm UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/16 "2017-01-09T12:25:25Z")
The problem is resolved. In VM3, the file system\_key in /etc/elasticsearch/x-pack was corrupted (I don't know why...) In VM1 I generate a new system\_key and I send it on VM3 with the terminal. Thanks for all your help, I really appreciate. Fayce ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 6, 2017, 12:25pm UTC](https://discuss.elastic.co/t/adding-third-node-from-subnet/70770/17 "2017-02-06T12:25:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.