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)
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 Apache log4j 1.2 - Frequently Asked Technical Questions for more info.
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):
Just a FYI
I just installed Marvel and I noticed you need 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 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.
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.
--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/CAKHuyJr7%3Deh-s85HrwTjmKJ7wTcezU4aiSQG6P8vC2
zFd2OD-w%40mail.gmail.com.
--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/1391327120065.1c3e15a9%40Nodemailer.
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).
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 ron.sher@gmail.com 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)
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 Apache log4j 1.2 - Frequently Asked Technical Questions for more info.
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):
Just a FYI
I just installed Marvel and I noticed you need 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 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.
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.
--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/CAKHuyJr7%3Deh-s85HrwTjmKJ7wTcezU4aiSQG6P8vC2
zFd2OD-w%40mail.gmail.com.
--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/1391327120065.1c3e15a9%40Nodemailer.
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).
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)
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 Apache log4j 1.2 - Frequently Asked Technical Questions for more info.
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):
Just a FYI
I just installed Marvel and I noticed you need 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 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 < climb...@gmail.com> 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.
--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/
1391327120065.1c3e15a9%40Nodemailer.
It looks like you have dynamic mappings disabled - most likely via the
following line in the elasticsearch.yml file:
index.mapper.dynamic: false
You will need to override it for marvel indices which rely on this
functionality. To do so (assuming you don't want to remove that line from
the elasticsearch.yml) add the following index template:
curl -XPUT "http://HOST:PORT/_template/custom_marvel" -d'
{
"template": ".marvel*",
"order": 1,
"settings": {
"mapper.dynamic": true
}
}'
After the template is added, you'd need to delete today's index so it will
be recreated using the new template:
curl -XDELETE "http://HOST:PORT/.marvel-2014.02.02"
There is no need to restart nodes. Once the index is re-created the error
should go away (should take ~5 sec)
On Sunday, February 2, 2014 4:38:57 PM UTC+1, Ron Sher wrote:
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 <b.le...@gmail.com<javascript:>
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).
On Sun, Feb 2, 2014 at 3:23 PM, Ron Sher <ron....@gmail.com <javascript:>
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 <ron....@gmail.com<javascript:>
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 <ron....@gmail.com<javascript:>
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 Apache log4j 1.2 - Frequently Asked Technical Questions for more info.
On Sun, Feb 2, 2014 at 10:05 AM, Boaz Leskes <b.le...@gmail.com<javascript:>
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):
Just a FYI
I just installed Marvel and I noticed you need 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 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 < climb...@gmail.com> 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.
--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/
1391327120065.1c3e15a9%40Nodemailer.
On Sunday, 2 February 2014 18:02:04 UTC, Boaz Leskes wrote:
[loads of great stuff snipped]
Just in case it helps anyone else out there, I was suffering with blank
Marvel dashboards (logstash 1.3.3 with ES 1.0.1) and it turned out to be a
permissions problem on the marvel plugin directory. We use a umask of 027
and as such the 'elasticsearch' user couldn't load the plugin when ES
started. This is pretty easily spotted in the logs, where the plugins run
announced "loaded , sites " rather than "loaded [marvel], sites
[marvel]", which is what you should see.
Anyhoo a chown -R of the plugins directory to match the user running ES,
and a cluster restart, and all is now well with the world.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.