-
Notifications
You must be signed in to change notification settings - Fork 292
Assertion failed: unknown EAI_* error code in uv_getaddrinfo_translate_error #4223
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
Comments
What execution steps are you taking to cause this error and what application code causes this error? The I attempted to execute this in the Node shell repl versions 20.2.0 and 18.15.0 and I could not produce an error:
|
@prettydiff The issue is not due to this code snippet, this is just a part of node cluster implementation. There are multiple incoming requests on production, and the error's reason is not known yet. That's why I pasted the console trace output here, I want to know if there is any way I can debug this error, i.e., the root cause of it. |
If the issue is somehow related to clusters I would log the cluster messaging. Clusters coordinate through a messaging scheme. |
It seems there has been no activity on this issue for a while, and it is being closed in 30 days. If you believe this issue should remain open, please leave a comment. |
It seems there has been no activity on this issue for a while, and it is being closed. If you believe this issue should remain open, please leave a comment. |
Uh oh!
There was an error while loading. Please reload this page.
Details
I'm encountering an error with the following assertion message:
Assertion failed: (!"unknown EAI_* error code"), function uv_getaddrinfo_translate_error, file src/unix/getaddrinfo.c, line 90.
I've already taken the following steps:
When the worker dies due to this error, all other requests on that worker get aborted, I want to prevent this behavior.
If anyone has encountered a similar issue or has insights into diagnosing and resolving low-level errors like this one, I would greatly appreciate your input. Any suggestions, debugging techniques, or potential workarounds would be invaluable.
Node.js version
v18.15.0
Example code
Operating system
Ubuntu Linux
The text was updated successfully, but these errors were encountered: