ENOTDIR error when manually installing Marvel

Elastic Stack Kibana
1

I am trying to manually install Marvel through Kibana but regardless of what syntax I use I get a ENOTDIR error:

$bin/kibana plugin --install marvel --url file:/home1/isuser/Desktop/up/marvel-2.3.3.tar.gz

Installing marvel
Attempting to transfer from file:/home1/isuser/Desktop/up/marvel-2.3.3.tar.gz
Transferring 1611136 bytes....................
Transfer complete
Extracting plugin archive
Extraction complete
Plugin installation was unsuccessful due to error "ENOTDIR: not a directory, unlink '/home1/isuser/Desktop/kibana-4.5.1-linux-x64/installedPlugins/.plugin.installing/archive.part'"

I tried changing the number of slashes after file as recommended by a user here but that doesn't seem to fix the issue. Does anyone have some advice?

2

Since this is related to the other post, is this the file that you messed with or is this a clean version of the .tar.gz file?

3

file that I messed with. If I didn't add plugin-descriptors it would have thrown that error

4

So Kibana doesn't care about that file. Elasticsearch requires that file as part of its plugins, but Kibana uses a system more related to node.js (package.json).

Try with the original (or just redownload it).

5

awesome, "plugin installation complete". thanks.

i'm pretty new to elasticsearch obviously so maybe I'm missing something but after I start my node and I go to localhost:9200/_plugin/marvel shouldn't I see the UI (unless something didn't install correctly)? all I see is a blank screen

6

but after I start my node and I go to localhost:9200/_plugin/marvel shouldn't I see the UI (unless something didn't install correctly)? all I see is a blank screen

No worries. That was the old way in ES 1.x (and Marvel 1.x). You are expecting to see the Marvel "site plugin", which is how Marvel worked in Marvel 1.x. However, running a UI from a data store proved to be a workable, but-not-so-great idea, so we stopped doing it.

Now that the UI is a part of Kibana, you need to go to Kibana to visually use it. Assuming you have started Kibana (${KIBANA_DIR}/bin/kibana), then it starts up a node.js server listening for web requests at port 5601 by default.

Since you're running Kibana 4.5, the plugins appear under the 9 square-dots:

  1. Click on those.
  2. Select Marvel.

Voila, you should now be able to monitor your cluster.

Let me know if you run into any issues.

7

genius! thank you so much. now that installation is (supposedly) complete, do you think it's worth following the video on https://info.elastic.co/2016-03-AB-Test-Getting-Started-ES_Video.html?aliId=43084931 which is still using old installation methods and such, or is there a different video you recommend?

thanks again! I've been stuck on this for days!

1 Like
8

That video is definitely out of date, unfortunately. As you've noticed, Elasticsearch 1.6 and 2.x are kind of different beasts. We really started to lock things down and tie things together in 2.x. Fortunately, Elasticsearch 5.x is much, much closer to ES 2.x than ES 2.x was to ES 1.6.

As for better resources, you should probably take a look at these "Elastic{content}" groups of content:

We're actually in the process of updating the Getting Started webinar to be more relevant to ES 2.x, so be on the look out for a post on that in the future.

9

Thanks again.