# Reporting pdf generation error

**URL:** <https://discuss.elastic.co/t/reporting-pdf-generation-error/204535>\
**Category:** Kibana\
**Created:** [October 21, 2019, 6:43pm UTC](https://discuss.elastic.co/t/reporting-pdf-generation-error/204535 "2019-10-21T18:43:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sushmamagesh](https://avatars.discourse-cdn.com/v4/letter/s/8491ac/32.png) [@sushmamagesh](https://discuss.elastic.co/u/sushmamagesh)\
**Post date:** [October 21, 2019, 6:43pm UTC](https://discuss.elastic.co/t/reporting-pdf-generation-error/204535/1 "2019-10-21T18:43:25Z")

</div>

Hi - I am trying to generate a pdf report from Kibana7 and I am on Centos7.

Error I am getting is -

```
Unable to generate report
Error: Error spawning Chromium browser: Error: socket hang up

```

From kibana logs:

```
{"type":"error","@timestamp":"2019-10-21T18:19:55Z","tags":["warning","process"],"pid":2216,"level":"error","error":{"message":"Error: socket hang up\n at createHangUpError (_http_client.js:323:15)\n at Socket.socketOnEnd (_http_client.js:426:23)\n at Socket.emit (events.js:194:15)\n at endReadableNT (_stream_readable.js:1103: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:323:15)\n at Socket.socketOnEnd (_http_client.js:426:23)\n at Socket.emit (events.js:194:15)\n at endReadableNT (_stream_readable.js:1103: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:323:15)\n at Socket.socketOnEnd (_http_client.js:426:23)\n at Socket.emit (events.js:194:15)\n at endReadableNT (_stream_readable.js:1103:12)\n at process._tickCallback (internal/process/next_tick.js:63:19)"}
{"type":"error","@timestamp":"2019-10-21T18:19:55Z","tags":["warning","process"],"pid":2216,"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: 159641)","name":"UnhandledPromiseRejectionWarning","stack":"Error: socket hang up\n at createHangUpError (_http_client.js:323:15)\n at Socket.socketOnEnd (_http_client.js:426:23)\n at Socket.emit (events.js:194:15)\n at endReadableNT (_stream_readable.js:1103: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: 159641)"}
```

---

<div class="post-metadata">

**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\
**Post date:** [October 21, 2019, 9:19pm UTC](https://discuss.elastic.co/t/reporting-pdf-generation-error/204535/2 "2019-10-21T21:19:23Z")

</div>

Hi @sushmamagesh, unfortunately reporting errors aren't great at the moment. Kibana 7.5 will be released soon and contains a fix to improve these messages. Until then, there is a [troubleshooting guide](https://www.elastic.co/guide/en/kibana/current/reporting-troubleshooting.html) in the docs you can look at. If you search that page for "CentOS" you'll find some info on dependencies that may be missing in your current installation.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 18, 2019, 9:19pm UTC](https://discuss.elastic.co/t/reporting-pdf-generation-error/204535/3 "2019-11-18T21:19:29Z")

</div>

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