Yes, the plugin is definitely installed on every node of the cluster. Installation was done in a repeatable and automated fashion (Ansible) and I can verify the plugin presence on every node. Plus, as I mentioned, it actually worked when I first installed it days ago.
On Thursday, February 20, 2014 1:15:28 PM UTC-5, Tony Su wrote: > > Hi George, > Just wondering if you've installed the Marvel plugin on <all> nodes. > > I think the Marvel dashboard is trying to access Marvel data but failing > because if you don't install the plugin on every node, the data isn't being > collected to be retrieved. > > Tony > > > > On Thursday, February 20, 2014 9:04:10 AM UTC-8, George Stathis wrote: > >> - Running 0.90.11 >> - Marvel monitor machine and the cluster it monitors are separated >> - Installed Marvel the day after it was released and it was originally >> running fine (all panels filled with data) >> >> Checked the dashboard again today (nothing has changed since it was >> installed) and some panels in the dashboard like the node stats and the >> indices stats are blank. I tried re-installing marvel on the monitoring >> box, cleaned out all marvel-* indexes and even wiped out the data path >> directory and let it re-build and the problem persisted. >> >> So I took a look at the JS console and it shows the following errors >> (host name redacted): >> >> event.returnValue is deprecated. Please use the standard >> event.preventDefault() instead. app.js?r=face658:5 >> POST >> http://<some_internal_host_name_>/.marvel-2014.02.20/_search?search_type=count >> >> 400 (Bad Request) app.js?r=face658:9 >> TypeError: Cannot read property 'timestamp' of undefined >> at >> http://<some_internal_host_name_>/_plugin/marvel/kibana/app/panels/marvel/stats_table/module.js?r=face658:4:10741 >> at i >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:458) >> at >> http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:1014 >> at Object.f.$eval >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:6963) >> at Object.f.$digest >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:5755) >> at Object.f.$apply >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:7111) >> at f >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:11507) >> at r >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:13216) >> at XMLHttpRequest.v.onreadystatechange >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:13851) >> >> app.js?r=face658:8 >> POST >> http://<some_internal_host_name_>/.marvel-2014.02.20/_search?search_type=count >> >> 400 (Bad Request) app.js?r=face658:9 >> TypeError: Cannot read property 'timestamp' of undefined >> at >> http://<some_internal_host_name_>/_plugin/marvel/kibana/app/panels/marvel/stats_table/module.js?r=face658:4:10741 >> at i >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:458) >> at >> http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:1014 >> at Object.f.$eval >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:6963) >> at Object.f.$digest >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:5755) >> at Object.f.$apply >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:7111) >> at f >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:11507) >> at r >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:13216) >> at XMLHttpRequest.v.onreadystatechange >> (http://<some_internal_host_name_>/_plugin/marvel/kibana/app/app.js?r=face658:9:13851) >> >> app.js?r=face658:8 >> Retrying call from Thu Feb 20 2014 11:46:56 GMT-0500 (EST) >> module.js?r=face658:4 >> Retrying call from Thu Feb 20 2014 11:46:56 GMT-0500 (EST) >> module.js?r=face658:4 >> Retrying call from Thu Feb 20 2014 11:47:16 GMT-0500 (EST) >> module.js?r=face658:4 >> Retrying call from Thu Feb 20 2014 11:47:16 GMT-0500 (EST) >> module.js?r=face658:4 >> >> >> I don't understand how this error just showed up without having changed >> anything on the monitor machine or the cluster it monitors. Any clues are >> welcome. >> > -- 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/63195796-37ed-4aae-ad9e-cdd9f7c09cff%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
