Problems genarating report PDF

Hi,

I’m have graylog installed with the docker-compose method (image: graylog/graylog:3.0, just rebuild so i have the latest version Graylog 3.0.2+1686930). Enterprise plugin version 3.0.2 is installed from tarball (binaries in /usr/share/graylog/bin and the .jar file in /usr/share/graylog/plugin)

graylog_1 | 2019-07-19 13:23:19,804 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded plugin: Graylog Enterprise 3.0.2 [org.graylog.plugins.enterprise.EnterprisePlugin]

Trying to download a report PDF fails with error:

{"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/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 4.15.0-54-generic x86_64) (WARNING: The server did not provide any stacktrace information)\nCommand duration or timeout: 81 milliseconds\nBuild info: version: 'unknown', revision: 'unknown', time: 'unknown'\nSystem info: host: '41b3e3cc353d', ip: '172.18.0.4', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-54-generic', java.version: '1.8.0_212'\nDriver info: driver.version: RemoteWebDriver"}

as per suggestion on another post i tried running the headless-shell directly in the container

graylog@76c66dab06ed:~/bin$ ./headless_shell

[0719/123611.362289:WARNING:resource_bundle.cc(358)] locale_file_path.empty() for locale

[0719/123611.362897: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.

running it with the --no-sanbox doesn’t help much

graylog@76c66dab06ed:~/bin$ ./headless_shell --no-sandbox

[0719/124305.361995:WARNING:resource_bundle.cc(358)] locale_file_path.empty() for locale

[0719/124305.393451:WARNING:resource_bundle.cc(358)] locale_file_path.empty() for locale
Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"

[0719/124305.438201:ERROR:gpu_process_transport_factory.cc(967)] Lost UI shared context.

[0719/124305.473644:WARNING:resource_bundle.cc(358)] locale_file_path.empty() for locale

[0719/124305.474346:ERROR:egl_util.cc(59)] Failed to load GLES library: /usr/share/graylog/bin/swiftshader/libGLESv2.so: cannot open shared object file: No such file or directory

[0719/124305.477460:ERROR:viz_main_impl.cc(184)] Exiting GPU process due to errors during initialization

Disabling the sanbox from graylog.conf and restart didn’t help either

report_disable_sandbox = true

When I try to download a report PDF i get gateway timeout from the nginx proxy, and no errors in the graylog logs

graylog_1        | 2019-07-19 13:37:49,463 INFO : org.graylog.plugins.report.render.BrowserDriverService - Starting report render engine: http://localhost:9515

graylog_1        | 2019-07-19 13:37:50,093 INFO : org.openqa.selenium.remote.ProtocolHandshake - Detected dialect: OSS

But as the ./headless_shell --no-sandbox didn’t work directly from the container either I didn’t really expect this to work either.

Is there an option to disable the GPU acceleration for the report generation? Or am I missing something else?

epte

it looks like the fontconfig is not installed on your System:

http://docs.graylog.org/en/3.0/pages/reporting/setup.html#installation

The GPU error can be ignored.

Hi,

Actually fontconfig is installed

root@501ac1539a9b:/usr/share/graylog# apt-get install fontconfig
Reading package lists... Done
Building dependency tree
Reading state information... Done
fontconfig is already the newest version (2.11.0-6.7+b1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

the error is:

Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"

not sure about that.

Hi,

This comment indicated that it would be an issue with the version of chromium, however not sure if this applies here or how I could fix it if it does.

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