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 <minf...@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+unsubscr...@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?utm_medium=email&utm_source=footer> > . > For more options, visit 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAA0DmXZbWiQuhDeFs-0XkCmUnL6y5Yc7UfowNyawesPsRKbMTw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
