Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to catch a global error with NodeJS

I am getting an unhandled error but not sure where it's coming from. My app has several http.request(options, callback).end() in different methods, with the callback's trapping "uncaughtException" and "error". I'd like to know which of my methods initiated this issue. Below is the error I get. It is random. Any ideas how to track this down? I was hoping for some global way of trapping unhandled errors.

events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: read ECONNRESET
    at exports._errnoException (util.js:746:11)
    at TCP.onread (net.js:559:26)
like image 903
user603749 Avatar asked Dec 09 '15 18:12

user603749


2 Answers

ECONNRESET means that the other side of the TCP connection is aborted. You could look at the server logs, but since it was random times this makes me think that the server becomes overloaded and kills a few connections.

If you're starting a process at any point in the process try the below:

process.on('uncaughtException', function (err) {
  console.error(err.stack);
  console.log("Node NOT Exiting...");
});
like image 76
Ross The Boss Avatar answered Sep 21 '22 04:09

Ross The Boss


attach a

request.on('error', function(err) {
    // Handle error
});

to your requests.

You can also catch uncaught errors for the process:

process.on('uncaughtException', function(err) {
  console.log('Caught exception: ' + err);
});

This error as it reads states the connection was reset, so its definitely one of the requests.

like image 37
AlexD Avatar answered Sep 20 '22 04:09

AlexD