Getting somewhere...

Changed the hosts and now I get the following:
type[cluster_stats] missing: trying to auto create mapping, but dynamic
mapping is disabled


On Sun, Feb 2, 2014 at 5:26 PM, Boaz Leskes <[email protected]> wrote:

> It looks like marvel can't store the data on localhost:9200. The most
> common reason is running on another port. Another option is that ES is not
> bound on localhost or that http access is turned off (in which case marvel
> won't work).
>
>  Can you verify you can connect ES via the terminal while on the machine
> itself? If needed you can change the host & port marvel where sends data
> to. See
> http://www.elasticsearch.org/guide/en/marvel/current/index.html#stats-export
>
>
> On Sun, Feb 2, 2014 at 3:23 PM, Ron Sher <[email protected]> wrote:
>
>> The beginning of the log looks like:
>> [2014-02-02 15:38:56,003][INFO ][node                     ] [hades3]
>> version[0.90.10], pid[20219], build[0a5781f/2014-01-10T10:18:37Z]
>> [2014-02-02 15:38:56,004][INFO ][node                     ] [hades3]
>> initializing ...
>> [2014-02-02 15:38:56,027][INFO ][plugins                  ] [hades3]
>> loaded [marvel], sites [marvel, head]
>> [2014-02-02 15:39:01,302][INFO ][node                     ] [hades3]
>> initialized
>> [2014-02-02 15:39:01,302][INFO ][node                     ] [hades3]
>> starting ...
>> [2014-02-02 15:39:01,410][INFO ][transport                ] [hades3]
>> bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
>> 192.168.10.148:9300]}
>> [2014-02-02 15:39:06,408][ERROR][marvel.agent.exporter    ] error
>> sending data
>>  java.io.FileNotFoundException: http://localhost:9200/_bulk
>>          
>> atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
>>         at org.elasticsearch.marvel.agent.exporter.ESExporter.
>> sendCloseExportingConnection(ESExporter.java:232)
>>         at org.elasticsearch.marvel.agent.exporter.ESExporter.
>> exportXContent(ESExporter.java:252)
>>         at org.elasticsearch.marvel.agent.exporter.ESExporter.
>> exportNodeStats(ESExporter.java:134)
>>         at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
>> exportNodeStats(AgentService.java:274)
>>         at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
>> run(AgentService.java:174)
>>         at java.lang.Thread.run(Thread.java:724)
>>
>>
>>
>> On Sun, Feb 2, 2014 at 3:43 PM, Ron Sher <[email protected]> wrote:
>>
>>> I've noticed that I didn't have a logging.yml (was called logging.xml
>>> instead).
>>> Changed that and then I see:
>>>
>>>  [2014-02-02 15:42:19,824][ERROR][marvel.agent.exporter    ] error
>>> sending data
>>>  java.io.FileNotFoundException: http://localhost:9200/_bulk
>>>         
>>> atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
>>>         at org.elasticsearch.marvel.agent.exporter.ESExporter.
>>> sendCloseExportingConnection(ESExporter.java:232)
>>>         at org.elasticsearch.marvel.agent.exporter.ESExporter.
>>> exportXContent(ESExporter.java:252)
>>>         at org.elasticsearch.marvel.agent.exporter.ESExporter.
>>> exportClusterStats(ESExporter.java:172)
>>>         at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
>>> exportClusterStats(AgentService.java:214)
>>>         at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.
>>> run(AgentService.java:180)
>>>         at java.lang.Thread.run(Thread.java:724)
>>>
>>>
>>> What now?
>>>
>>>
>>> On Sun, Feb 2, 2014 at 11:29 AM, Ron Sher <[email protected]> wrote:
>>>
>>>> This is what I see in the log after the restart:
>>>> STATUS | wrapper  | 2014/02/02 11:26:54 |   Copyright (C) 1999-2011
>>>> Tanuki Software, Ltd. All Rights Reserved.
>>>> STATUS | wrapper  | 2014/02/02 11:26:54 |
>>>> http://wrapper.tanukisoftware.com
>>>> STATUS | wrapper  | 2014/02/02 11:26:54 |
>>>> WARN   | wrapper  | 2014/02/02 11:26:54 | Encountered an invalid
>>>> numerical value for configuration property 
>>>> wrapper.java.initmemory=%ES_HEAP_SIZE%.
>>>>  Resolving to 0.
>>>> WARN   | wrapper  | 2014/02/02 11:26:54 | Encountered an invalid
>>>> numerical value for configuration property 
>>>> wrapper.java.maxmemory=%ES_HEAP_SIZE%.
>>>>  Resolving to 0.
>>>> STATUS | wrapper  | 2014/02/02 11:26:54 | Launching a JVM...
>>>> INFO   | jvm 1    | 2014/02/02 11:26:55 | WrapperManager:
>>>> Initializing...
>>>> INFO   | jvm 1    | 2014/02/02 11:27:01 | log4j:WARN No appenders
>>>> could be found for logger (node).
>>>> INFO   | jvm 1    | 2014/02/02 11:27:01 | log4j:WARN Please initialize
>>>> the log4j system properly.
>>>> INFO   | jvm 1    | 2014/02/02 11:27:01 | log4j:WARN See
>>>> http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
>>>>
>>>>
>>>>
>>>> On Sun, Feb 2, 2014 at 10:05 AM, Boaz Leskes <[email protected]>wrote:
>>>>
>>>>> OK, interesting.
>>>>>
>>>>> Can you check the logs on one of the nodes to if there are any errors?
>>>>> also please double check that when the node started it logged a line
>>>>> similar to the following (containing marvel in the list after loaded):
>>>>>
>>>>>  [2014-02-02 09:03:48,043][INFO ][plugins                  ] [
>>>>> Stonewall] loaded [marvel], sites [marvel]
>>>>>
>>>>>
>>>>>
>>>>> start a node (one is enough)
>>>>>
>>>>>
>>>>> On Sunday, February 2, 2014 8:50:47 AM UTC+1, Ron Sher wrote:
>>>>>
>>>>>>  again, using 0.90.10.
>>>>>> This is what I did:
>>>>>>  bin/plugin -i elasticsearch/marvel/latest
>>>>>>   /etc/init.d/elasticsearch restart
>>>>>>
>>>>>> Did the same on a different cluster - still doesn't work.
>>>>>>
>>>>>>
>>>>>> On Sun, Feb 2, 2014 at 9:45 AM, Boaz Leskes <[email protected]>wrote:
>>>>>>
>>>>>>>  Hi Ron,
>>>>>>>
>>>>>>> It looks like no data is sent. What version of ES are you running?
>>>>>>> Did you restart tES after installing the plugin?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Boaz
>>>>>>>
>>>>>>>
>>>>>>>  On Sun, Feb 2, 2014 at 8:27 AM, Ron Sher <[email protected]> wrote:
>>>>>>>
>>>>>>>>  Tony,
>>>>>>>> What do you mean by <activity>?
>>>>>>>>
>>>>>>>>  Indeed I've added marvel to an already running cluster and no
>>>>>>>> data is shown in the dashboard and I don't see any marvel index
>>>>>>>>
>>>>>>>> Ron
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Jan 31, 2014 at 12:47 AM, Tony Su <[email protected]>wrote:
>>>>>>>>
>>>>>>>>>  Just a FYI
>>>>>>>>> I just installed Marvel and I noticed you need <activity> for
>>>>>>>>> Marvel to start collecting and displaying data, even about itself.
>>>>>>>>> If your machines are all previously setup and data already in
>>>>>>>>> place, I don't know if you'd read anything.
>>>>>>>>> Other thing I noticed is that <all> ES nodes have to be the same
>>>>>>>>> version.
>>>>>>>>> So, for example if Marvel is pointing to an odd-ball ES node,
>>>>>>>>> there would not be any activity with any other ES node so would be 
>>>>>>>>> blank.
>>>>>>>>>
>>>>>>>>> And, I assume that after changing ES versions you restarted the ES
>>>>>>>>> services on every node? Otherwise you're still stuck on the previous
>>>>>>>>> version.
>>>>>>>>>
>>>>>>>>> HTH,
>>>>>>>>> Tony
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thursday, January 30, 2014 11:24:11 AM UTC-8, Brad Jordan wrote:
>>>>>>>>>
>>>>>>>>>> I keep getting this alert: *No results* There were no results
>>>>>>>>>> because no indices were found that match your selected time span.
>>>>>>>>>>
>>>>>>>>>> -Brad
>>>>>>>>>>
>>>>>>>>>> On Thursday, January 30, 2014 12:23:04 PM UTC-7, Brad Jordan
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Upgraded my cluster to 0.9.10 and still get a blank Marvel
>>>>>>>>>>> dashboard...
>>>>>>>>>>>
>>>>>>>>>>> I have about 30 indexes which all have data starting on about
>>>>>>>>>>> 1/20/2014 going back to 5/01/2013. Bigdesk and the Head plugin have 
>>>>>>>>>>> no
>>>>>>>>>>> problems seeing that nodes, shards, indexes. Is there an additional 
>>>>>>>>>>> step
>>>>>>>>>>> I'm missing?
>>>>>>>>>>>
>>>>>>>>>>> -Brad
>>>>>>>>>>>
>>>>>>>>>>> On Thursday, January 30, 2014 10:48:04 AM UTC-7, Brad Jordan
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Thursday, January 30, 2014 10:43:35 AM UTC-7, Boaz Leskes
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi brad,
>>>>>>>>>>>>>
>>>>>>>>>>>>> You should upgrade to 0.90.10. 0.90.7 is not supported by
>>>>>>>>>>>>> marvel.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>> Boaz
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Jan 30, 2014 at 6:39 PM, Brad Jordan <
>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I also have the same issue. I'm running elasticsearch-0.90.7.
>>>>>>>>>>>>>> I installed the plugin, bounced the cluster and Marvel is just 
>>>>>>>>>>>>>> blank. Is
>>>>>>>>>>>>>> there a config I'm missing?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -Brad
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Thursday, January 30, 2014 5:22:03 AM UTC-7, Ron Sher
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hey,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Just tried installing the plugin.
>>>>>>>>>>>>>>> Installation was easy (bin/plugin -i elasticsearch/marvel/
>>>>>>>>>>>>>>> latest followed by a restart) by then the plugin shows an
>>>>>>>>>>>>>>> empty dashboard.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Am I missing something?\
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Ron
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>    --
>>>>>>>>>>>>>> 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/UPBMKvxwwM8/
>>>>>>>>>>>>>> unsubscribe.
>>>>>>>>>>>>>> To unsubscribe from this group and all its topics, send an
>>>>>>>>>>>>>> email to [email protected].
>>>>>>>>>>>>>> To view this discussion on the web visit
>>>>>>>>>>>>>> https://groups.google.com/d/msgid/elasticsearch/4dcf998b-89f
>>>>>>>>>>>>>> e-4f07-bb2d-a036cd567c66%40googlegroups.com.
>>>>>>>>>>>>>> For more options, visit https://groups.google.com/grou
>>>>>>>>>>>>>> ps/opt_out.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>        --
>>>>>>>>> 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/UPBMKvxwwM8/unsubscribe.
>>>>>>>>> To unsubscribe from this group and all its topics, send an email
>>>>>>>>> to [email protected].
>>>>>>>>>  To view this discussion on the web visit
>>>>>>>>> https://groups.google.com/d/msgid/elasticsearch/43083c5a-
>>>>>>>>> bc16-4f01-8450-15402e82d798%40googlegroups.com.
>>>>>>>>>
>>>>>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>>>>>
>>>>>>>>
>>>>>>>>  --
>>>>>>>> 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/UPBMKvxwwM8/unsubscribe.
>>>>>>>>  To unsubscribe from this group and all its topics, send an email
>>>>>>>> to [email protected].
>>>>>>>>  To view this discussion on the web visit
>>>>>>>> https://groups.google.com/d/msgid/elasticsearch/CAKHuyJr7%3Deh-
>>>>>>>> s85HrwTjmKJ7wTcezU4aiSQG6P8vC2zFd2OD-w%40mail.gmail.com.
>>>>>>>>
>>>>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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/UPBMKvxwwM8/unsubscribe.
>>>>>>>  To unsubscribe from this group and all its topics, send an email
>>>>>>> to [email protected].
>>>>>>>  To view this discussion on the web visit
>>>>>>> https://groups.google.com/d/msgid/elasticsearch/
>>>>>>> 1391327120065.1c3e15a9%40Nodemailer.
>>>>>>>
>>>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>    --
>>>>> 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/UPBMKvxwwM8/unsubscribe
>>>>> .
>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>> [email protected].
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/elasticsearch/53e585f5-b8f8-4213-9d78-3c964971ce5f%40googlegroups.com
>>>>> .
>>>>>
>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>
>>>>
>>>>
>>>
>>  --
>> 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/UPBMKvxwwM8/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/CAKHuyJrNNn3UcihdORh9bmSPMFvqukKDYYaVZiTrnk24b5bzkA%40mail.gmail.com
>> .
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> 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/UPBMKvxwwM8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/1391354763457.886ae8c2%40Nodemailer
> .
>
> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAKHuyJp9scSGxtaQtcRnteX3Ma2J8hBL8_QzvTpev_2zzyF_AA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to