Debugging events.js unhanded 'error' events - Galaxy

help
1

I have my app in production using Galaxy at the moment. I have been getting errors randomly that have crashed the server. Sometimes it’s only 1-2 times a day, but yesterday for example, the server crashed 4+ times within 1 hour, which is not acceptable.

We’re still using Meteor 1.3 at the moment.

Problem is, I’m not sure how to debug it. This is the entire error log every time the server has went down:

2016-12-27 14:07:18-08:00events.js:72
2016-12-27 14:07:18-08:00 throw er; // Unhandled 'error' event
2016-12-27 14:07:18-08:00 ^
2016-12-27 14:07:18-08:00Error: read ECONNRESET
2016-12-27 14:07:18-08:00 at errnoException (net.js:905:11)
2016-12-27 14:07:18-08:00 at TCP.onread (net.js:559:19)

Any advice on how to approach this would be appreciated!

2

Does this by any chance happen when sending e-mail?

3

I don’t believe so, our only feature that sends email is inviting new users, which was not done at these times.

I have no idea what it’s related to honestly - that’s why I’m hoping for some assistance on how to debug this. Somedays it does not happen or only happens once, and other days multiple times per hour. Does not seem related to any other console.logs or errors in our application. And of course, the error itself is not very informative at all.

4

The reason I was asking was that I have seeing the exact same problem and was able to narrow it down to e-mail and the MAIL_URL configuration, depending on which mail server I use.

5

Thanks for the suggestion!

I can do some experimenting with MAIL_URL, but as mentioned I doubt that is the case here. We have not invited any new users to our software recently.

But it’s worth an attempt just to rule out!

Thanks again!