Cannot access grokdebugger in Kibana6 on FreeBSD 11

Elastic Stack Kibana
1

This is a cross posting from https://stackoverflow.com/questions/51754200/cannot-access-grokdebugger-in-kibana-6-on-freebsd-11 . I have posted its contents here. Thank you.

It appears that my kibana installation did not contain the grokdebugger plugin since I was not able to find it in /usr/local/www/kibana6/ and it did not appear under the Dev Tools pane.

I did install it by installing x-pack using elasticsearch-plugin and kibana-plugin. This required removing a few of these x-pack plugins after installation since they were reported as being red status upon visiting the Kibana page. However, I successfully removed them and Kibana loads as normal; but there is no grokdebugger. The grokdebugger source directory is present in /usr/local/www/kibana6/plugins/x-pack/plugins/, and its contents appear to be normal, but it does not appear in the Dev Tools section.

I would rather consult some experts before diving too much deeper and messing things up (more than I already have).

It is worth mentioning, this is a new installation so I am open to deleting anything or installing anything from scratch if that is cleaner or easiest.

Thanks~

Edit

I've noticed that only a few of the plugins that are in src/core_plugins are loaded, according to the logs:

elasticsearch kibana timelion metrics console

There are numerous other plugins in that directory which are not being loaded. I tried placing grokdebugger in there from where it was in plugins/x-pack, but it also was not picked up.

2

Since 6.3, the Elasticsearch and Kibana default distributions should include the Grok Debugger. You should not be needing to move files around.

Download Kibana and Elasticsearch.

Start them both, and you should have the Grok Debugger tab in Dev Tools.

3

Thank you for your response.I am reluctant to download the packages directly, since I used FreeBSD's official package distribution to install them, and I am wary of the complications of installing something with dependencies outside of the purview of the package system.

In any case, it appears that Grok Debugger was for whatever reason not present when I first installed ES and Kibana. Just to clarify, I have indeed installed ES and Kibana and they are started and functioning normally. I have also tried removing and reinstalling Kibana.

I have just realized that I did not have 6.3, as I thought, but 6.2.4, sorry about that. Do you know how I can install grokdebugger on this version?

4

In that case, you will need to install X-Pack in both Kibana and Elasticsearch. Make sure you restart the service after installing the plugin.

5

I did install X-Pack using elasticsearch-plugin and kibana-plugin, but several of the plugins were in 'red' state when I tried starting Kibana, so I removed those ones from kibana6/plugins/x-pack/plugins. grokdebugger was not one of the ones which was in red, state, so I kept it there. However it does not appear in the Dev Tools (Dev Tools goes directly to Console) and it does not appear to be loaded at startup by Kibana; currently Kibana appears to only load those plugins which are present in core_plugins.

6

In particular, it loads metrics, timelion, elasticsearch, kibana, and console:

    {"type":"log","@timestamp":"2018-08-09T02:52:27Z","tags":["status","plugin:kibana@6.2.4","info"],"pid":21720,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2018-08-09T02:52:27Z","tags":["status","plugin:elasticsearch@6.2.4","info"],"pid":21720,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2018-08-09T02:52:28Z","tags":["status","plugin:timelion@6.2.4","info"],"pid":21720,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2018-08-09T02:52:28Z","tags":["status","plugin:console@6.2.4","info"],"pid":21720,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2018-08-09T02:52:28Z","tags":["status","plugin:metrics@6.2.4","info"],"pid":21720,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2018-08-09T02:52:28Z","tags":["listening","info"],"pid":21720,"message":"Server running at http://192.168.12.5:5601"}
{"type":"log","@timestamp":"2018-08-09T02:52:28Z","tags":["status","plugin:elasticsearch@6.2.4","info"],"pid":21720,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}

Maybe I should change the log settings to better see what's going on during startup, why it would not be able to load the plugin.

7

To be honest, you shouldn't be removing the core and individual plugins from the filesystem. Not saying it won't work, but there might be cross dependencies.

I would recommend you start over. You should not need to manually manipulate the source code. That is what the yml configuration files are for. If you get to this point, we can investigate the red plugin state.

8

I installed xpack again with kibana-plugin and everything appears to work. Not sure what I was doing wrong. Apprecaite the responses

9

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.