Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issue when installing plugins #66

Open
carioka88 opened this issue Jun 3, 2016 · 1 comment
Open

issue when installing plugins #66

carioka88 opened this issue Jun 3, 2016 · 1 comment

Comments

@carioka88
Copy link

Hello,
I am using the module kibana4 in my puppet manifest and I am having some troubles when installing kibana and plugins (as timelion or sense).

When running puppet, installing only kibana, there are not errors, and the kibana service is running correctly.
When running puppet, specifying that I want the kibana and plugins, then the kibana service does not start.
What is giving problems is the file .babelcache.json in /opt/kibana/optimize. It has these permissions:
-rw-r--r--. 1 root root .babelcache.json
When it should have:
-rw-r--r--. 1 kibana root .babelcache.json

If kibana is already installed and running, and you run puppet with the plugins, then it does not give this problem. It is only when you want to installed both for the first time.

I was trying to modify the puppet manifest, but I am getting a dependency cycle.
(Exec[install_kibana_plugin_heatmap] => Service[kibana4] => Kibana4::Plugin[heatmap] => Exec[install_kibana_plugin_heatmap]

Someone else having this problem?
In the meantime, I am modifying the .babelcache.json permissions.

Thanks!

@carioka88
Copy link
Author

The problem was understood and fixed in our side as follow:
After the kibana installation, if the kibana service is not running the file .babelcache.json is created with root permissions, and this generates other problems when trying to start kibana.
We propose this #67

We had to remove the notify and add the service kibana restart in the command execution.. otherwise it was giving a dependency cycle, when trying to request the kibana service running, and also notifying the service after the plugin installation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant