Kibana 6.2.3 -> 6.2.4: Error: Invalid dimensions for plot, width = 473, height = 0

[diranged]

We recently upgraded from ES 6.2.3 -> 6.2.4 due to a leaky file handle issue (Open File Handles leaking on 6.2.3 nodes..?). To keep Kibana happy, we upgraded it as well to 6.2.4.

We have a new issue now though - the Kibana 6.2.4 monitoring UI throws an error when it loads up:

vendors.bundle.js?v=16627:116 Error: Invalid dimensions for plot, width = 473, height = 0
    at Canvas.resize (commons.bundle.js?v=16627:45)
    at new Canvas (commons.bundle.js?v=16627:45)
    at commons.bundle.js?v=16627:45
    at new Plot (commons.bundle.js?v=16627:45)
    at Function.$.plot (commons.bundle.js?v=16627:45)
    at ChartTarget.value (monitoring.bundle.js?v=16627:1)
    at ChartTarget.value (monitoring.bundle.js?v=16627:1)
    at commitLifeCycles (commons.bundle.js?v=16627:45)
    at c (commons.bundle.js?v=16627:45)
    at k (commons.bundle.js?v=16627:45)
    at p (commons.bundle.js?v=16627:45)
    at y (commons.bundle.js?v=16627:45)
    at D (commons.bundle.js?v=16627:45)
    at Object.updateContainer (commons.bundle.js?v=16627:45)
    at commons.bundle.js?v=16627:45
    at Object.unbatchedUpdates (commons.bundle.js?v=16627:45)

The UI is pretty unusable, looking like this:

[Stacey_Gammon]

Yes that UI doesn't look right at all.

I upgraded from 6.2.3 to 6.2.4 and wasn't able to repro.

What page in monitoring did you screenshot that from? The landing page when you click on the monitoring app, or the Overview page in monitoring? If you have access to the landing page, do any of the other sub sections work? e.g. if you click on Nodes or Indices

cc @tsullivan @pickypg - you guys see anything like this before?

[pickypg (Chris Earle)]

That appears to be an index-level page based on the screenshot. I am also unable to reproduce this as well, but it appears to be caused by at least one of the charts on the page based on the error.

Does it happen on any other page(s), or just this one page and is it specific to this index (suggesting it's the index's data that triggers the condition)? Does resizing the browser window, then refreshing the page help?

[diranged]

This happens basically on any of the "Monitoring" pages. We do a pretty basic install of Kibana w/ the Elastic.co provided Puppet module (v6.0.1). Double checking the Kibana logs, I see this in the Kibana error log:

FATAL { Error: EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/ml.style.css'
    at Error (native)
  cause: 
   { Error: EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/ml.style.css'
       at Error (native)
     errno: -13,
     code: 'EACCES',
     syscall: 'open',
     path: '/usr/share/kibana/optimize/bundles/ml.style.css' },
  isOperational: true,
  errno: -13,
  code: 'EACCES',
  syscall: 'open',
  path: '/usr/share/kibana/optimize/bundles/ml.style.css' }

I've seen some permissions issues here before, so I wiped out the bundles directory and restarted Kibana. That seems to have solved it. It seems like its some issue with the Kibana puppet module and the order-of-operations.. some files get owned by root before Kibana starts up, and then it can't properly generate the bundles.

[pickypg (Chris Earle)]

@diranged

Thanks for the update. I'll add an issue to the Puppet module to point this out.

Issue: Unexpected Permissions issues

If you have any other issues, please add them to the ticket there so that the maintainer can properly fix it (I'm not a Puppet expert unfortunately). It may also be worthwhile for you to follow the issue over there in case any questions that you can answer come in.

Thanks,
Chris

[tsullivan (Tim Sullivan)]

The chart height dimension comes from a CSS style, so if there were problems loading a CSS resource, then this issue makes sense. Thanks for the update!