PDF export not enabled in Kibana v.7.7

Elastic Stack Kibana
1

Hi everybody,
I read docs about PDF export but I'm not able to make it work.
I am using full-stack v7.7.1 and native realm.
I tried to save a test dashboard but I cannot create PDF report since I cannot see that feature.

Currently, I'm using elastic user so I'm quite confident that should have all the correct permissions.
I set in kibana.yml also the xpack.security.encryptionKey

can you help me?

edit:

restarting Kibana I saw these errors in the log:

{"type":"log","@timestamp":"2020-07-09T09:21:21Z","tags":["error","reporting"],"pid":8224,"message":"The Reporting plugin encountered issues launching Chromium in a self-test. You may have trouble generating reports."}

{"type":"log","@timestamp":"2020-07-09T09:21:21Z","tags":["error","reporting"],"pid":8224,"message":"ErrorEvent {\n  target:\n   WebSocket {\n     _events:\n      [Object: null prototype] { open: [Function], error: [Function] },\n     _eventsCount: 2,\n     _maxListeners: undefined,\n     readyState: 3,\n     protocol: '',\n     _binaryType: 'nodebuffer',\n     _closeFrameReceived: false,\n     _closeFrameSent: false,\n     _closeMessage: '',\n     _closeTimer: null,\n     _closeCode: 1006,\n     _extensions: {},\n     _receiver: null,\n     _sender: null,\n     _socket: null,\n     _isServer: false,\n     _redirects: 0,\n     url:\n      'ws://127.0.0.1:42060/devtools/browser/6e60c2eb-b96f-489c-9abe-784242a87876',\n     _req: null },\n  type: 'error',\n  message: 'connect ECONNRESET 127.0.0.1:42060',\n  error:\n   { Error: connect ECONNRESET 127.0.0.1:42060\n       at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)\n     errno: 'ECONNRESET',\n     code: 'ECONNRESET',\n     syscall: 'connect',\n     address: '127.0.0.1',\n     port: 42060 } }"}

{"type":"log","@timestamp":"2020-07-09T09:21:21Z","tags":["warning","reporting"],"pid":8224,"message":"See Chromium's log output at \"/var/lib/kibana/headless_shell-linux/chrome_debug.log\""}

{"type":"log","@timestamp":"2020-07-09T09:21:21Z","tags":["error","reporting"],"pid":8224,"message":"Error: Could not close browser client handle!\n    at browserFactory.test.then.browser (/usr/share/kibana/x-pack/legacy/plugins/reporting/server/lib/validate/validate_browser.js:26:15)\n    at process._tickCallback (internal/process/next_tick.js:68:7)"}

{"type":"log","@timestamp":"2020-07-09T09:21:21Z","tags":["warning","reporting"],"pid":8224,"message":"Reporting plugin self-check generated a warning: Error: Could not close browser client handle!"}

checking also chrome_debug.log I saw:

[0709/113340.169523:WARNING:resource_bundle.cc(358)] locale_file_path.empty() for locale 
[0709/113340.169736:INFO:cpu_info.cc(53)] Available number of cores: 8
[0709/113340.169770:VERBOSE1:zygote_main_linux.cc(217)] ZygoteMain: initializing 0 fork delegates
[0709/113340.186582:WARNING:resource_bundle.cc(358)] locale_file_path.empty() for locale
2

Hello,

The chrome debug log looks pretty good, those warnings shouldn't have anything to do with this. I'm more worried about those errors in the Kibana log. Can you check the folder/files owner and permissions on for the reporting chromium?

3

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