Closed tsullivan closed 5 years ago
2019-07-22T23:46:59.864709000Z {"type":"log","@timestamp":"2019-07-22T23:46:59Z","tags":["reporting","browser-driver","chromium-driver-factory","headless-chromium-driver","error"],"pid":1,"message":"waitForSelector [data-shared-item],[data-shared-items-count] failed on https://web:8080/kibana/app/canvas#/export/workpad/pdf/workpad-6ea6dc46-a7ad-4275-87c6-7a58669160b2/page/1?forceNow=2019-07-22T23:42:20.950Z"}
When I load that URL in my browser, I see this:
It has just enough stuff on the page to make the Reporting browser think it is on the right place, and it's not seeing any toast error that would cause a meaningful failure.
The workpad loads OK when I navigate to it from the workpad loader.
This probably explains something I didn't understand in the logs:
2019-07-22T23:45:12.531501900Z {"type":"log","@timestamp":"2019-07-22T23:45:12Z","tags":["reporting","screenshots","browser","debug"],"pid":1,"message":"JSHandle@error"}
Initially, when I saw that line I mistaked it for the: Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-eval' 'nonce-
The logs are correct in saying the data-shared-item
data on the page could not be found:
cc @elastic/kibana-canvas
I've seen when running 7.2.0 from source, the error shown as the failure reason is different. When running in source, Reporting shows the error message found in the browser JS console and gave that as the failure reason.
When running a build (Docker, with Kibana behind a proxy), I get a meaningless "Max attempts" error
7.2.0-specific bug. Closing via https://github.com/elastic/kibana/pull/41298
Hi Tim,
Can you confirm this issue is now resolved? I'm stuck on 7.2 with none of my PDF reports working and awaiting the fix for this desperately.
Thanks
Hi @Eniqmatic https://github.com/elastic/kibana/pull/41298 is targeting 7.2.1, which is the next patch coming up in the 7.2 minor. We don't announce release dates, but it'll be coming soon.
Hi Tim,
I don't see this issue resolved in the change log for 7.3, would I assume it is not yet fixed in that version?
Thanks
@Eniqmatic it likely is not fixed, and we're tracking a number of issues around PDFs in Kibana
We suspect that this is a combination effort and that some PDF functionality will be impacted in 7.3.
The release notes don't mention this as a resolved Reporting issue. The issue Reporting issue happened because Canvas was crashing when rendering its export view: https://github.com/elastic/kibana/pull/41298
The export view that I looked up to find the page crash can be found in the debug logs of Kibana. Search for opening url
. For example:
{"type":"log","@timestamp":"2019-08-01T20:57:40Z","tags":["reporting","screenshots","debug"],"pid":1,"message":"opening https://web:8080/kibana/app/canvas#/export/workpad/pdf/workpad-cada9628-a635-4e69-a63d- e7955acfdbfc/page/6?forceNow=2019-08-01T20%3A55%3A38.395Z"}
We're working on making this kind of message more evident in the logs, since it was necessary to try to run that URL to find that the Canvas page was crashing. And we're working on the other stability and performance issues that Shaun listed
Also, my understanding is the Canvas fix should be listed in the release notes for 7.2.1: https://www.elastic.co/guide/en/kibana/7.2/release-notes-7.2.1.html
I'll check if this was an oversight
Thanks Shaun and Tim. Hopefully this is implemented in 7.2.1, this is killing our reports at the moment and we are having to run a bunch of things manually for many many weeks now.
@tsullivan, Thank you for looking into this. Please let us know if this is fixed in 7.2.1. Thank you for your confirmation.
@MarianMM confirmed.
The fix in Canvas closes this issue because Canvas no longer crashes when Reporting scans the page for PDF.
If customers are still having problems with any part of Reporting in any other version, please turn on debug logs in Kibana and look for the parts that show what the Reporting headless browser is doing on the server side of Kibana. You'll find:
What's always harder to find and detect are environmental problem with Reporting: not able to connect to Kibana webserver due to firewalling, not able to log in due to invalid auth cache, trying to open a saved object but getting a 404, not enough RAM or CPU on the machine for Chromium, etc.
Describe the bug: Canvas can not export a workpad to PDF in 7.2.0.
This appears to be a resurfacing of https://github.com/elastic/kibana/issues/25052, however this workflow does work in master.
Steps to reproduce:
My verbose debug logs show that Reporting navigated to the page and loaded the workpad:
Therefore, it could be a problem with the expected
data-shared-item
attributes on the visualization