# Seperate interfaces for clustering and querying **URL:** \ **Category:** Elasticsearch\ **Created:** [May 18, 2012, 1:58am UTC](https://discuss.elastic.co/t/seperate-interfaces-for-clustering-and-querying/7754 "2012-05-18T01:58:51Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Jim\_Mitchener](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jim_mitchener/32/2981_2.png) [@Jim\_Mitchener](https://discuss.elastic.co/u/Jim_Mitchener)\ **Post date:** [May 18, 2012, 1:58am UTC](https://discuss.elastic.co/t/seperate-interfaces-for-clustering-and-querying/7754/1 "2012-05-18T01:58:51Z")
I am trying to setup an elastic cluster with a different network.bind\_host and network.publish\_host interfaces. I cannot for the life of me get this to work with 2 real interfaces. If I set both to the same interface or one to loopback and the other to a real interface it works. However, if I try to set publish\_host and bind\_host to different interfaces I get errors on the publish\_host timing out trying to reconnect to itself. Am I not understanding how publish\_host is supposed to work? Should it not be set to a local IP that I wish to talk to the cluster on? I can post full trace logs if needed. Thanks, Jim ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 20, 2012, 8:13pm UTC](https://discuss.elastic.co/t/seperate-interfaces-for-clustering-and-querying/7754/2 "2012-05-20T20:13:07Z")
The publish host will be the address used to broadcast to the other nodes so they will use it to connect to the cluster with. On Fri, May 18, 2012 at 3:58 AM, Jim Mitchener [jcm@packetpan.org](mailto:jcm@packetpan.org) wrote: > I am trying to setup an elastic cluster with a different network.bind\_host > and network.publish\_host interfaces. I cannot for the life of me get this > to work with 2 real interfaces. If I set both to the same interface or one > to loopback and the other to a real interface it works. However, if I try > to set publish\_host and bind\_host to different interfaces I get errors on > the publish\_host timing out trying to reconnect to itself. > > Am I not understanding how publish\_host is supposed to work? Should it not > be set to a local IP that I wish to talk to the cluster on? I can post full > trace logs if needed. > > Thanks, > Jim ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 20, 2012, 8:13pm UTC](https://discuss.elastic.co/t/seperate-interfaces-for-clustering-and-querying/7754/3 "2012-05-20T20:13:20Z")
Sorry, to connect to the node with. On Sun, May 20, 2012 at 10:13 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > The publish host will be the address used to broadcast to the other nodes > so they will use it to connect to the cluster with. > > On Fri, May 18, 2012 at 3:58 AM, Jim Mitchener [jcm@packetpan.org](mailto:jcm@packetpan.org) wrote: > > > I am trying to setup an elastic cluster with a different > > network.bind\_host and network.publish\_host interfaces. I cannot for the > > life of me get this to work with 2 real interfaces. If I set both to the > > same interface or one to loopback and the other to a real interface it > > works. However, if I try to set publish\_host and bind\_host to different > > interfaces I get errors on the publish\_host timing out trying to reconnect > > to itself. > > > > Am I not understanding how publish\_host is supposed to work? Should it > > not be set to a local IP that I wish to talk to the cluster on? I can post > > full trace logs if needed. > > > > Thanks, > > Jim ---
**Author:** ![swendel](https://avatars.discourse-cdn.com/v4/letter/s/b2d939/32.png) [@swendel](https://discuss.elastic.co/u/swendel)\ **Post date:** [June 8, 2012, 11:56am UTC](https://discuss.elastic.co/t/seperate-interfaces-for-clustering-and-querying/7754/4 "2012-06-08T11:56:55Z")
hey guys, im also trying to get seperate interfaces configuration for the cluster and http communication running, but no luke. vagrant@ubuntu10044:~$ sudo netstat -tlpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:32000 0.0.0.0:\* LISTEN 5655/java tcp6 0 0 10.0.2.15:9300 :::\* LISTEN 5655/java tcp6 0 0 10.0.2.15:9200 :::\* LISTEN 5655/java vi /etc/elasticsearch/elasticsearch.yml ############################## Network And HTTP ############################### network.bind\_host: _eth0:ipv4_ network.publish\_host: _eth1:ipv4_ ################################### Gateway ################################### less /var/log/elasticsearch/elasticsearch.log [2012-06-08 00:00:26,884][WARN][cluster.service] [ubuntu10044] failed to reconnect to node [ubuntu10044][WHZxwr9VQeyVpASDgHSJ6w][inet[/192.168.0.4:9300]] org.elasticsearch.transport.ConnectTransportException: [ubuntu10044][inet[/192.168.0.4:9300]] connect\_timeout[30s] at org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:560) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:503) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:482) at org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:128) at org.elasticsearch.cluster.service.InternalClusterService$ReconnectToNodes.run(InternalClusterService.java:377) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592) at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:400) at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:362) at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:284) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:102) You can see how i tried to deploy elasticsearch in my chef cookbook at git hub: [https://github.com/sebwendel/chef-elasticsearch/tree/0.1.0](https://github.com/sebwendel/chef-elasticsearch/tree/0.1.0) do you have any ideas? Regards, Sebastian ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [June 10, 2012, 10:28pm UTC](https://discuss.elastic.co/t/seperate-interfaces-for-clustering-and-querying/7754/5 "2012-06-10T22:28:25Z")
If you want separate interfaces for internal cluster (transport) communication and http, the settings should be transport.host for the inner cluster communication, and http.host for the http one. On Fri, Jun 8, 2012 at 1:56 PM, swendel [s.wendel@sourceindex.de](mailto:s.wendel@sourceindex.de) wrote: > hey guys, > > im also trying to get seperate interfaces configuration for the cluster and > http communication running, but no luke. > > vagrant@ubuntu10044:~$ sudo netstat -tlpn > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State > PID/Program name > tcp 0 0 127.0.0.1:32000 0.0.0.0:\* LISTEN > 5655/java > tcp6 0 0 10.0.2.15:9300 :::\* LISTEN > 5655/java > tcp6 0 0 10.0.2.15:9200 :::\* LISTEN > 5655/java > > vi /etc/elasticsearch/elasticsearch.yml > ############################## Network And HTTP > ############################### > > network.bind\_host: _eth0:ipv4_ > network.publish\_host: _eth1:ipv4_ > > ################################### Gateway > ################################### > > less /var/log/elasticsearch/elasticsearch.log > [2012-06-08 00:00:26,884][WARN][cluster.service] [ubuntu10044] > failed to reconnect to node > [ubuntu10044][WHZxwr9VQeyVpASDgHSJ6w][inet[/192.168.0.4:9300]] > org.elasticsearch.transport.ConnectTransportException: > [ubuntu10044][inet[/192.168.0.4:9300]] connect\_timeout[30s] > at > > org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:560) > at > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:503) > at > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:482) > at > > org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:128) > at > > org.elasticsearch.cluster.service.InternalClusterService$ReconnectToNodes.run(InternalClusterService.java:377) > at > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:636) > Caused by: java.net.ConnectException: Connection refused > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > at > sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592) > at > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:400) > at > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:362) > at > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:284) > at > > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:102) > > You can see how i tried to deploy elasticsearch in my chef cookbook at git > hub: > [https://github.com/sebwendel/chef-elasticsearch/tree/0.1.0](https://github.com/sebwendel/chef-elasticsearch/tree/0.1.0) > > do you have any ideas? > > Regards, > Sebastian > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Seperate-interfaces-for-clustering-and-querying-tp4000112p4018970.html](http://elasticsearch-users.115913.n3.nabble.com/Seperate-interfaces-for-clustering-and-querying-tp4000112p4018970.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![swendel](https://avatars.discourse-cdn.com/v4/letter/s/b2d939/32.png) [@swendel](https://discuss.elastic.co/u/swendel)\ **Post date:** [June 11, 2012, 6:31pm UTC](https://discuss.elastic.co/t/seperate-interfaces-for-clustering-and-querying/7754/6 "2012-06-11T18:31:02Z")
Thanks for the answer. But whare ist the difference to: network.bind\_host and network.publish\_host? And how comes that the documentation tells something completely different? > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Is this a complete new implementation? Or did i misunderstood the documentation? greetings, Sebastian 2012/6/11 Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) > If you want separate interfaces for internal cluster (transport) > communication and http, the settings should be transport.host for the inner > cluster communication, and http.host for the http one. > > On Fri, Jun 8, 2012 at 1:56 PM, swendel [s.wendel@sourceindex.de](mailto:s.wendel@sourceindex.de) wrote: > > > hey guys, > > > > im also trying to get seperate interfaces configuration for the cluster > > and > > http communication running, but no luke. > > > > vagrant@ubuntu10044:~$ sudo netstat -tlpn > > Active Internet connections (only servers) > > Proto Recv-Q Send-Q Local Address Foreign Address State > > PID/Program name > > tcp 0 0 127.0.0.1:32000 0.0.0.0:\* > > LISTEN > > 5655/java > > tcp6 0 0 10.0.2.15:9300 :::\* > > LISTEN > > 5655/java > > tcp6 0 0 10.0.2.15:9200 :::\* > > LISTEN > > 5655/java > > > > vi /etc/elasticsearch/elasticsearch.yml > > ############################## Network And HTTP > > ############################### > > > > network.bind\_host: _eth0:ipv4_ > > network.publish\_host: _eth1:ipv4_ > > > > ################################### Gateway > > ################################### > > > > less /var/log/elasticsearch/elasticsearch.log > > [2012-06-08 00:00:26,884][WARN][cluster.service] [ubuntu10044] > > failed to reconnect to node > > [ubuntu10044][WHZxwr9VQeyVpASDgHSJ6w][inet[/192.168.0.4:9300]] > > org.elasticsearch.transport.ConnectTransportException: > > [ubuntu10044][inet[/192.168.0.4:9300]] connect\_timeout[30s] > > at > > > > org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:560) > > at > > > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:503) > > at > > > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:482) > > at > > > > org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:128) > > at > > > > org.elasticsearch.cluster.service.InternalClusterService$ReconnectToNodes.run(InternalClusterService.java:377) > > at > > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > > at > > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > > at java.lang.Thread.run(Thread.java:636) > > Caused by: java.net.ConnectException: Connection refused > > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > > at > > sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592) > > at > > > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:400) > > at > > > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:362) > > at > > > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:284) > > at > > > > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:102) > > > > You can see how i tried to deploy elasticsearch in my chef cookbook at git > > hub: > > [https://github.com/sebwendel/chef-elasticsearch/tree/0.1.0](https://github.com/sebwendel/chef-elasticsearch/tree/0.1.0) > > > > do you have any ideas? > > > > Regards, > > Sebastian > > > > -- > > View this message in context: > > [http://elasticsearch-users.115913.n3.nabble.com/Seperate-interfaces-for-clustering-and-querying-tp4000112p4018970.html](http://elasticsearch-users.115913.n3.nabble.com/Seperate-interfaces-for-clustering-and-querying-tp4000112p4018970.html) > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![swendel](https://avatars.discourse-cdn.com/v4/letter/s/b2d939/32.png) [@swendel](https://discuss.elastic.co/u/swendel)\ **Post date:** [June 11, 2012, 10:01pm UTC](https://discuss.elastic.co/t/seperate-interfaces-for-clustering-and-querying/7754/7 "2012-06-11T22:01:30Z")
hi Shay, your advice worked as i hoped, thanks. vagrant@ubuntu1204:~$ cat /etc/elasticsearch/elasticsearch.ym http.host: _eth0:ipv4_ transport.host: _eth1:ipv4_ but 😉 now there is another problem. vagrant@ubuntu1204:~$ sudo netstat -tulpn | grep java tcp 0 0 127.0.0.1:32000 0.0.0.0:\* LISTEN 8184/java tcp6 0 0 10.0.2.15:9200 :::\* LISTEN 8184/java tcp6 0 0 192.168.0.5:9300 :::\* LISTEN 8184/java udp6 0 0 :::54328 :::\* 8184/java Zen Discovery is not listening on the same interface that the transport. If there any way to also control that? didn't found any hint in the documentation or in the net. 2012/6/11 Sebastian Wendel [s.wendel@sourceindex.de](mailto:s.wendel@sourceindex.de) > Thanks for the answer. > > But whare ist the difference to: network.bind\_host > and network.publish\_host? > > And how comes that the documentation tells something completely different? > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/modules/network.html) > > Is this a complete new implementation? Or did i misunderstood the > documentation? > > greetings, > Sebastian > > 2012/6/11 Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) > > > If you want separate interfaces for internal cluster (transport) > > communication and http, the settings should be transport.host for the inner > > cluster communication, and http.host for the http one. > > > > On Fri, Jun 8, 2012 at 1:56 PM, swendel [s.wendel@sourceindex.de](mailto:s.wendel@sourceindex.de) wrote: > > > > > hey guys, > > > > > > im also trying to get seperate interfaces configuration for the cluster > > > and > > > http communication running, but no luke. > > > > > > vagrant@ubuntu10044:~$ sudo netstat -tlpn > > > Active Internet connections (only servers) > > > Proto Recv-Q Send-Q Local Address Foreign Address State > > > PID/Program name > > > tcp 0 0 127.0.0.1:32000 0.0.0.0:\* > > > LISTEN > > > 5655/java > > > tcp6 0 0 10.0.2.15:9300 :::\* > > > LISTEN > > > 5655/java > > > tcp6 0 0 10.0.2.15:9200 :::\* > > > LISTEN > > > 5655/java > > > > > > vi /etc/elasticsearch/elasticsearch.yml > > > ############################## Network And HTTP > > > ############################### > > > > > > network.bind\_host: _eth0:ipv4_ > > > network.publish\_host: _eth1:ipv4_ > > > > > > ################################### Gateway > > > ################################### > > > > > > less /var/log/elasticsearch/elasticsearch.log > > > [2012-06-08 00:00:26,884][WARN][cluster.service] [ubuntu10044] > > > failed to reconnect to node > > > [ubuntu10044][WHZxwr9VQeyVpASDgHSJ6w][inet[/192.168.0.4:9300]] > > > org.elasticsearch.transport.ConnectTransportException: > > > [ubuntu10044][inet[/192.168.0.4:9300]] connect\_timeout[30s] > > > at > > > > > > org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:560) > > > at > > > > > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:503) > > > at > > > > > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:482) > > > at > > > > > > org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:128) > > > at > > > > > > org.elasticsearch.cluster.service.InternalClusterService$ReconnectToNodes.run(InternalClusterService.java:377) > > > at > > > > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > > > at > > > > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > > > at java.lang.Thread.run(Thread.java:636) > > > Caused by: java.net.ConnectException: Connection refused > > > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > > > at > > > sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592) > > > at > > > > > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:400) > > > at > > > > > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:362) > > > at > > > > > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:284) > > > at > > > > > > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:102) > > > > > > You can see how i tried to deploy elasticsearch in my chef cookbook at > > > git > > > hub: > > > [https://github.com/sebwendel/chef-elasticsearch/tree/0.1.0](https://github.com/sebwendel/chef-elasticsearch/tree/0.1.0) > > > > > > do you have any ideas? > > > > > > Regards, > > > Sebastian > > > > > > -- > > > View this message in context: > > > [http://elasticsearch-users.115913.n3.nabble.com/Seperate-interfaces-for-clustering-and-querying-tp4000112p4018970.html](http://elasticsearch-users.115913.n3.nabble.com/Seperate-interfaces-for-clustering-and-querying-tp4000112p4018970.html) > > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). -- Mit freundlichen Grüßen, Sebastian Wendel. ////////////////////////////////////////////////////////////////////////////////////// SourceIndex IT-Services Wohlwillstraße 2, 20359 Hamburg Office: +49(0)40-209 344 900 Fax: +49(0)40-209 344 909 Email: [s.wendel@sourceindex.de](mailto:s.wendel@sourceindex.de) Web: [http://www.sourceindex.de](http://www.sourceindex.de) Xing: [Sebastian Wendel - Fullstack Developer & Platform Engineer - REBOOT IN PROGRESS | XING](http://www.xing.com/profile/sebastian_wendel) WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [June 13, 2012, 6:32pm UTC](https://discuss.elastic.co/t/seperate-interfaces-for-clustering-and-querying/7754/8 "2012-06-13T18:32:09Z")
The network.host setting simply sets it to all sockets based modules (http and transport). On Mon, Jun 11, 2012 at 8:31 PM, Sebastian Wendel [s.wendel@sourceindex.de](mailto:s.wendel@sourceindex.de)wrote: > Thanks for the answer. > > But whare ist the difference to: network.bind\_host > and network.publish\_host? > > And how comes that the documentation tells something completely different? > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/modules/network.html) > > Is this a complete new implementation? Or did i misunderstood the > documentation? > > greetings, > Sebastian > > 2012/6/11 Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) > > > If you want separate interfaces for internal cluster (transport) > > communication and http, the settings should be transport.host for the inner > > cluster communication, and http.host for the http one. > > > > On Fri, Jun 8, 2012 at 1:56 PM, swendel [s.wendel@sourceindex.de](mailto:s.wendel@sourceindex.de) wrote: > > > > > hey guys, > > > > > > im also trying to get seperate interfaces configuration for the cluster > > > and > > > http communication running, but no luke. > > > > > > vagrant@ubuntu10044:~$ sudo netstat -tlpn > > > Active Internet connections (only servers) > > > Proto Recv-Q Send-Q Local Address Foreign Address State > > > PID/Program name > > > tcp 0 0 127.0.0.1:32000 0.0.0.0:\* > > > LISTEN > > > 5655/java > > > tcp6 0 0 10.0.2.15:9300 :::\* > > > LISTEN > > > 5655/java > > > tcp6 0 0 10.0.2.15:9200 :::\* > > > LISTEN > > > 5655/java > > > > > > vi /etc/elasticsearch/elasticsearch.yml > > > ############################## Network And HTTP > > > ############################### > > > > > > network.bind\_host: _eth0:ipv4_ > > > network.publish\_host: _eth1:ipv4_ > > > > > > ################################### Gateway > > > ################################### > > > > > > less /var/log/elasticsearch/elasticsearch.log > > > [2012-06-08 00:00:26,884][WARN][cluster.service] [ubuntu10044] > > > failed to reconnect to node > > > [ubuntu10044][WHZxwr9VQeyVpASDgHSJ6w][inet[/192.168.0.4:9300]] > > > org.elasticsearch.transport.ConnectTransportException: > > > [ubuntu10044][inet[/192.168.0.4:9300]] connect\_timeout[30s] > > > at > > > > > > org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:560) > > > at > > > > > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:503) > > > at > > > > > > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:482) > > > at > > > > > > org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:128) > > > at > > > > > > org.elasticsearch.cluster.service.InternalClusterService$ReconnectToNodes.run(InternalClusterService.java:377) > > > at > > > > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > > > at > > > > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > > > at java.lang.Thread.run(Thread.java:636) > > > Caused by: java.net.ConnectException: Connection refused > > > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > > > at > > > sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592) > > > at > > > > > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:400) > > > at > > > > > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:362) > > > at > > > > > > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:284) > > > at > > > > > > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:102) > > > > > > You can see how i tried to deploy elasticsearch in my chef cookbook at > > > git > > > hub: > > > [https://github.com/sebwendel/chef-elasticsearch/tree/0.1.0](https://github.com/sebwendel/chef-elasticsearch/tree/0.1.0) > > > > > > do you have any ideas? > > > > > > Regards, > > > Sebastian > > > > > > -- > > > View this message in context: > > > [http://elasticsearch-users.115913.n3.nabble.com/Seperate-interfaces-for-clustering-and-querying-tp4000112p4018970.html](http://elasticsearch-users.115913.n3.nabble.com/Seperate-interfaces-for-clustering-and-querying-tp4000112p4018970.html) > > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:24am UTC](https://discuss.elastic.co/t/seperate-interfaces-for-clustering-and-querying/7754/9 "2017-07-06T03:24:26Z")