-
Notifications
You must be signed in to change notification settings - Fork 922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EventEmitter memory leak detected #2373
Comments
Due to elasticsearch client. See Waiting for the fix from elastic |
Completely breaks the run time environment, is this something which can be reverted?
|
I dont think its related, looks like you experiment a timeout on connecting to elasticsearch. |
any update? |
Looks like still work in progress on elastic side. |
This warning doesnt break anything. If you have an error in the import it should come from another reason |
No, It makes dashboard irresponsive, unable to even log in. |
Hi @shahidakhter786 , if you have irresponsibe dashboard it must comes from another problem. |
there's no error in logs except (node:7) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 abort listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit. |
Same here... |
I am using 5.5.4 and the same warning is showing. |
As time goes, the opencti container consumes up to 24GB ram and it reduces to less than 6GB when I restart the project. |
I had the same error after the OS crashed. |
Memory leak is i think related to #2878 and not this eventEmitter warning from elastic client |
Looks like due to (accidental?) closure of the PR at Elastic repo, it is now being tracked here: |
Decide to patch the lib to increase the limit waiting for an official patch |
Hi,
It doesn't seems to alter in any way the platform, but as it seems related to this issue and that the issue is marked as fixed, should we perform some steps in order to prevent these errors? Regards. |
Still seeing this on 5.12.33 (node:7) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 abort listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit |
Still seeing in in 6.0.10 |
Reopening as our internal patch doesnt resolve the underlying problem. |
- This upgrade should resolve EventEmitter #2373
- This upgrade should resolve EventEmitter OpenCTI-Platform#2373
Looks good since elasticsearch upgrade in 6.2.2. |
Description
I didn't receive any update from days so i check the log and found this
(node:7) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 abort listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
Environment
Reproducible Steps
Steps to create the smallest reproducible scenario:
From log of docker appears this message on login.
The text was updated successfully, but these errors were encountered: