Turns out my problem was caused by stray RabbitMQ connections getting
closed. Installing the longjohn module helped debug this with better stack
traces.
On Wednesday, 5 June 2013 13:39:43 UTC-4, Matt Zukowski wrote:
>
> Pretty much in the same boat here. Occasionally seeing the following
> error, crashing the whole app. It's mostly unpredictable, but I can
> sometimes reproduce it by pounding the server with ab for a while. It never
> happens while the server is processing requests, only about 1 - 2 minutes
> after, when no requests are coming though:
>
> events.js:72
> throw er; // Unhandled 'error' event
> ^
> Error: read ECONNRESET
> at errnoException (net.js:884:11)
> at TCP.onread (net.js:539:19)
>
> On Monday, 8 April 2013 13:57:39 UTC-4, Jimb Esser wrote:
>>
>> As an extra data point, I've been seeing these too, since updating to
>> node 0.10, but have no idea where they're coming from. I think we wrap all
>> of our HTTP requests such that errors get caught, but this is bubbling up
>> to process.on('uncaughtException'). We also have warnings that fire if we
>> ever get a request and do not respond to it, and those warnings are not
>> firing when this occurs, so, other than the uncaughtException, we're not
>> seeing anything that would indicate anything going wrong. Admittedly, this
>> is inside of a rather large and complex app, so it's quite possible we're
>> missing something, but it's definitely not coming from our usual suspects
>> for HTTP requests (Amazon APIs).
>>
>> On Friday, April 5, 2013 12:52:03 PM UTC-7, Isaac Schlueter wrote:
>>>
>>> Without seeing anything except an error message, I can't really answer
>>> that except to say that some net.Socket object is trying to read(),
>>> and getting an ECONNRESET error. Someone sent someone else a RST
>>> packet, and instead of ignoring it, Node is emitting an error because
>>> of it, like it ought to have in the first place.
>>>
>>> Maybe share more of your code, put error handlers on your client and
>>> server connections, and use domain objects to get more context in the
>>> error. That'd all help track down where this is coming from.
>>>
>>>
>>> On Fri, Apr 5, 2013 at 9:19 AM, Jochen Delabie <[email protected]>
>>> wrote:
>>> > Since we updated from Node 0.8 to Node 0.10 we're seeing these errors:
>>> >
>>> > { [Error: read ECONNRESET] code: 'ECONNRESET', errno: 'ECONNRESET',
>>> > syscall: 'read' }
>>> > Error: read ECONNRESET
>>> > at errnoException (net.js:878:11)
>>> > at TCP.onread (net.js:539:19)
>>> >
>>> >
>>> > I know this error was previously ignored before 0.10, but I'd like to
>>> know
>>> > what's causing this and how I can fix it/debug it?
>>> > Is it a problem on our end (server) closing connections too soon?
>>> >
>>> > Thanks!
>>> >
>>> > --
>>> > --
>>> > Job Board: http://jobs.nodejs.org/
>>> > Posting guidelines:
>>> > 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 post to this group, send email to [email protected]
>>> > To unsubscribe from this group, send email to
>>> > [email protected]
>>> > For more options, visit this group at
>>> > http://groups.google.com/group/nodejs?hl=en?hl=en
>>> >
>>> > ---
>>> > 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].
>>> > For more options, visit https://groups.google.com/groups/opt_out.
>>> >
>>> >
>>>
>>
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
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].
For more options, visit https://groups.google.com/groups/opt_out.
