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

deb package does not have correct permissions for directory #6085

Closed
robin13 opened this issue Feb 3, 2016 · 6 comments
Closed

deb package does not have correct permissions for directory #6085

robin13 opened this issue Feb 3, 2016 · 6 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience

Comments

@robin13
Copy link
Contributor

robin13 commented Feb 3, 2016

Installed with debian package - kibana likes to write to /opt/kibana/optimize/.babelcache.json, but the file is owned by root...

Error: EACCES, permission denied '/opt/kibana/optimize/.babelcache.json'
@rashidkpc rashidkpc added the bug Fixes for quality problems that affect the customer experience label Feb 3, 2016
@rashidkpc
Copy link
Contributor

Also this #6091

@jbudz
Copy link
Member

jbudz commented Feb 3, 2016

@robin13 Did your install process deviate from https://www.elastic.co/guide/en/kibana/4.4/setup.html at all? The post install script should chown the optimize folder to kibana.

@betelgius87
Copy link

I resolve this issue with running command 'chmod 666 .babelcache.json'

@robin13
Copy link
Contributor Author

robin13 commented Feb 4, 2016

Process to reproduce:

Install deb package, then install marvel plugin (need to be root to do this).

sudo bin/kibana plugin --install elasticsearch/marvel/latest

Of course it can be fixed by chown-ing back to kibana user after

sudo chown kibana:root /opt/kibana/optimize/.babelcache.json

In addition - if Kibana has been run once (as kibana user), then the .babelcache.json already exists with the correct user/group, so installing the plugin does not break this.

This state occurred when automating kibana install with Ansible, so I guess I can add the chown rule to the playbook.

@robin13 robin13 closed this as completed Feb 4, 2016
@nikolay
Copy link

nikolay commented Feb 22, 2016

@robin13 Is this fixed in master?

@robin13
Copy link
Contributor Author

robin13 commented Feb 23, 2016

@nikolay This is not fixed, and IMO cannot be fixed from Kibana - this is an (unavoidable?) side effect of installing plugins with a configuration management system running as root. The workaround is to chown the babelcache file as part of your deployment process after installing plugins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience
Projects
None yet
Development

No branches or pull requests

5 participants