You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I guess this might be related to dns since it happened after ares_query(3).
Our software fetches URLs (using the http module and the underlying dns module) submitted by users. We are not storing URL logs for privacy reasons, but I think the issue is not related to a particular URL, because the process restarted and retried with no further errors.
It seems to be random, and I wasn't able to reproduce the issue in local environment yet.
It’s hard to tell whether this has to do with ares_query() itself, because for these kinds of errors typically are the result of memory corruption that happened at an earlier point in time.
Do you think you would be able to provide core dumps? Do you use any native addons? Are you using the official binary from https://nodejs.org/, or a distribution-provided one?
Do you think you would be able to provide core dumps?
It occurred on a production server with core dump disabled. I'm still trying to reproduce in a local environment but with no luck. Actually it happened after serving 20 million URLs, seems fully random.
Do you use any native addons?
No, the software only uses built-in modules (no dependencies), no pure javascript or native modules form NPM.
Are you using the official binary from https://nodejs.org/, or a distribution-provided one?
We are using official binary distributions provided by NodeSource in production.
I'll switch my local environment to a NodeSource version and see if I can dump a core.
I guess this might be related to
dns
since it happened after ares_query(3).Our software fetches URLs (using the
http
module and the underlyingdns
module) submitted by users. We are not storing URL logs for privacy reasons, but I think the issue is not related to a particular URL, because the process restarted and retried with no further errors.It seems to be random, and I wasn't able to reproduce the issue in local environment yet.
The text was updated successfully, but these errors were encountered: