# Report Generation Error **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [February 15, 2019, 11:56am UTC](https://community.graylog.org/t/report-generation-error/8889 "2019-02-15T11:56:55Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![unixfun](https://avatars.discourse-cdn.com/v4/letter/u/74df32/32.png) [@unixfun](https://community.graylog.org/u/unixfun)\ **Post date:** [February 15, 2019, 11:56am UTC](https://community.graylog.org/t/report-generation-error/8889/1 "2019-02-15T11:56:55Z")
I’m trying to generate a report using the Enterprise 3.0 feature set. I get the following error from the UI (IPs removed): `{"type":"ApiError","message":"Timed out waiting for driver server to start.\nBuild info: version: 'unknown', revision: 'unknown', time: 'unknown'\nSystem info: host: '', ip: '', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-957.5.1.el7.x86_64', java.version: '1.8.0_191'\nDriver info: driver.version: unknown"}` I see the following error message in /var/log/graylog/server.log: ```auto 2019-02-15T11:50:12.632Z ERROR [OsProcess] org.apache.commons.exec.ExecuteException: Process exited with an error: 127 (Exit value: 127) 2019-02-15T11:50:12.745Z ERROR [AnyExceptionClassMapper] Unhandled exception in REST resource org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start. Build info: version: 'unknown', revision: 'unknown', time: 'unknown' System info: host: '', ip: '', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-957.5.1.el7.x86_64', java.version: '1.8.0_191' Driver info: driver.version: unknown at org.openqa.selenium.remote.service.DriverService.waitUntilAvailable(DriverService.java:202) ~[?:?] at org.openqa.selenium.remote.service.DriverService.start(DriverService.java:188) ~[?:?] at org.graylog.plugins.report.render.RemoteBrowserService.connectDriver(RemoteBrowserService.java:135) ~[?:?] at org.graylog.plugins.report.render.RemoteBrowserService.connectDriver(RemoteBrowserService.java:111) ~[?:?] at org.graylog.plugins.report.api.ReportService.fetchPdf(ReportService.java:259) ~[?:?] at org.graylog.plugins.report.rest.ReportResource.generateReport(ReportResource.java:156) ~[?:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_191] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_191] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_191] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_191] at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) ~[graylog.jar:?] at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144) ~[graylog.jar:?] at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161) ~[graylog.jar:?] at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160) ~[graylog.jar:?] at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99) ~[graylog.jar:?] at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389) ~[graylog.jar:?] at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347) ~[graylog.jar:?] at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102) ~[graylog.jar:?] at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326) [graylog.jar:?] at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) [graylog.jar:?] at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) [graylog.jar:?] at org.glassfish.jersey.internal.Errors.process(Errors.java:315) [graylog.jar:?] at org.glassfish.jersey.internal.Errors.process(Errors.java:297) [graylog.jar:?] at org.glassfish.jersey.internal.Errors.process(Errors.java:267) [graylog.jar:?] at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) [graylog.jar:?] at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) [graylog.jar:?] at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) [graylog.jar:?] at org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpContainer.service(GrizzlyHttpContainer.java:384) [graylog.jar:?] at org.glassfish.grizzly.http.server.HttpHandler$1.run(HttpHandler.java:224) [graylog.jar:?] at com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:181) [graylog.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_191] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_191] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191] Caused by: org.openqa.selenium.net.UrlChecker$TimeoutException: Timed out waiting for [http://localhost:9515/status] to be available after 20000 ms at org.openqa.selenium.net.UrlChecker.waitUntilAvailable(UrlChecker.java:100) ~[?:?] at org.openqa.selenium.remote.service.DriverService.waitUntilAvailable(DriverService.java:197) ~[?:?] ... 32 more Caused by: java.util.concurrent.TimeoutException at java.util.concurrent.FutureTask.get(FutureTask.java:205) ~[?:1.8.0_191] at com.google.common.util.concurrent.SimpleTimeLimiter.callWithTimeout(SimpleTimeLimiter.java:156) ~[graylog.jar:?] at org.openqa.selenium.net.UrlChecker.waitUntilAvailable(UrlChecker.java:75) ~[?:?] at org.openqa.selenium.remote.service.DriverService.waitUntilAvailable(DriverService.java:197) ~[?:?] ... 32 more ``` Note: If I monitor the system for port 9515 – I never see a listener brought up for the report generator. ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [February 15, 2019, 12:15pm UTC](https://community.graylog.org/t/report-generation-error/8889/2 "2019-02-15T12:15:45Z")
Please use proper formatting - without that your posting is nearly impossible. So quick, edit your posting and surround the log message with ````` like described in the FAQ: [https://community.graylog.org/faq#format-markdown](https://community.graylog.org/faq#format-markdown) That makes it more likely that someone can help you. ---
**Author:** ![unixfun](https://avatars.discourse-cdn.com/v4/letter/u/74df32/32.png) [@unixfun](https://community.graylog.org/u/unixfun)\ **Post date:** [February 15, 2019, 12:18pm UTC](https://community.graylog.org/t/report-generation-error/8889/3 "2019-02-15T12:18:20Z")
Formatting has been added per your request. ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [February 15, 2019, 12:20pm UTC](https://community.graylog.org/t/report-generation-error/8889/4 "2019-02-15T12:20:53Z")
How did you install Graylog and the enterprise plugins? ---
**Author:** ![unixfun](https://avatars.discourse-cdn.com/v4/letter/u/74df32/32.png) [@unixfun](https://community.graylog.org/u/unixfun)\ **Post date:** [February 15, 2019, 12:28pm UTC](https://community.graylog.org/t/report-generation-error/8889/5 "2019-02-15T12:28:23Z")
I used the RPM distribution method of installation. I followed the CentOS installation instructions. ---
**Author:** ![edmundo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/edmundo/32/2161_2.png) [@edmundo](https://community.graylog.org/u/edmundo)\ **Post date:** [February 15, 2019, 2:26pm UTC](https://community.graylog.org/t/report-generation-error/8889/6 "2019-02-15T14:26:18Z")
Hi Dustin, Could you please verify that the folder indicated in the `bin_dir` option of your Graylog configuration file has the following binary files? ```auto headless_shell chromedriver chromedriver_start.sh ``` Also make sure that those binaries have the right permissions (and owner) so that the user executing Graylog server can also execute them. Hope that helps. ---
**Author:** ![unixfun](https://avatars.discourse-cdn.com/v4/letter/u/74df32/32.png) [@unixfun](https://community.graylog.org/u/unixfun)\ **Post date:** [February 15, 2019, 3:00pm UTC](https://community.graylog.org/t/report-generation-error/8889/7 "2019-02-15T15:00:24Z")
The local graylog server is running under the ‘graylog’ user. The permissions show read and execute for all users: ```auto 4 -rwxr-xr-x. 1 root root 798 Feb 11 13:57 graylog-server 111944 -rwxr-xr-x. 1 root root 114627328 Feb 11 13:58 headless_shell 4 -rwxr-xr-x. 1 root root 132 Feb 11 13:58 chromedriver_start.sh 8368 -rwxr-xr-x. 1 root root 8565408 Feb 11 13:58 chromedriver ``` The directory is accessible for the graylog user account as well. Any other ideas? ---
**Author:** ![edmundo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/edmundo/32/2161_2.png) [@edmundo](https://community.graylog.org/u/edmundo)\ **Post date:** [February 15, 2019, 3:40pm UTC](https://community.graylog.org/t/report-generation-error/8889/8 "2019-02-15T15:40:46Z")
Is that the `bin_dir` directory set in your Graylog server configuration file? Also, could you try executing both the `headless_shell` and `chromedriver` binaries on a normal shell and share the output with us? ---
**Author:** ![unixfun](https://avatars.discourse-cdn.com/v4/letter/u/74df32/32.png) [@unixfun](https://community.graylog.org/u/unixfun)\ **Post date:** [February 15, 2019, 3:57pm UTC](https://community.graylog.org/t/report-generation-error/8889/9 "2019-02-15T15:57:58Z")
Sure thing – here you go: ```auto ./chromedriver: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory [danders@ip-172-32-10-253 bin]$ ./headless_shell [0215/155618.653317:WARNING:resource_bundle.cc(358)] locale_file_path.empty() for locale [0215/155618.656798:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox. #0 0x000003efdfdf #1 0x000003e81a50 #2 0x00000515db40 #3 0x000003e34103 #4 0x0000051644b8 #5 0x000003e2d3a1 #6 0x000003f20ee8 #7 0x000003f20f75 #8 0x000003e6aa72 #9 0x7f0896c8b3d5 __libc_start_main #10 0x00000259202a _start Received signal 6 #0 0x000003efdfdf #1 0x000003efdb51 #2 0x7f089832f5d0 #3 0x7f0896c9f207 __GI_raise #4 0x7f0896ca08f8 __GI_abort #5 0x000003efc985 #6 0x000003e81ec2 #7 0x00000515db40 #8 0x000003e34103 #9 0x0000051644b8 #10 0x000003e2d3a1 #11 0x000003f20ee8 #12 0x000003f20f75 #13 0x000003e6aa72 #14 0x7f0896c8b3d5 __libc_start_main #15 0x00000259202a _start r8: 00007f08989537c0 r9: 0000000000000002 r10: 0000000000000008 r11: 0000000000000206 r12: 00007ffd7925d638 r13: 0000000000000161 r14: 00007ffd7925d640 r15: 00007ffd7925d648 di: 0000000000001611 si: 0000000000001611 bp: 00007ffd7925cc90 bx: 00007ffd7925ccf0 dx: 0000000000000006 ax: 0000000000000000 cx: ffffffffffffffff sp: 00007ffd7925cb58 ip: 00007f0896c9f207 efl: 0000000000000206 cgf: 0000000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated. ``` ---
**Author:** ![unixfun](https://avatars.discourse-cdn.com/v4/letter/u/74df32/32.png) [@unixfun](https://community.graylog.org/u/unixfun)\ **Post date:** [February 15, 2019, 4:08pm UTC](https://community.graylog.org/t/report-generation-error/8889/10 "2019-02-15T16:08:58Z")
I installed libX11 (yum install libX11) which resolved the chromedriver execution issue. However, here is the new error message I receive when trying to invoke a report from the UI: ```auto {"type":"ApiError","message":"unknown error: Chrome failed to start: exited abnormally\n (unknown error: DevToolsActivePort file doesn't exist)\n (The process started from chrome location /usr/share/graylog-server/bin/headless_shell is no longer running, so ChromeDriver is assuming that Chrome has crashed.)\n (Driver info: chromedriver=72.0.3583.1 (9ae827a6f6bbc9186d4e79681de885ce77d5bfe9),platform=Linux 3.10.0-957.5.1.el7.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)\nCommand duration or timeout: 67 milliseconds\nBuild info: version: 'unknown', revision: 'unknown', time: 'unknown'\nSystem info: host: '', ip: '', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-957.5.1.el7.x86_64', java.version: '1.8.0_191'\nDriver info: driver.version: RemoteWebDriver"} ``` ---
**Author:** ![marius](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/marius/32/14_2.png) [@marius](https://community.graylog.org/u/marius)\ **Post date:** [February 15, 2019, 4:09pm UTC](https://community.graylog.org/t/report-generation-error/8889/11 "2019-02-15T16:09:42Z")
@unixfun looks like you are running a RedHat/CentOS system with a pretty old kernel. Either update to a 4.x kernel or disable reporting sandbox with: report\_disable\_sandbox = true In the server configuration file. ---
**Author:** ![unixfun](https://avatars.discourse-cdn.com/v4/letter/u/74df32/32.png) [@unixfun](https://community.graylog.org/u/unixfun)\ **Post date:** [February 15, 2019, 4:41pm UTC](https://community.graylog.org/t/report-generation-error/8889/12 "2019-02-15T16:41:21Z")
Interesting note is that I used the default AWS 7.5 Centos Base image and it has a 3.x kernel. I upgraded the kernel to 4.2 and still received an error with headless\_shell looking for libGLEXv2.so I installed chromium-libs-71.0.3578.98 after running `yum whatprovides '*/libGLESv2.so*'` and restarted graylog. With the addition of this package, I was able to successfully create a report. I suggest additional Linux requirements be added to the documentation for future users. Thanks for the help! ---
**Author:** ![marius](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/marius/32/14_2.png) [@marius](https://community.graylog.org/u/marius)\ **Post date:** [February 15, 2019, 4:50pm UTC](https://community.graylog.org/t/report-generation-error/8889/13 "2019-02-15T16:50:49Z")
Cool that it is working now for you! We will add more details to the documentation soon. The error regarding libGLES could be ignored, since in headless\_mode no graphic acceleration is needed anyways. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [March 1, 2019, 4:57pm UTC](https://community.graylog.org/t/report-generation-error/8889/14 "2019-03-01T16:57:15Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.