Kibana reporting pdf with error: "Error: Error spawning Chromium browser: Error: socket hang up"

hi, i want to use kibana reporting pdf dashbord, but i got follow error
image

and i foudn error logs in my kibana log:

{"type":"error","@timestamp":"2019-02-17T07:03:46Z","tags":["warning","process"],"pid":18769,"level":"error","error":{"message":"Error: socket hang up\n    at createHangUpError (_http_client.js:322:15)\n    at Socket.socketOnEnd (_http_client.js:425:23)\n    at Socket.emit (events.js:187:15)\n    at endReadableNT (_stream_readable.js:1094:12)\n    at process._tickCallback (internal/process/next_tick.js:63:19)","name":"UnhandledPromiseRejectionWarning","stack":"UnhandledPromiseRejectionWarning: Error: socket hang up\n    at createHangUpError (_http_client.js:322:15)\n    at Socket.socketOnEnd (_http_client.js:425:23)\n    at Socket.emit (events.js:187:15)\n    at endReadableNT (_stream_readable.js:1094:12)\n    at process._tickCallback (internal/process/next_tick.js:63:19)\n    at emitWarning (internal/process/promises.js:81:15)\n    at emitPromiseRejectionWarnings (internal/process/promises.js:120:9)\n    at process._tickCallback (internal/process/next_tick.js:69:34)"},"message":"Error: socket hang up\n    at createHangUpError (_http_client.js:322:15)\n    at Socket.socketOnEnd (_http_client.js:425:23)\n    at Socket.emit (events.js:187:15)\n    at endReadableNT (_stream_readable.js:1094:12)\n    at process._tickCallback (internal/process/next_tick.js:63:19)"}
{"type":"error","@timestamp":"2019-02-17T07:03:46Z","tags":["warning","process"],"pid":18769,"level":"error","error":{"message":"Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)","name":"UnhandledPromiseRejectionWarning","stack":"Error: socket hang up\n    at createHangUpError (_http_client.js:322:15)\n    at Socket.socketOnEnd (_http_client.js:425:23)\n    at Socket.emit (events.js:187:15)\n    at endReadableNT (_stream_readable.js:1094:12)\n    at process._tickCallback (internal/process/next_tick.js:63:19)"},"message":"Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)"}

and error log in chrome_debug.log as follows:

[0217/124726.158736:WARNING:resource_bundle.cc(358)] locale_file_path.empty() for locale
[0217/124726.158900:INFO:cpu_info.cc(46)] Available number of cores: 24
[0217/124726.158935:VERBOSE1:zygote_main_linux.cc(217)] ZygoteMain: initializing 0 fork delegates
[0217/124726.180343:WARNING:resource_bundle.cc(358)] locale_file_path.empty() for locale
[0217/124726.180742:ERROR:egl_util.cc(59)] Failed to load GLES library: /usr/local/kibana-6.6.0-linux-x86_64/data/headless_shell-linux/swiftshader/libGLESv2.so: cannot open shared object file: No such file or directory
[0217/124726.180772:VERBOSE1:gpu_init.cc(238)] gl::init::InitializeGLNoExtensionsOneOff failed
[0217/124726.182461:ERROR:viz_main_impl.cc(184)] Exiting GPU process due to errors during initialization
[0217/124726.182900:VERBOSE1:statistics_recorder.cc(410)] Collections of all histograms

could anyone help this? many thanks.

Hello,

Can you please post which distribution and the version of your stack?

@joelgriffith @tsullivan

Thanks,
Bhavya

i use stack 6.6.0

Hi, we're using Puppeteer for launching the headless browser process on the server that will open the URL to the saved object in Kibana and take the screenshot.

If you've already checked the troubleshooting information on Reporting in the Elastic documentation and that didn't resolve it, also take a look at the troubleshooting information in the Puppeteer documentation: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

We're working on improving the startup and diagnostic capabilities for reporting. Please bear with us! Thanks

@tsullivan after installed dependencies listed in https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md, i can now generate pdf report, thank you very much.

Glad to hear you got it working!

I have a pull request open to improve the documentation for Getting Started and Troubleshooting with reporting: https://github.com/elastic/kibana/pull/31539/files

If you have a minute, I'd appreciate if you could take a look and see if these changes would have helped the issue for you.

Thanks!

good job,especially the System Dependencies part mentioned, it solved my problem.

1 Like

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