# Marvel does not work after upgrading to Elastic 2.3.2 **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-monitoring\ **Created:** [May 10, 2016, 3:03pm UTC](https://discuss.elastic.co/t/marvel-does-not-work-after-upgrading-to-elastic-2-3-2/49674 "2016-05-10T15:03:54Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![edalford11](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/edalford11/32/27571_2.png) [@edalford11](https://discuss.elastic.co/u/edalford11)\ **Post date:** [May 10, 2016, 3:03pm UTC](https://discuss.elastic.co/t/marvel-does-not-work-after-upgrading-to-elastic-2-3-2/49674/1 "2016-05-10T15:03:54Z")
I've just upgraded our elastic cluster from 2.1 to 2.3.2. Everything is working great except now marvel is constantly saying "No marvel data found". We have 4 elastic nodes in our cluster, all with marvel.agent.exporters: id1: type: http host: ["[http://10.0.68.51:9200](http://10.0.68.51:9200)"] Where that host is a separate node that serves as our monitor node, which has marvel 2.3 installed into Kibana 4.5. The data is coming into kibana just fine and the .marvel-es-data index is still there from before the upgrade. What is wrong here? ---
**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\ **Post date:** [May 10, 2016, 5:17pm UTC](https://discuss.elastic.co/t/marvel-does-not-work-after-upgrading-to-elastic-2-3-2/49674/2 "2016-05-10T17:17:38Z")
Hi, If it's complaining that No marvel data is found at the top level of the UI, then it generally means that the cluster-level details are not coming to the monitoring index. Can you verify that the elected master node is updated and running Marvel 2.3? Please run this from the monitored cluster and let me know what it comes back with: ```auto $ curl -XGET host:9200/_cat/plugins?v ``` ---
**Author:** ![edalford11](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/edalford11/32/27571_2.png) [@edalford11](https://discuss.elastic.co/u/edalford11)\ **Post date:** [May 10, 2016, 5:28pm UTC](https://discuss.elastic.co/t/marvel-does-not-work-after-upgrading-to-elastic-2-3-2/49674/3 "2016-05-10T17:28:20Z")
Thanks pickypg. I made sure marvel agent was updated and installed before starting the nodes back up after upgrading them. Now somehow the marvel agent is completely missing from every single node. Not sure how that happened but I'm sure thats the problem. I'm sure getting them installed again will fix this problem. ---
**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\ **Post date:** [May 10, 2016, 5:49pm UTC](https://discuss.elastic.co/t/marvel-does-not-work-after-upgrading-to-elastic-2-3-2/49674/4 "2016-05-10T17:49:58Z")
It happens. One important note for anyone that comes across this post (it may not apply to you): - Any plugin that modifies the way that Elasticsearch works requires that Elasticsearch be restarted for it to take effect because Java plugins are only loaded at startup. So, if you install the plugin after restarting a node, then it won't take effect until the next restart. Good luck! ---
**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, 1:43pm UTC](https://discuss.elastic.co/t/marvel-does-not-work-after-upgrading-to-elastic-2-3-2/49674/5 "2017-07-06T13:43:37Z")