Hi, I have a long-running node script doing sustained reads and writes against multiple HTTP APIs. Most of the work is being done with mikeal/request and caolan/async. After an hour or two of grinding against all the same code paths, my node process unexpectedly exits without any error messages, stack traces, etc and an exit status of 0. I've more or less ruled out dropped callbacks because the script exits at unpredictable points in the code and on paths that have already ran hundreds of times with similar inputs without incident.
Other things I’ve looked at that haven’t appeared problematic: Ephemeral ports, /var/log/messages and resource usage. Any suggestions in terms of figuring out what's happening? None of my normal tools (like console.log, the debugger, core dumps) seem directly applicable. This isn't a lot to go on given that I don't have a succinct repro case OR an error message. —Josh -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/b24070dc-1474-408d-8c3f-a73d3b682c58%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
