Marvel 2.1 basic licence. Cannot access cluster data

Elastic Stack Elasticsearch
1

I have an Elastic 2.1.0 cluster, logging to an external Marvel 2.1 with Kibana 4.3.1.

All worked fine with trial licenses, but when I updated them with a basic one, all clusters gone grayed out in Kibana and I cannot see info of any of them anymore.

There's nothing relevant in either cluster logs.

Has anyone encountered a similar issue?

2

Do you have Shield installed in the cluster?

3

No, only Marvel in both clusters.

4

Hi Alejandro,

The free Basic license enables most Marvel functionality, but support for multiple clusters from a single monitoring cluster requires a Gold or Platinum license. Note that you do not need to install Marvel on the monitoring cluster itself. If you do have multiple production clusters, you could configure one monitoring cluster per production cluster.

Cheers,
Steve

5

That worked! Thanks!

6

hi，mole，you have basic license ，marvel in both cluster can work ？But when I use this command （curl -XPUT -u admin 'http://:/_license?acknowledge=true' -d @license.json）to change basic one but marvel can't work? If I use （curl -XPUT -u admin 'http://:/_license' -d @license.json） this to change is not success。marvel on kibana always remind me license is Trial and Expired。I hope your help。

1 Like
7

Hi steve

I have same issus with free Basic license.
I have 1 monitoring node and 2 productions nodes in single cluster.

8

Hi Suntuo,

You must install the Marvel and licensing plugins on all nodes in your cluster. All nodes must then be restarted after the plugins are installed.

Thanks,
Steve

1 Like
9

Hi skearns
It worked a few days later and i didn't restart any node or service.
That's wired, but thank you anyway.

10

This was such a pain. I have a production and monitoring cluster so I had to remove the marvel plugin from the monitoring cluster. That was no big deal but it didn't take effect until I removed all my historical data :frowning:

11

Hi @jspooner,

I realize that it doesn't help you now, but we should have a fix for this in 5.0 to avoid that kind of issue (and moving forward).

For what it's worth, the installation should also become dramatically simpler now that Monitoring, Security, Watcher, and Licensing are all combined into a single plugin: x-pack.

Thanks,
Chris