# Nodeclient connection problems

**URL:** <https://discuss.elastic.co/t/nodeclient-connection-problems/21879>\
**Category:** Elasticsearch\
**Created:** [January 28, 2015, 2:39pm UTC](https://discuss.elastic.co/t/nodeclient-connection-problems/21879 "2015-01-28T14:39:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marc\_2](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Marc\_2](https://discuss.elastic.co/u/Marc_2)\
**Post date:** [January 28, 2015, 2:39pm UTC](https://discuss.elastic.co/t/nodeclient-connection-problems/21879/1 "2015-01-28T14:39:42Z")

</div>

Hi there,

I have a test server running that I can only access via ssh.  
Therefore, I tunneled the 9300 port to my localhost.  
The nodeClient in the JavaAPI somehow can find my masternode but not  
connect after timeout of 30s.  
Any ideas? Help!

2015-01-28T15:34:33.651+0100|Information: 2015.01.28\_15:34:33,651 - DEBUG  
org.elasticsearch.discovery.zen: [LT356.41c6fb63] filtered ping responses: (  
filter\_client[true], filter\_data[false])  
--\> ping\_response{node [[centralnode][TxdaBxULSK6Rr1obILiP\_A][ritab2v05  
][inet[/161.50.140.3:9300]]{bench=true}], id[306], master  
[[centralnode][TxdaBxULSK6Rr1obILiP\_A][ritab2v05][inet[/161.50.140.3:9300]]{bench=true}],  
hasJoinedOnce [true], cluster\_name[elasticsearch-test]}  
[Thread=elasticsearch[LT356.41c6fb63][generic][T#5]]

2015-01-28T15:34:54.663+0100|Information: 2015.01.28\_15:34:54,662 - WARN  
org.elasticsearch.discovery.zen: [LT356.41c6fb63] failed to connect to  
master  
[[centralnode][TxdaBxULSK6Rr1obILiP\_A][ritab2v05][inet[/161.50.140.3:9300]]{bench=true}],  
retrying... [Thread=elasticsearch[LT356.41c6fb63][generic][T#5]]  
org.elasticsearch.transport.ConnectTransportException:  
[centralnode][inet[/161.50.140.3:9300]] connect\_timeout[30s]  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:807)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:741)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:714)  
at  
org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:150)  
at  
org.elasticsearch.discovery.zen.ZenDiscovery.joinElectedMaster(ZenDiscovery.java:441)  
at  
org.elasticsearch.discovery.zen.ZenDiscovery.innerJoinCluster(ZenDiscovery.java:393)  
at  
org.elasticsearch.discovery.zen.ZenDiscovery.access$6000(ZenDiscovery.java:80)  
at  
org.elasticsearch.discovery.zen.ZenDiscovery$JoinThreadControl$1.run(ZenDiscovery.java:1318)  
at  
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:745)  
Caused by: java.net.ConnectException: Connection timed out: no further  
information: /161.50.140.3:9300  
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)  
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739  
)  
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.  
connect(NioClientBoss.java:152)  
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.  
processSelectedKeys(NioClientBoss.java:105)  
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.  
process(NioClientBoss.java:79)  
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector  
.run(AbstractNioSelector.java:318)  
at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(  
NioClientBoss.java:42)  
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(  
ThreadRenamingRunnable.java:108)  
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.  
run(DeadLockProofWorker.java:42)  
... 3 more

2015-01-28T15:34:54.667+0100|Information: 2015.01.28\_15:34:54,667 - DEBUG  
org.elasticsearch.cluster.service: [LT356.41c6fb63] processing [finalize\_join  
([centralnode][TxdaBxULSK6Rr1obILiP\_A][ritab2v05][inet[/161.50.140.3:9300]]{  
bench=true})]: execute [Thread=elasticsearch[LT356.41c6fb63][clusterService  
#updateTask][T#1]]

2015-01-28T15:34:54.668+0100|Information: 2015.01.28\_15:34:54,668 - DEBUG  
org.elasticsearch.cluster.service: [LT356.41c6fb63] processing [finalize\_join  
([centralnode][TxdaBxULSK6Rr1obILiP\_A][ritab2v05][inet[/161.50.140.3:9300]]{  
bench=true})]: no change in cluster\_state [Thread=elasticsearch[LT356.  
41c6fb63][clusterService#updateTask][T#1]]

2015-01-28T15:34:54.681+0100|Information: 2015.01.28\_15:34:54,680 - DEBUG  
org.elasticsearch.transport.netty: [LT356.41c6fb63] connected to node [[#zen\_unicast\_1#][LT356][inet[localhost/127.0.0.1:9300]]]  
[Thread=elasticsearch[LT356.41c6fb63][[unicast\_connect]][T#1]]

2015-01-28T15:34:57.687+0100|Information: 2015.01.28\_15:34:57,687 - DEBUG  
org.elasticsearch.transport.netty: [LT356.41c6fb63] disconnecting from [[#zen\_unicast\_1#][LT356][inet[localhost/127.0.0.1:9300]]]  
due to explicit disconnect call  
[Thread=elasticsearch[LT356.41c6fb63][generic][T#1]]

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/9e45fa37-c17e-4d93-afa0-1c447bc6aaf2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9e45fa37-c17e-4d93-afa0-1c447bc6aaf2%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 12:36am UTC](https://discuss.elastic.co/t/nodeclient-connection-problems/21879/2 "2017-07-06T00:36:08Z")

</div>

Closed on July 6, 2017, 12:36am UTC


