# Getting \[marvel.agent.exporter \] \[Tempest\] remote target didn't respond with 200 OK response code \[404 Not Found **URL:** \ **Category:** Elasticsearch\ **Created:** [March 20, 2014, 12:35am UTC](https://discuss.elastic.co/t/getting-marvel-agent-exporter-tempest-remote-target-didnt-respond-with-200-ok-response-code-404-not-found/16482 "2014-03-20T00:35:05Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Dennis\_Andersen](https://avatars.discourse-cdn.com/v4/letter/d/848f3c/32.png) [@Dennis\_Andersen](https://discuss.elastic.co/u/Dennis_Andersen)\ **Post date:** [March 20, 2014, 12:35am UTC](https://discuss.elastic.co/t/getting-marvel-agent-exporter-tempest-remote-target-didnt-respond-with-200-ok-response-code-404-not-found/16482/1 "2014-03-20T00:35:05Z")
My two clusters, currently default named, Tempest and Morg, appear to be working fine. The head plugin shows green and queries work. I have indices and documents added. When I added Marvel, restarted both nodes, I see the error [marvel.agent.exporter] [Tempest] remote target didn't respond with 200 OK response code [404 Not Found repeated in each cluster's log files (with the names changed accordingly). Marvel has a blank screen and reports "No results There were no results because no indices were found that match your selected time span". I am running version 1.0.1 on each server, have Java (build 1.7.0\_25-b15) on each. No configuration changes were made -- meaning no marvel.agent properties were set in the configuration. I do have discovery.zen.ping.multicast.enabled: false Any suggestions? thanks, Dennis -- 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/7aaece0e-3d3b-4798-aacc-f71f53ecbe53%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7aaece0e-3d3b-4798-aacc-f71f53ecbe53%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [March 21, 2014, 6:29pm UTC](https://discuss.elastic.co/t/getting-marvel-agent-exporter-tempest-remote-target-didnt-respond-with-200-ok-response-code-404-not-found/16482/2 "2014-03-21T18:29:13Z")
Hi Dennis, Do you have action.auto\_create\_index: false in your elasticsearch.yml? if so see [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/marvel/current/#relevant-settings) Cheers, Boaz On Thursday, March 20, 2014 1:35:05 AM UTC+1, Dennis Andersen wrote: > My two clusters, currently default named, Tempest and Morg, appear to be > working fine. The head plugin shows green and queries work. I have indices > and documents added. > > When I added Marvel, restarted both nodes, I see the error > [marvel.agent.exporter] [Tempest] remote target didn't respond with > 200 OK response code [404 Not Found > repeated in each cluster's log files (with the names changed accordingly). > > Marvel has a blank screen and reports "No results There were no results > because no indices were found that match your selected time span". > > I am running version 1.0.1 on each server, have Java (build 1.7.0\_25-b15) > on each. No configuration changes were made -- meaning no marvel.agent > properties were set in the configuration. > I do have > discovery.zen.ping.multicast.enabled: false > > Any suggestions? > > thanks, > > Dennis -- 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/7dbc30b6-0c5f-4776-b550-d842a8b4bda2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7dbc30b6-0c5f-4776-b550-d842a8b4bda2%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Dennis\_Andersen](https://avatars.discourse-cdn.com/v4/letter/d/848f3c/32.png) [@Dennis\_Andersen](https://discuss.elastic.co/u/Dennis_Andersen)\ **Post date:** [March 21, 2014, 8:57pm UTC](https://discuss.elastic.co/t/getting-marvel-agent-exporter-tempest-remote-target-didnt-respond-with-200-ok-response-code-404-not-found/16482/3 "2014-03-21T20:57:21Z")
Yes, that was it! Thanks! Dennis On Friday, March 21, 2014 11:29:13 AM UTC-7, Boaz Leskes wrote: > Hi Dennis, > > Do you have action.auto\_create\_index: false in your elasticsearch.yml? if > so see > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/marvel/current/#relevant-settings) > > Cheers, > Boaz > > On Thursday, March 20, 2014 1:35:05 AM UTC+1, Dennis Andersen wrote: > > > My two clusters, currently default named, Tempest and Morg, appear to be > > working fine. The head plugin shows green and queries work. I have indices > > and documents added. > > > > When I added Marvel, restarted both nodes, I see the error > > [marvel.agent.exporter] [Tempest] remote target didn't respond with > > 200 OK response code [404 Not Found > > repeated in each cluster's log files (with the names changed accordingly). > > > > Marvel has a blank screen and reports "No results There were no results > > because no indices were found that match your selected time span". > > > > I am running version 1.0.1 on each server, have Java (build 1.7.0\_25-b15) > > on each. No configuration changes were made -- meaning no marvel.agent > > properties were set in the configuration. > > I do have > > discovery.zen.ping.multicast.enabled: false > > > > Any suggestions? > > > > thanks, > > > > Dennis -- 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/0b2ed392-ea0b-4641-ac41-413d5a67b188%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0b2ed392-ea0b-4641-ac41-413d5a67b188%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![bsarkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bsarkar/32/42967_2.png) [@bsarkar](https://discuss.elastic.co/u/bsarkar)\ **Post date:** [February 27, 2015, 5:00am UTC](https://discuss.elastic.co/t/getting-marvel-agent-exporter-tempest-remote-target-didnt-respond-with-200-ok-response-code-404-not-found/16482/4 "2015-02-27T05:00:28Z")
If I set action.auto\_create\_index to false and I've setup a separate Elasticsearch cluster for Marvel indices, will I still face this issue? On Friday, March 21, 2014 at 11:59:13 PM UTC+5:30, Boaz Leskes wrote: > Hi Dennis, > > Do you have action.auto\_create\_index: false in your elasticsearch.yml? if > so see > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/marvel/current/#relevant-settings) > > Cheers, > Boaz > > On Thursday, March 20, 2014 1:35:05 AM UTC+1, Dennis Andersen wrote: > > > My two clusters, currently default named, Tempest and Morg, appear to be > > working fine. The head plugin shows green and queries work. I have indices > > and documents added. > > > > When I added Marvel, restarted both nodes, I see the error > > [marvel.agent.exporter] [Tempest] remote target didn't respond with > > 200 OK response code [404 Not Found > > repeated in each cluster's log files (with the names changed accordingly). > > > > Marvel has a blank screen and reports "No results There were no results > > because no indices were found that match your selected time span". > > > > I am running version 1.0.1 on each server, have Java (build 1.7.0\_25-b15) > > on each. No configuration changes were made -- meaning no marvel.agent > > properties were set in the configuration. > > I do have > > discovery.zen.ping.multicast.enabled: false > > > > Any suggestions? > > > > thanks, > > > > Dennis -- 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/f7fb82f4-40d2-4ae4-ad66-a3f7ea13898d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f7fb82f4-40d2-4ae4-ad66-a3f7ea13898d%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [February 27, 2015, 7:08am UTC](https://discuss.elastic.co/t/getting-marvel-agent-exporter-tempest-remote-target-didnt-respond-with-200-ok-response-code-404-not-found/16482/5 "2015-02-27T07:08:11Z")
No. The auto create needs to be enabled (or set to marvel-\*) on the cluster that will store your marvel data. Using a separated monitoring cluster means that your production cluster can have it disabled On Fri, Feb 27, 2015 at 6:00 AM, Mouzer [bittusrk@gmail.com](mailto:bittusrk@gmail.com) wrote: > If I set action.auto\_create\_index to false and I've setup a separate > Elasticsearch cluster for Marvel indices, will I still face this issue? > On Friday, March 21, 2014 at 11:59:13 PM UTC+5:30, Boaz Leskes wrote: > > > Hi Dennis, > > > > Do you have action.auto\_create\_index: false in your elasticsearch.yml? if > > so see > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/marvel/current/#relevant-settings) > > > > Cheers, > > Boaz > > > > On Thursday, March 20, 2014 1:35:05 AM UTC+1, Dennis Andersen wrote: > > > > > My two clusters, currently default named, Tempest and Morg, appear to be > > > working fine. The head plugin shows green and queries work. I have indices > > > and documents added. > > > > > > When I added Marvel, restarted both nodes, I see the error > > > [marvel.agent.exporter] [Tempest] remote target didn't respond with > > > 200 OK response code [404 Not Found > > > repeated in each cluster's log files (with the names changed accordingly). > > > > > > Marvel has a blank screen and reports "No results There were no results > > > because no indices were found that match your selected time span". > > > > > > I am running version 1.0.1 on each server, have Java (build 1.7.0\_25-b15) > > > on each. No configuration changes were made -- meaning no marvel.agent > > > properties were set in the configuration. > > > I do have > > > discovery.zen.ping.multicast.enabled: false > > > > > > Any suggestions? > > > > > > thanks, > > > > > > Dennis > > -- > You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit [https://groups.google.com/d/topic/elasticsearch/IfyoSgZgR9E/unsubscribe](https://groups.google.com/d/topic/elasticsearch/IfyoSgZgR9E/unsubscribe). > To unsubscribe from this group and all its topics, 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/f7fb82f4-40d2-4ae4-ad66-a3f7ea13898d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f7fb82f4-40d2-4ae4-ad66-a3f7ea13898d%40googlegroups.com). > 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/1425020890325.e102d9%40Nodemailer](https://groups.google.com/d/msgid/elasticsearch/1425020890325.e102d9%40Nodemailer). 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:29am UTC](https://discuss.elastic.co/t/getting-marvel-agent-exporter-tempest-remote-target-didnt-respond-with-200-ok-response-code-404-not-found/16482/6 "2017-07-06T00:29:38Z")