I guess there is a difference for network.host. If I keep it to either 127.0.0.1 or localhost, pinging ES will time out. If I remove the network.host line it won't. (but still no data results)
On Monday, 7 April 2014 18:31:00 UTC-3, Danny Joris wrote: > > Possibly. > > now this returns no hits: GET localhost:9200/_search > > Shouldn't this at least return my _river and kibana dashboard settings? > > I had an index with documents as well. No big deal if it's gone as it's > just data imported from mongodb through a river. Though I hope I didn't > lose the mapping. > > > On Monday, 7 April 2014 18:18:42 UTC-3, David Pilato wrote: >> >> I guess you installed Marvel some time ago and did not restart your node? >> >> -- >> *David Pilato* | *Technical Advocate* | *Elasticsearch.com* >> @dadoonet <https://twitter.com/dadoonet> | >> @elasticsearchfr<https://twitter.com/elasticsearchfr> >> >> >> Le 7 avril 2014 à 23:17:44, Danny Joris ([email protected]) a écrit: >> >> Removing Marvel worked using >> plugin --remove Marvel >> >> Seems like Elasticsearch starts correctly again. Not sure why Marvel >> became a culprit here as I haven't used it since I first installed it when >> it came out. I also didn't update Elasticsearch or any of the other plugins >> since. >> >> Thanks for your fast response, David. >> >> >> On Monday, 7 April 2014 18:13:33 UTC-3, Danny Joris wrote: >> >> >> curl -XGET 'http://127.0.0.1:9200/' >> >> curl: (7) Failed connect to 127.0.0.1:9200; Operation timed out >> >> >> >> Removing or updating network.host to localhost has the same result when >> trying to start elasticsearch. >> >> I'll try to remove the marvel plugin and see what it does. >> >> >> >> On Monday, 7 April 2014 18:05:28 UTC-3, David Pilato wrote: >> >> Can you tell why do you think it's not working anymore? >> >> What gives GET /localhost:9200 >> >> Also, could you try to modify >> network.host: 127.0.0.1 >> >> And unset it or set it to >> >> network.host: localhost >> >> -- >> *David Pilato* | *Technical Advocate* | *Elasticsearch.com* >> @dadoonet <https://twitter.com/dadoonet> | >> @elasticsearchfr<https://twitter.com/elasticsearchfr> >> >> >> Le 7 avril 2014 à 23:02:27, Danny Joris ([email protected]) a écrit: >> >> Elasticsearch.yml file: >> https://gist.github.com/DannyJoris/bb559005aad7f0bb1f10 >> >> I don't know why it stopped working. I've had ES running for a while. >> Restarted it several times even over the past months without problems. I >> made a simple query change on Kibana and it stopped working and I can't >> start it up again. >> >> Oh, and I wasn't using the Marvel interface when it went wrong. Though I >> did install the Marvel plugin quite a while ago, but I never really used it. >> >> Danny >> >> >> On Monday, 7 April 2014 17:53:49 UTC-3, David Pilato wrote: >> >> I answered this on SOF: >> >> The error you mentioned does not mean that your elasticsearch node is >> not working but only that it could not contact your Marvel node. >> >> Why do you think it's not working? >> >> Could you also gist your elasticsearch.yml file? >> >> -- >> *David Pilato* | *Technical Advocate* | *Elasticsearch.com* >> @dadoonet <https://twitter.com/dadoonet> | >> @elasticsearchfr<https://twitter.com/elasticsearchfr> >> >> >> Le 7 avril 2014 à 22:47:47, Danny Joris ([email protected]) a écrit: >> >> After making a simple change on a query in Kibana, my Elasticsearch >> instance stopped working and I can't start it up again. I'm using ES 0.90.9 >> on OSX using homebrew. >> >> Normally I would use this to start ES: >> elasticsearch -f -D >> es.config=/usr/local/opt/elasticsearch/config/elasticsearch.yml >> >> This however throws out a repeated error: >> >> [2014-04-07 15:59:02,128][INFO ][node ] [Puck] initializing ... >> [2014-04-07 15:59:02,224][INFO ][plugins ] [Puck] loaded [mongodb-river, >> mapper-attachments, marvel], sites [river-mongodb, marvel] >> [2014-04-07 15:59:04,553][INFO ][node ] [Puck] initialized >> [2014-04-07 15:59:04,553][INFO ][node ] [Puck] starting ... >> [2014-04-07 15:59:04,665][INFO ][transport ] [Puck] bound_address >> {inet[/127.0.0.1:9302]}, >> publish_address {inet[/127.0.0.1:9302]} >> [2014-04-07 15:59:07,727][INFO ][cluster.service ] [Puck] new_master >> [Puck][gtub58OkR9SskDE0SfYobw][inet[/127.0.0.1:9302]], reason: >> zen-disco-join (elected_as_master) >> [2014-04-07 15:59:07,778][INFO ][discovery ] [Puck] >> elasticsearch_dannyjoris/gtub58OkR9SskDE0SfYobw >> [2014-04-07 15:59:07,795][INFO ][http ] [Puck] bound_address {inet[/127.0 >> .0.1:9202]}, publish_address {inet[/127.0.0.1:9202]} >> [2014-04-07 15:59:07,796][INFO ][node ] [Puck] started >> [2014-04-07 15:59:07,813][INFO ][gateway ] [Puck] recovered [0] indices >> into cluster_state >> [2014-04-07 15:59:09,589][ERROR][marvel.agent.exporter ] error >> connecting to [localhost:9200] >> java.net.SocketTimeoutException: connect timed out >> at java.net.PlainSocketImpl.socketConnect(Native Method) >> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:382) >> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:241) >> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:228) >> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:431) >> at java.net.Socket.connect(Socket.java:527) >> at sun.net.NetworkClient.doConnect(NetworkClient.java:158) >> at sun.net.www.http.HttpClient.openServer(HttpClient.java:424) >> at sun.net.www.http.HttpClient.openServer(HttpClient.java:538) >> at sun.net.www.http.HttpClient.<init>(HttpClient.java:214) >> at sun.net.www.http.HttpClient.New(HttpClient.java:300)</sp >> >> ... >> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/0ce9a89f-48ce-4197-8c13-a36f0ac8f762%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/0ce9a89f-48ce-4197-8c13-a36f0ac8f762%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1913e64e-5f7e-4529-92d4-28ecdc823297%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
