-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Kibana reporting error : spawn EACCES #15459
Comments
Thanks for filling, we're tracking this #8818 so I'm going to close this out to avoid discussions diverging. Currently we recommend running plugin installs as the kibana user, |
Hi Jonathan, the phantom bin is already own by the kibana user |
but still not working |
Ah I see. Can you enable verbose logging in kibana.yml with |
|
|
Hi, do we have any updates on this? I'd like to get it closed if it is no longer applicable. |
recap: if there's issues, usually double checking permissions is a good start. that includes other restrictions like apparmor, selinux, and noexec. deb and rpm packages install phantom to /var/lib/kibana. tar and zips install to the data folder inside kibana. I think we're good closing for now and we can reopen if there's more comments (sorry about the late reply jsdumont, hope things are working now) |
Thanks @jbudz! I like the suggestion about checking file permission on the binary |
Closing for a meta-issue on having Reporting do better in self-diagnosing problems: https://github.com/elastic/dev/issues/1087 |
Kibana version: 5.6.2
Elasticsearch version: 5.6.2
Server OS version: Centos7
Browser version: Chrome Version 62.0.3202.94 (Official Build) (64-bit)
Browser OS version: 2012 R2
Original install method (e.g. download page, yum, from source, etc.): RPM
Description of the problem including expected versus actual behavior: Unable to display report in Kibana
Steps to reproduce:
Errors in browser console (if relevant):There was an error generating your report for the "blah blah blah" dashboard: Error: spawn EACCES
Provide logs and/or server output (if relevant):
Dec 6 10:22:44 kibana: Unhandled rejection Error: spawn EACCES
Dec 6 10:22:44 kibana: at exports._errnoException (util.js:1018:11)
Dec 6 10:22:44 kibana: at ChildProcess.spawn (internal/child_process.js:319:11)
Dec 6 10:22:44 kibana: at exports.spawn (child_process.js:378:9)
Dec 6 10:22:44 kibana: at spawnPhantom (/usr/share/kibana/plugins/x-pack/node_modules/@elastic/node-phantom-simple/node-phantom-simple.js:143:19)
Dec 6 10:22:44 kibana: at Object.exports.create (/usr/share/kibana/plugins/x-pack/node_modules/@elastic/node-phantom-simple/node-phantom-simple.js:283:3)
Dec 6 10:22:44 kibana: at Phantom.cb (/usr/share/kibana/plugins/x-pack/plugins/reporting/server/lib/phantom/index.js:67:43)
Dec 6 10:22:44 kibana: at tryCatcher (/usr/share/kibana/plugins/x-pack/node_modules/bluebird/js/release/util.js:11:23)
Dec 6 10:22:44 kibana: at Promise.fromNode.Promise.fromCallback (/usr/share/kibana/plugins/x-pack/node_modules/bluebird/js/release/promise.js:173:30)
Dec 6 10:22:44 kibana: at new Phantom (/usr/share/kibana/plugins/x-pack/plugins/reporting/server/lib/phantom/index.js:67:17)
Dec 6 10:22:44 kibana: at Object.create (/usr/share/kibana/plugins/x-pack/plugins/reporting/server/lib/phantom/index.js:59:12)
Dec 6 10:22:44 kibana: at Promise.resolve.then.port (/usr/share/kibana/plugins/x-pack/plugins/reporting/export_types/printable_pdf/server/lib/screenshot.js:60:20)
Dec 6 10:22:44 kibana: at process._tickDomainCallback (internal/process/next_tick.js:135:7)
NOTE: I had to run this because the owner was root:root.
chown -R kibana:kibana /usr/share/kibana/plugins/
chown -R kibana:kibana /usr/share/kibana/optimize/bundles
Describe the feature:
The text was updated successfully, but these errors were encountered: