Cabana gives error when setting auto refresh

Elastic Stack Kibana
1

Hello,

No matter what value I set for the auto refresh in Kibana I get the following errors:

Courier Fetch: undefined is not an object (evaluating 'resp.timed_out')
Version: 4.4.1
Build: 9693
Error: undefined is not an object (evaluating 'resp.timed_out')
https://core.z0z0.tk:5601/bundles/kibana.bundle.js?v=9693:90010:18
https://core.z0z0.tk:5601/bundles/commons.bundle.js?v=9693:63867:28
https://core.z0z0.tk:5601/bundles/commons.bundle.js?v=9693:63836:31
map@[native code]
map@https://core.z0z0.tk:5601/bundles/commons.bundle.js?v=9693:63835:34
callResponseHandlers@https://core.z0z0.tk:5601/bundles/kibana.bundle.js?v=9693:90003:26
https://core.z0z0.tk:5601/bundles/kibana.bundle.js?v=9693:89510:37
processQueue@https://core.z0z0.tk:5601/bundles/commons.bundle.js?v=9693:41836:31
https://core.z0z0.tk:5601/bundles/commons.bundle.js?v=9693:41852:40
$eval@https://core.z0z0.tk:5601/bundles/commons.bundle.js?v=9693:43080:29
$digest@https://core.z0z0.tk:5601/bundles/commons.bundle.js?v=9693:42891:37
$apply@https://core.z0z0.tk:5601/bundles/commons.bundle.js?v=9693:43188:32
done@https://core.z0z0.tk:5601/bundles/commons.bundle.js?v=9693:37637:54
completeRequest@https://core.z0z0.tk:5601/bundles/commons.bundle.js?v=9693:37835:16
requestLoaded@https://core.z0z0.tk:5601/bundles/commons.bundle.js?v=9693:37776:25

Please help me figure this out.

Regards,
Peter

2

Hi Peter,

I was able to reproduce this issue only one time. How often are you seeing this happen? Can you provide steps to reproduce this bug.

Thanks.

3

I'm pretty sure this will happen whenever Kibana is expecting a json response from an xhr request but it gets back a different type of response (usually html).

4

It happens to me almost every time I an setting up autorefresh. What I last did I set the dashboard show 30days of data then I selected refresh time 5 minutes. After about 10 seconds of thinking I end up with the errors above.

5

Are you using the shield UI plugin? There's currently a P1 bug related to that, which looks to be the same issue that you're having: https://github.com/elastic/kibana/issues/6254

Basically, it happens every time the session expires.

6

Yes, I am using shield. And that's right usually that happens when the sessions expires. However it also happens if the data takes too long to load, but it never happened before I have installed and configured shield on the system.