Replies: 1 comment 4 replies
-
Could you please advise? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I’m encountering an issue with the MeshCentral server logs where the following warning appears repeatedly:
(node:1529) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Socket]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
(Use
node --trace-warnings ...
to show where the warning was created)(node:1529) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Socket]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
(node:1529) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Socket]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
(node:1529) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Socket]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
I’m concerned it may point to a potential issue with memory management or improper event listener handling. Additionally, I’m worried that this could indicate a deeper problem in the event-driven architecture that might expose vulnerabilities, such as memory leaks or unhandled errors that could be exploited.
Could you please help me understand the cause of this warning and recommend steps to resolve it?
"meshVersion": "v1.1.33",
"nodeVersion": "v20.18.0",
"runMode": "WAN mode",
"productionMode": true,
"database": "NeDB",
"platform": "linux",
"arch": "x64
Thank you
Beta Was this translation helpful? Give feedback.
All reactions