# Reporting - PDF generation fail "Unable to generate report Error : Caught error spawning Chromium"

**URL:** <https://discuss.elastic.co/t/reporting-pdf-generation-fail-unable-to-generate-report-error-caught-error-spawning-chromium/208007>\
**Category:** Kibana\
**Created:** [November 15, 2019, 7:50am UTC](https://discuss.elastic.co/t/reporting-pdf-generation-fail-unable-to-generate-report-error-caught-error-spawning-chromium/208007 "2019-11-15T07:50:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lbosec](https://avatars.discourse-cdn.com/v4/letter/l/94ad74/32.png) [@lbosec](https://discuss.elastic.co/u/lbosec)\
**Post date:** [November 15, 2019, 7:50am UTC](https://discuss.elastic.co/t/reporting-pdf-generation-fail-unable-to-generate-report-error-caught-error-spawning-chromium/208007/1 "2019-11-15T07:50:38Z")

</div>

Hello,

I get an error each time i want to generate a PDF report, a pop-up say " Unable to generate report Error : Caught error spawning Chromium".

I already try a lot of things i found on other discussion but nothing works...

Kibana 6.5 is installed on a SLES 12 SP2

A solution provided is to ensure that headless\_shell binary located in Kibana data directory is owned by the user who is running Kibana, that the user has the execute permission, that's the case :

```
admin@linux-5t15:~> ps -eaf |grep kiba
root 2473 2220 8 15:29 pts/1 00:00:22 ./kibana-6.5.4-linux-x86_64/bin/../node/bin/node --no-warnings ./kibana-6.5.4-linux-x86_64/bin/../src/cli
admin 2578 2554 0 15:34 pts/2 00:00:00 grep --color=auto kiba
 
 
 
admin@linux-5t15:~> ll ./kibana-6.5.4-linux-x86_64/data/
total 4
drwxr-xr-x 3 root root 43 Nov 13 14:56 headless_shell-linux
-rw-r--r-- 1 root root 36 Nov 13 10:49 uuid

 
admin@linux-5t15:~> ll ./kibana-6.5.4-linux-x86_64/data/headless_shell-linux/
total 111116
-rwxr-xr-x 1 root root 113780392 Nov 13 10:49 headless_shell
drwx------ 2 root root 6 Nov 13 14:56 locales

```

I also installed : fontconfig, freetype, ipa-gothic-fonts, xorg-x11-fonts, xorg-x11-fonts-core, mozilla-nss, mozilla-nspr but still the same issue.

I try ldd command to see missing dependencies and i think all is alright :

```
    linux-5t15:/home/admin # ldd ./kibana-6.5.4-linux-x86_64/data/headless_shell-linux/headless_shell 
	linux-vdso.so.1 (0x00007ffdd91f6000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f01f5343000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f01f5126000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f01f4f1e000)
	libnss3.so => /usr/lib64/libnss3.so (0x00007f01f4bfb000)
	libnssutil3.so => /usr/lib64/libnssutil3.so (0x00007f01f49cd000)
	libnspr4.so => /usr/lib64/libnspr4.so (0x00007f01f478f000)
	libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f01f4565000)
	libuuid.so.1 => /usr/lib64/libuuid.so.1 (0x00007f01f4360000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f01f4063000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f01f3e4c000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f01f3aab000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f01f5547000)
	libplc4.so => /usr/lib64/libplc4.so (0x00007f01f38a6000)
	libplds4.so => /usr/lib64/libplds4.so (0x00007f01f36a2000)

```

need your help to make it works please 🙂

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [November 18, 2019, 8:44pm UTC](https://discuss.elastic.co/t/reporting-pdf-generation-fail-unable-to-generate-report-error-caught-error-spawning-chromium/208007/2 "2019-11-18T20:44:16Z")

</div>

I think kibana is not run by your own user, it should be run by the `elasticsearch` user when ran as a service.

---

<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:** [December 16, 2019, 8:44pm UTC](https://discuss.elastic.co/t/reporting-pdf-generation-fail-unable-to-generate-report-error-caught-error-spawning-chromium/208007/3 "2019-12-16T20:44:21Z")

</div>

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