# NS\_ERROR\_FAILURE observed in Kibana dashboard in Firefox

**URL:** <https://discuss.elastic.co/t/ns-error-failure-observed-in-kibana-dashboard-in-firefox/111941>\
**Category:** Kibana\
**Created:** [December 15, 2017, 9:53am UTC](https://discuss.elastic.co/t/ns-error-failure-observed-in-kibana-dashboard-in-firefox/111941 "2017-12-15T09:53:01Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![aaradhanas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aaradhanas/32/25850_2.png) [@aaradhanas](https://discuss.elastic.co/u/aaradhanas)\
**Post date:** [December 15, 2017, 9:53am UTC](https://discuss.elastic.co/t/ns-error-failure-observed-in-kibana-dashboard-in-firefox/111941/1 "2017-12-15T09:53:01Z")

</div>

## Issue

When Kibana dashboard is viewed in Firefox browser and a chart is viewed in an expanded mode and then back to the collapsed mode,the remaining charts are not rendered.

## Versions used

Firefox: 52.4.1 (32-bit)  
Kibana: 5.6.3  
Elastic: 5.6.3

## Usecase

When a user tries to expand one of the charts in the dashboard and then collapse it, the other charts are not rendered.  
This issue occurs in Firefox browser.

## Observations

We observed that the **common.bundle.js** throws **NS\_ERROR\_FAILURE** when the chart is expanded.

Would you please help us resolve this issue?

---

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [December 15, 2017, 10:04am UTC](https://discuss.elastic.co/t/ns-error-failure-observed-in-kibana-dashboard-in-firefox/111941/2 "2017-12-15T10:04:13Z")

</div>

Hi Aaradhana,

a `NS_ERROR_FAILURE` usually would indicate an network error. Could you open the Dev Tools in Firefox, go to the Network tab, then reproduce the issue, and check if a specific call failed there and what additional information about that failing call might be provided?

Cheers,  
Tim

---

<div class="post-metadata">

**Author:** ![aaradhanas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aaradhanas/32/25850_2.png) [@aaradhanas](https://discuss.elastic.co/u/aaradhanas)\
**Post date:** [December 15, 2017, 10:16am UTC](https://discuss.elastic.co/t/ns-error-failure-observed-in-kibana-dashboard-in-firefox/111941/3 "2017-12-15T10:16:33Z")

</div>

Hi Tim,

Thanks for your reply.

I analyzed the Network tab in the Dev Tools, but didn't find any failed call. I could see the following error trace in the Console while expanding the panel:

Exception { message: "", result: 2147500037, name: "NS\_ERROR\_FAILURE", filename: "commons.bundle.js", lineNumber: 115, columnNumber: 0, data: null, stack: "VislibAxisLabelsProvider/AxisLabels…" } 1 commons.bundle.js:38:11454  
consoleLog/\< commons.bundle.js:38:11454  
$ExceptionHandlerProvider/this.$get\</\< commons.bundle.js:37:17828  
processQueue commons.bundle.js:38:23742  
scheduleProcessQueue/\< commons.bundle.js:38:23888  
$RootScopeProvider/this.$get\</Scope.prototype.$eval commons.bundle.js:39:4607  
$RootScopeProvider/this.$get\</Scope.prototype.$digest commons.bundle.js:39:2343  
$RootScopeProvider/this.$get\</Scope.prototype.$apply commons.bundle.js:39:5026  
timeout/timeoutId\< commons.bundle.js:39:17601  
completeOutstandingRequest commons.bundle.js:36:4607  
Browser/self.defer/timeoutId\< commons.bundle.js:36:7706

Hope this information is useful.

Thanks.

---

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [December 15, 2017, 10:28am UTC](https://discuss.elastic.co/t/ns-error-failure-observed-in-kibana-dashboard-in-firefox/111941/4 "2017-12-15T10:28:16Z")

</div>

The output seems, like there is still parts of the stacktrace cut off. Can you expand the object in the dev tools, so that whatever the stack value states there (beginning with "VislibAxisLabelsProvider/...") will be fully visible?

Also, does this issue occur in any other browser too, e.g. Chrome on the same system, or a more up to date Firefox version? Since network failures can also be caused by several ad block or script block plugins, have you tried turning of the currently active plugins in that browser?

Cheers,  
Tim

---

<div class="post-metadata">

**Author:** ![aaradhanas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aaradhanas/32/25850_2.png) [@aaradhanas](https://discuss.elastic.co/u/aaradhanas)\
**Post date:** [December 20, 2017, 10:58am UTC](https://discuss.elastic.co/t/ns-error-failure-observed-in-kibana-dashboard-in-firefox/111941/5 "2017-12-20T10:58:27Z")

</div>

Hi Tim,

Sorry for getting back late.

I did check the Firefox developer console for a more detailed log. But this is the available stacktrace. I have attached the screenshot of the console. Hope this helps.

 ![KibanaIssue](https://us1.discourse-cdn.com/elastic/original/3X/3/f/3fbe50435829b0f0e9322feca304f39c92cec3c3.png)

For your question regarding the issue in other browsers, it is not observed in Chrome. It is seen in Firefox 52.4.1.

I disabled an ad block extension which was in active state. But still, I am able to see this issue.

Thanks,  
Aaradhana

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 17, 2018, 10:58am UTC](https://discuss.elastic.co/t/ns-error-failure-observed-in-kibana-dashboard-in-firefox/111941/6 "2018-01-17T10:58:28Z")

</div>

Closed on January 17, 2018, 10:58am UTC

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