Failed to send ping to zen_unicast_1

mohit_Kumar · July 17, 2013, 3:05pm

hello everybody,
I am just creating a demo cluster in Linux machine. and facing this issue
jvm 1 | [2013-07-17 19:16:08,805][WARN ][discovery.zen.ping.unicast]
[Atleza] failed to send ping to [[#zen_unicast_1#][inet[/192.168.1.81:9201
]]]
jvm 1 | org.elasticsearch.transport.ReceiveTimeoutTransportException:
[][inet[/192.168.1.81:9201]][discovery/zen/unicast] request_id [58] timed
out after [3750ms]
jvm 1 | at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
jvm 1 | at java.lang.Thread.run(Thread.java:636)
jvm 1 | [2013-07-17 19:16:13,309][WARN ][discovery.zen.ping.unicast]
[Atleza] failed to send ping to [[#zen_unicast_1#][inet[/192.168.1.81:9201
]]]
jvm 1 | org.elasticsearch.transport.ReceiveTimeoutTransportException:
[][inet[/192.168.1.81:9201]][discovery/zen/unicast] request_id [61] timed
out after [3750ms]
jvm 1 | at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
jvm 1 | at java.lang.Thread.run(Thread.java:636)
jvm 1 | [2013-07-17 19:16:17,813][WARN ][discovery.zen.ping.unicast]
[Atleza] failed to send ping to [[#zen_unicast_1#][inet[/192.168.1.81:9201
]]]
jvm 1 | org.elasticsearch.transport.ReceiveTimeoutTransportException:
[][inet[/192.168.1.81:9201]][discovery/zen/unicast] request_id [64] timed
out after [3751ms]
jvm 1 | at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
jvm 1 | at java.lang.Thread.run(Thread.java:636)

I am not able to find out where thing goes wrong. I have attached the
config yml file of elasticsearch . please find the attachment for the for
the yml file.
I am creating first time the cluster so kindly help me.
Thanks in advance
Regrads
Mohit Kumar Yadav
(MCA/BBA)
Assocaite Software Developer
Next Gen Invent Corporation, Noida
Email Id : mohit.kumar@ngiventures.com ,mohit.kumar.ngi@gmail.com

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

jprante · July 17, 2013, 3:08pm

The line

discovery.zen.ping.unicast.hosts: ["10.0.0.3:9201"]

will not work. 9201 is an ES HTTP port.

Use port range 9300-9400 instead for the ES discovery (e.g. 9300 or 9301
...)

Jörg

Am 17.07.13 17:05, schrieb Mohit Kumar Yadav:

