# Marvel.agent.exporter: error connecting to \[\[0:0:0:0:0:0:0:0\]:9200\] \[No route to host\] **URL:** \ **Category:** Elasticsearch\ **Created:** [April 17, 2015, 5:51pm UTC](https://discuss.elastic.co/t/marvel-agent-exporter-error-connecting-to-0-0-0-0-0-0-0-0-9200-no-route-to-host/23300 "2015-04-17T17:51:45Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Graham\_Leggett](https://avatars.discourse-cdn.com/v4/letter/g/e56c9b/32.png) [@Graham\_Leggett](https://discuss.elastic.co/u/Graham_Leggett)\ **Post date:** [April 17, 2015, 5:51pm UTC](https://discuss.elastic.co/t/marvel-agent-exporter-error-connecting-to-0-0-0-0-0-0-0-0-9200-no-route-to-host/23300/1 "2015-04-17T17:51:45Z")
Hi all, We have an elasticsearch v1.4.4-1 server deployed on RHEL6 via RPM, and we're having trouble getting marvel to display data. The elasticsearch.log file shows the following error logged over and over again: [2015-04-17 18:47:16,046][ERROR][marvel.agent.exporter] [visim-test] error connecting to [[0:0:0:0:0:0:0:0]:9200] [No route to host] [2015-04-17 18:47:16,046][ERROR][marvel.agent.exporter] [visim-test] could not connect to any configured elasticsearch instances: [[0:0:0:0:0:0:0:0]:9200] Has anyone seen this problem before? ## Regards, Graham -- 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/19bb834a-1a0e-4851-95f7-bd3194d08612%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/19bb834a-1a0e-4851-95f7-bd3194d08612%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Kimbro\_Staken](https://avatars.discourse-cdn.com/v4/letter/k/9fc29f/32.png) [@Kimbro\_Staken](https://discuss.elastic.co/u/Kimbro_Staken)\ **Post date:** [April 17, 2015, 6:12pm UTC](https://discuss.elastic.co/t/marvel-agent-exporter-error-connecting-to-0-0-0-0-0-0-0-0-9200-no-route-to-host/23300/2 "2015-04-17T18:12:31Z")
Yes, I saw the same issue yesterday on a test system. For me it started after the node crashed and rebooted. It looks like it's trying to use the IPv6 address to connect. I didn't really dig too far for a real fix since this was a test system but setting network.bind\_host 0.0.0.0 got marvel working again. On Fri, Apr 17, 2015 at 10:51 AM, Graham Leggett [minfrin@sharp.fm](mailto:minfrin@sharp.fm) wrote: > Hi all, > > We have an elasticsearch v1.4.4-1 server deployed on RHEL6 via RPM, and > we're having trouble getting marvel to display data. > > The elasticsearch.log file shows the following error logged over and over > again: > > [2015-04-17 18:47:16,046][ERROR][marvel.agent.exporter] [visim-test] > error connecting to [[0:0:0:0:0:0:0:0]:9200] [No route to host] > [2015-04-17 18:47:16,046][ERROR][marvel.agent.exporter] [visim-test] > could not connect to any configured elasticsearch instances: > [[0:0:0:0:0:0:0:0]:9200] > > Has anyone seen this problem before? > > ## Regards, Graham > > -- > 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/19bb834a-1a0e-4851-95f7-bd3194d08612%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/19bb834a-1a0e-4851-95f7-bd3194d08612%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/19bb834a-1a0e-4851-95f7-bd3194d08612%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/19bb834a-1a0e-4851-95f7-bd3194d08612%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAA0DmXZbWiQuhDeFs-0XkCmUnL6y5Yc7UfowNyawesPsRKbMTw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAA0DmXZbWiQuhDeFs-0XkCmUnL6y5Yc7UfowNyawesPsRKbMTw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Graham\_Leggett](https://avatars.discourse-cdn.com/v4/letter/g/e56c9b/32.png) [@Graham\_Leggett](https://discuss.elastic.co/u/Graham_Leggett)\ **Post date:** [April 17, 2015, 6:37pm UTC](https://discuss.elastic.co/t/marvel-agent-exporter-error-connecting-to-0-0-0-0-0-0-0-0-9200-no-route-to-host/23300/3 "2015-04-17T18:37:37Z")
On Friday, 17 April 2015 20:12:43 UTC+2, Kimbro Staken wrote: > Yes, I saw the same issue yesterday on a test system. For me it started > after the node crashed and rebooted. It looks like it's trying to use the > IPv6 address to connect. I didn't really dig too far for a real fix since > this was a test system but setting network.bind\_host 0.0.0.0 got marvel > working again. No luck with 0.0.0.00, it made no difference. Setting network.bind\_host to the external IP address specifically (in our case we need this) seems to have worked around the problem. ## Regards, Graham -- 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/d8134524-106b-4e9c-ac30-ec6aa7605f54%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d8134524-106b-4e9c-ac30-ec6aa7605f54%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:18am UTC](https://discuss.elastic.co/t/marvel-agent-exporter-error-connecting-to-0-0-0-0-0-0-0-0-9200-no-route-to-host/23300/4 "2017-07-06T00:18:57Z")