# Kibana Discovery Errors followed by unknown node.js issues

**URL:** <https://discuss.elastic.co/t/kibana-discovery-errors-followed-by-unknown-node-js-issues/208070>\
**Category:** Kibana\
**Created:** [November 15, 2019, 12:11pm UTC](https://discuss.elastic.co/t/kibana-discovery-errors-followed-by-unknown-node-js-issues/208070 "2019-11-15T12:11:00Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![tomervain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomervain/32/57776_2.png) [@tomervain](https://discuss.elastic.co/u/tomervain)\
**Post date:** [November 15, 2019, 12:11pm UTC](https://discuss.elastic.co/t/kibana-discovery-errors-followed-by-unknown-node-js-issues/208070/1 "2019-11-15T12:11:00Z")

</div>

Hello,

I'm having some issues with Kibana recently and could really use the community's help.

I'm running Elasticsearch + Kibana 6.5.4 (both) on a Windows Server with one master node without any issues. Elasticsearch is running as a Windows Service and Kibana is running by the Kibana.bat script.

About 2 weeks ago i started to notice sudden Timeout Errors (after 30000ms) after a 12-hour (approximately) time period of proper behavior. Checking Elasticsearch's service, i didn't find any issues and Kibana was running since i could see everything from the Web App.

After checking the running Kibana.bat (via Terminal/CMD) i noticed the following non-stop errors:

```
Error: Cannot find module '/proc/self/environ'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at Function.Module._preloadModules (module.js:754:12)
    at preloadModules (bootstrap_node.js:488:38)
    at startup (bootstrap_node.js:201:9)
    at bootstrap_node.js:625:3
module.js:550
    throw err;
    ^

```

I Restarted Kibana (closed and reinitialized Kibana.bat) and everything went back to normal until it came back after the stated time period (happens every time).

I've tried to perform some basic troubleshooting:

- Restarting Elasticsearch Service
- Restarting the Server
- Downgrade Browser's (Google Chrome) version
- Replacing Kibana 6.5.4's copy with a fresh download

Nothing worked. I also tried to replace the node.js executable without success (errors seems to be generated by node's process).

I've also routed the logging to a file in order to find more information regarding thid issue and encounter this error, which i'm not sure it's related:

```
    {
  "type": "error",
  "@timestamp": "2019-11-14T21:10:50Z",
  "tags": [
    "warning",
    "process"
  ],
  "pid": 4668,
  "level": "error",
  "error": {
    "message": "Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)",
    "name": "UnhandledPromiseRejectionWarning",
    "stack": "Error: Specified object should be an Object or Array
       at validateObject (KIBANA_PATH/kibana-6.5.4-windows-x86_64/kibana-6.5.4-windows-x86_64/node_modules/x-pack/server/lib/key_case_converter.js:39:11)
       at convertKeysToSnakeCaseDeep (KIBANA_PATH/kibana-6.5.4-windows-x86_64/kibana-6.5.4-windows-x86_64/node_modules/x-pack/server/lib/key_case_converter.js:44:3)
       at handler (KIBANA_PATH/kibana-6.5.4-windows-x86_64/kibana-6.5.4-windows-x86_64/node_modules/x-pack/plugins/xpack_main/server/routes/api/v1/xpack_info.js:22:13)
       at Object.internals.handler (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hapi\\lib\\handler.js:96:36)
       at request._protect.run (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hapi\\lib\\handler.js:30:23)
       at module.exports.internals.Protect.internals.Protect.run (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hapi\\lib\\protect.js:64:5)
       at exports.execute (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hapi\\lib\\handler.js:24:22)
       at each (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hapi\\lib\\request.js:384:16)
       at iterate (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\items\\lib\\index.js:36:13)
       at done (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\items\\lib\\index.js:28:25)
       at Hoek.once (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hapi\\lib\\protect.js:52:16)
       at wrapped (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hoek\\lib\\index.js:879:20)
       at done (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\items\\lib\\index.js:31:25)
       at Function.wrapped [as _next] (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hoek\\lib\\index.js:879:20)
       at Function.internals.continue (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hapi\\lib\\reply.js:108:10)
       at method (KIBANA_PATH/kibana-6.5.4-windows-x86_64/kibana-6.5.4-windows-x86_64/node_modules/x-pack/plugins/dashboard_mode/server/dashboard_mode_request_interceptor.js:44:7)
       at Items.serial (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hapi\\lib\\request.js:403:22)
       at iterate (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\items\\lib\\index.js:36:13)
       at done (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\items\\lib\\index.js:28:25)
       at Function.wrapped [as _next] (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hoek\\lib\\index.js:879:20)
       at Function.internals.continue (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hapi\\lib\\reply.js:108:10)
       at spacesOnRequestHandler (KIBANA_PATH/kibana-6.5.4-windows-x86_64/kibana-6.5.4-windows-x86_64/node_modules/x-pack/plugins/spaces/server/lib/space_request_interceptors.js:82:16)
       at Items.serial (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hapi\\lib\\request.js:403:22)
       at iterate (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\items\\lib\\index.js:36:13)
       at done (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\items\\lib\\index.js:28:25)
       at Function.wrapped (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hoek\\lib\\index.js:879:20)
       at Function.internals.continue (KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\node_modules\\hapi\\lib\\reply.js:108:10)
       at KIBANA_PATH\\kibana-6.5.4-windows-x86_64\\kibana-6.5.4-windows-x86_64\\src\\server\\http\\xsrf.js:33:26"
  },
  "message": "Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)"
}

```

I didn't find neither similar nor related issues online, hoping someone can direct me to additional troubleshooting or a possible solution.

Thanks,

Tomer Vainstein.

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [November 18, 2019, 10:07pm UTC](https://discuss.elastic.co/t/kibana-discovery-errors-followed-by-unknown-node-js-issues/208070/2 "2019-11-18T22:07:14Z")

</div>

Can you any other errors in the Kibana or ES log?

---

<div class="post-metadata">

**Author:** ![tomervain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomervain/32/57776_2.png) [@tomervain](https://discuss.elastic.co/u/tomervain)\
**Post date:** [November 19, 2019, 11:19am UTC](https://discuss.elastic.co/t/kibana-discovery-errors-followed-by-unknown-node-js-issues/208070/3 "2019-11-19T11:19:06Z")

</div>

No, they are all the same as i posted.

When i try to access monitoring data from the API, i can see Node information. Any response to Indices status requests is Internal Server Error (500)

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [November 19, 2019, 12:46pm UTC](https://discuss.elastic.co/t/kibana-discovery-errors-followed-by-unknown-node-js-issues/208070/4 "2019-11-19T12:46:23Z")

</div>

What do you mean by the API? Requests to ES?

---

<div class="post-metadata">

**Author:** ![camathieu](https://avatars.discourse-cdn.com/v4/letter/c/91b2a8/32.png) [@camathieu](https://discuss.elastic.co/u/camathieu)\
**Post date:** [November 19, 2019, 5:12pm UTC](https://discuss.elastic.co/t/kibana-discovery-errors-followed-by-unknown-node-js-issues/208070/5 "2019-11-19T17:12:32Z")

</div>

Hello,

We are experiencing the same issue since a few days.

> Nov 18 15:58:30 elasticsearch5-logs-master05-am5 kibana[88005]: {"type":"error","@timestamp":"2019-11-18T15:58:30Z","tags":["warning","process"],"pid":88005,"level":"error","error":{"message":"Error: Specified object should be an Object or Array  
> at validateObject (/usr/local/kibana-6.3.1/node\_modules/x-pack/server/lib/key\_case\_converter.js:39:11)  
> at convertKeysToSnakeCaseDeep (/usr/local/kibana-6.3.1/node\_modules/x-pack/server/lib/key\_case\_converter.js:44:3)  
> at handler (/usr/local/kibana-6.3.1/node\_modules/x-pack/plugins/xpack\_main/server/routes/api/v1/xpack\_info.js:22:13)  
> at Object.internals.handler (/usr/local/kibana-6.3.1/node\_modules/hapi/lib/handler.js:96:36)  
> at request.\_protect.run (/usr/local/kibana-6.3.1/node\_modules/hapi/lib/handler.js:30:23)  
> at module.exports.internals.Protect.internals.Protect.run (/usr/local/kibana-6.3.1/node\_modules/hapi/lib/protect.js:64:5)  
> at exports.execute (/usr/local/kibana-6.3.1/node\_modules/hapi/lib/handler.js:24:22)  
> at each (/usr/local/kibana-6.3.1/node\_modules/hapi/lib/request.js:384:16)  
> at iterate (/usr/local/kibana-6.3.1/node\_modules/items/lib/index.js:36:13)  
> at done (/usr/local/kibana-6.3.1/node\_modules/items/lib/index.js:28:25)  
> at Hoek.once (/usr/local/kibana-6.3.1/node\_modules/hapi/lib/protect.js:52:16)  
> at wrapped (/usr/local/kibana-6.3.1/node\_modules/hoek/lib/index.js:879:20)  
> at done (/usr/local/kibana-6.3.1/node\_modules/items/lib/index.js:31:25)  
> at Function.wrapped [as \_next] (/usr/local/kibana-6.3.1/node\_modules/hoek/lib/index.js:879:20)  
> at Function.internals.continue (/usr/local/kibana-6.3.1/node\_modules/hapi/lib/reply.js:108:10)  
> at method (/usr/local/kibana-6.3.1/node\_modules/x-pack/plugins/dashboard\_mode/server/dashboard\_mode\_request\_interceptor.js:44:7)  
> at Items.serial (/usr/local/kibana-6.3.1/node\_modules/hapi/lib/request.js:403:22)  
> at iterate (/usr/local/kibana-6.3.1/node\_modules/items/lib/index.js:36:13)  
> at done (/usr/local/kibana-6.3.1/node\_modules/items/lib/index.js:28:25)  
> at Function.wrapped [as \_next] (/usr/local/kibana-...

Kibana becomes unusable because of request timeouts on the GET /api/xpack/v1/info http route on Kibana.  
A restart of the process fixes the issue for a moment then it reappears.

When the call is a success here is the output :

> {  
> "features": {  
> "graph": {  
> "enable\_app\_link": false,  
> "message": "Graph is unavailable for the current basic license. Please upgrade your license.",  
> "show\_app\_link": false  
> },  
> "grokdebugger": {  
> "enable\_api\_route": true,  
> "enable\_link": true  
> },  
> "index\_management": {  
> "enable\_links": true,  
> "is\_available": true,  
> "show\_links": true  
> },  
> "logstash": {  
> "enable\_links": false,  
> "is\_available": false,  
> "is\_read\_only": false,  
> "message": "Your basic license does not support Logstash pipeline management features. Please upgrade your license."  
> },  
> "ml": {  
> "enable\_links": false,  
> "is\_available": false,  
> "message": "Your basic license does not support Machine Learning. Please upgrade your license.",  
> "show\_links": false  
> },  
> "reporting": {  
> "csv": {  
> "enable\_links": true,  
> "show\_links": true  
> },  
> "management": {  
> "enable\_links": true,  
> "job\_types": [  
> "csv"  
> ],  
> "show\_links": true  
> },  
> "printable\_pdf": {  
> "enable\_links": false,  
> "message": "Your basic license does not support PDF Reporting. Please upgrade your license.",  
> "show\_links": false  
> }  
> },  
> "searchprofiler": {  
> "enable\_app\_link": true,  
> "show\_app\_link": true  
> },  
> "security": {  
> "allow\_login": false,  
> "allow\_role\_document\_level\_security": false,  
> "allow\_role\_field\_level\_security": false,  
> "links\_message": "Your Basic license does not support Security. Please upgrade your license.",  
> "show\_links": false,  
> "show\_login": false  
> },  
> "tilemap": {  
> "license": {  
> "active": true,  
> "uid": "XXXX-XXXXXXXXXXXXX-XXXXXX",  
> "valid": true  
> }  
> },  
> "watcher": {  
> "is\_available": false,  
> "message": "Your basic license does not support Watcher. Please upgrade your license.",  
> "show\_links": false  
> }  
> },  
> "license": {  
> "is\_active": true,  
> "type": "basic"  
> }  
> }

---

<div class="post-metadata">

**Author:** ![tomervain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomervain/32/57776_2.png) [@tomervain](https://discuss.elastic.co/u/tomervain)\
**Post date:** [November 20, 2019, 8:09am UTC](https://discuss.elastic.co/t/kibana-discovery-errors-followed-by-unknown-node-js-issues/208070/6 "2019-11-20T08:09:41Z")

</div>

Thats correct, i meant using the REST API for monitoring requests.

From the comment above i see that others has similar issues.

---

<div class="post-metadata">

**Author:** ![camathieu](https://avatars.discourse-cdn.com/v4/letter/c/91b2a8/32.png) [@camathieu](https://discuss.elastic.co/u/camathieu)\
**Post date:** [November 20, 2019, 10:03am UTC](https://discuss.elastic.co/t/kibana-discovery-errors-followed-by-unknown-node-js-issues/208070/7 "2019-11-20T10:03:12Z")

</div>

Also when the problem appears I noticed that those two paths behave differently :

The first one returns a 404

> curl [http://127.0.0.1:5601/api/x-pack/v1/info](http://127.0.0.1:5601/api/x-pack/v1/info)  
> {"statusCode":404,"error":"Not Found","message":"Not Found"}

The second one timeout :

> curl [http://127.0.0.1:5601/api/xpack/v1/info](http://127.0.0.1:5601/api/xpack/v1/info)  
> ^C

---

<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:** [December 18, 2019, 10:03am UTC](https://discuss.elastic.co/t/kibana-discovery-errors-followed-by-unknown-node-js-issues/208070/8 "2019-12-18T10:03:26Z")

</div>

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