hello everybody,
I am just creating a demo cluster in Linux machine. and facing this issue
jvm 1 | [2013-07-17 19:16:08,805][WARN
][discovery.zen.ping.unicast] [Atleza] failed to send ping to
[[#zen_unicast_1#][inet[/192.168.1.81:9201]]]
jvm 1 |
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[inet[/192.168.1.81:9201]][discovery/zen/unicast] request_id [58]
timed out after [3750ms]
jvm 1 | at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
jvm 1 | at java.lang.Thread.run(Thread.java:636)
jvm 1 | [2013-07-17 19:16:13,309][WARN
][discovery.zen.ping.unicast] [Atleza] failed to send ping to
[[#zen_unicast_1#][inet[/192.168.1.81:9201]]]
jvm 1 |
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[inet[/192.168.1.81:9201]][discovery/zen/unicast] request_id [61]
timed out after [3750ms]
jvm 1 | at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
jvm 1 | at java.lang.Thread.run(Thread.java:636)
jvm 1 | [2013-07-17 19:16:17,813][WARN
][discovery.zen.ping.unicast] [Atleza] failed to send ping to
[[#zen_unicast_1#][inet[/192.168.1.81:9201]]]
jvm 1 |
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[inet[/192.168.1.81:9201]][discovery/zen/unicast] request_id [64]
timed out after [3751ms]
jvm 1 | at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
jvm 1 | at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
jvm 1 | at java.lang.Thread.run(Thread.java:636)

I am not able to find out where thing goes wrong. I have attached the
config yml file of elasticsearch . please find the attachment for the
for the yml file.
I am creating first time the cluster so kindly help me.
Thanks in advance
Regrads
Mohit Kumar Yadav
(MCA/BBA)
Assocaite Software Developer
Next Gen Invent Corporation, Noida
Email Id : mohit.kumar@ngiventures.com
mailto:mohit.kumar@ngiventures.com ,mohit.kumar.ngi@gmail.com
mailto:mohit.kumar.ngi@gmail.com

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.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

mohit_Kumar · July 17, 2013, 5:45pm

hi Jorg,
thanks for response.
*but i have one more query that I am using the same configuration for
windows machines and its working great. if its related to ES port then it
should not for windows machine also...
*
On Wednesday, July 17, 2013 8:38:58 PM UTC+5:30, Jörg Prante wrote:

The line

discovery.zen.ping.unicast.hosts: ["10.0.0.3:9201"]

will not work. 9201 is an ES HTTP port.

Use port range 9300-9400 instead for the ES discovery (e.g. 9300 or 9301
...)

Jörg

Am 17.07.13 17:05, schrieb Mohit Kumar Yadav:

hello everybody,
I am just creating a demo cluster in Linux machine. and facing this
issue
jvm 1 | [2013-07-17 19:16:08,805][WARN
][discovery.zen.ping.unicast] [Atleza] failed to send ping to
[[#zen_unicast_1#][inet[/192.168.1.81:9201]]]
jvm 1 |
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[inet[/192.168.1.81:9201]][discovery/zen/unicast] request_id [58]
timed out after [3750ms]
jvm 1 | at

org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)

jvm 1 | at

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

jvm 1 | at

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)

jvm 1 | at java.lang.Thread.run(Thread.java:636)
jvm 1 | [2013-07-17 19:16:13,309][WARN
][discovery.zen.ping.unicast] [Atleza] failed to send ping to
[[#zen_unicast_1#][inet[/192.168.1.81:9201]]]
jvm 1 |
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[inet[/192.168.1.81:9201]][discovery/zen/unicast] request_id [61]
timed out after [3750ms]
jvm 1 | at

org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)

jvm 1 | at

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

jvm 1 | at

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)

jvm 1 | at java.lang.Thread.run(Thread.java:636)
jvm 1 | [2013-07-17 19:16:17,813][WARN
][discovery.zen.ping.unicast] [Atleza] failed to send ping to
[[#zen_unicast_1#][inet[/192.168.1.81:9201]]]
jvm 1 |
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[inet[/192.168.1.81:9201]][discovery/zen/unicast] request_id [64]
timed out after [3751ms]
jvm 1 | at

org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)

jvm 1 | at

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

jvm 1 | at

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)

jvm 1 | at java.lang.Thread.run(Thread.java:636)

I am not able to find out where thing goes wrong. I have attached the
config yml file of elasticsearch . please find the attachment for the
for the yml file.
I am creating first time the cluster so kindly help me.
Thanks in advance
Regrads
Mohit Kumar Yadav
(MCA/BBA)
Assocaite Software Developer
Next Gen Invent Corporation, Noida
Email Id : mohit...@ngiventures.com <javascript:>
<mailto:mohit...@ngiventures.com <javascript:>>,
mohit.kumar.ngi@gmail.com <javascript:>
<mailto:mohit.k...@gmail.com <javascript:>>

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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

jprante · July 17, 2013, 5:55pm

Use port range 9300-9400, this is correct.

Jörg

Am 17.07.13 19:45, schrieb Mohit Kumar Yadav:

hi Jorg,
thanks for response.
*but i have one more query that I am using the same configuration for
windows machines and its working great. if its related to ES port then
it should not for windows machine also... *

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

mohit_Kumar · July 17, 2013, 7:12pm

hi jorg,
I succeed in creating the cluster on linux machine just because of you....
really thanks a ton..

On Wednesday, July 17, 2013 11:25:09 PM UTC+5:30, Jörg Prante wrote:

Use port range 9300-9400, this is correct.

Jörg

Am 17.07.13 19:45, schrieb Mohit Kumar Yadav:

hi Jorg,
thanks for response.
*but i have one more query that I am using the same configuration for
windows machines and its working great. if its related to ES port then
it should not for windows machine also... *

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

Topic		Replies	Views
Failed to send ping to Elasticsearch	11	20012	July 5, 2017
Unicast discovery fails to connect to master Elasticsearch	7	2981	July 6, 2017
Logstash failed to send ping to elasticsearch Elasticsearch	2	1525	July 6, 2017
How can I fix the following error? Elasticsearch	1	480	July 6, 2017
Unicast Problems (no handler found for action [discovery/zen/unicast]) Elasticsearch	3	1048	July 6, 2017

Failed to send ping to zen_unicast_1

Related topics