# MaxListenersExceededWarning in Kibana

**URL:** <https://discuss.elastic.co/t/maxlistenersexceededwarning-in-kibana/167121>\
**Category:** Kibana\
**Created:** [February 5, 2019, 12:36pm UTC](https://discuss.elastic.co/t/maxlistenersexceededwarning-in-kibana/167121 "2019-02-05T12:36:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\
**Post date:** [February 5, 2019, 12:36pm UTC](https://discuss.elastic.co/t/maxlistenersexceededwarning-in-kibana/167121/1 "2019-02-05T12:36:16Z")

</div>

Hello,

While working with Kibana(modifying visualizations, logstash pipelines,...) I got a lot of timeouts today so I looked into the error log of Kibana to see if I could find an error message. This is what I found:  
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 message listeners added. Use emitter.setMaxListeners() to increase limit  
at \_addListener (events.js:280:19)  
at ChildProcess.addListener (events.js:297:10)  
at resolve (/logserver/applications/kibana-6.5.4-linux-x86\_64/node\_modules/x-pack/plugins/canvas/server/lib/route\_expression/thread/index.js:57:12)  
at new Promise ()  
at exports.thread (/logserver/applications/kibana-6.5.4-linux-x86\_64/node\_modules/x-pack/plugins/canvas/server/lib/route\_expression/thread/index.js:54:30)  
at Namespace.io.on (/logserver/applications/kibana-6.5.4-linux-x86\_64/node\_modules/x-pack/plugins/canvas/server/routes/socket.js:51:7)  
at   
at process.\_tickDomainCallback (internal/process/next\_tick.js:229:7)

I use Kibana 6.5.4. After restarting Kibana the error is gone.

Can anyone tell me what this means? Do I have to set a config setting to increase the listeners?

---

<div class="post-metadata">

**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\
**Post date:** [February 5, 2019, 8:24pm UTC](https://discuss.elastic.co/t/maxlistenersexceededwarning-in-kibana/167121/2 "2019-02-05T20:24:32Z")

</div>

`EventEmitter` is a class that gets extended to allow subscribing to events. Sounds like subscriptions are not getting cleaned up when something is destroyed. Any chance you can create a reliable way to recreate the issue? Could you please file a bug at [https://github.com/elastic/kibana/issues/new?template=Bug\_report.md](https://github.com/elastic/kibana/issues/new?template=Bug_report.md)

---

<div class="post-metadata">

**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\
**Post date:** [February 6, 2019, 6:08am UTC](https://discuss.elastic.co/t/maxlistenersexceededwarning-in-kibana/167121/3 "2019-02-06T06:08:38Z")

</div>

Done: [https://github.com/elastic/kibana/issues/30181](https://github.com/elastic/kibana/issues/30181)

---

<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:** [March 6, 2019, 6:08am UTC](https://discuss.elastic.co/t/maxlistenersexceededwarning-in-kibana/167121/4 "2019-03-06T06:08:39Z")

</div>

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