Upstart reports that bouncy has exit #26

serby opened this Issue Mar 9, 2012 · 2 comments


None yet

2 participants

serby commented Mar 9, 2012

On ubuntu/Lucid, upstart reports that bouncy has exited with a status 1, at random intervals

If you run bouncy from the console it remains running without any problem.

This is the routes file
"test": 3023,
"test2": 3023

This could well be a problem with upstart, but this is the first node app I've experienced this with. Have you seen anything like this before?

serby commented Mar 10, 2012

It isn't upstart, bouncy crashes from the console too once enough traffic goes through the proxy.

This is the trace:

throw e; // process.nextTick error, or 'error' event on first tick
Error: write EPIPE
at errnoException (net.js:642:11)
at Object.afterWrite as oncomplete

As of yet I'm unable to reproduce the the error on demand.


This issue is happening for us with but it appears to be bad behavior on the part of older browsers abruptly ending the connection. How can this condition be handled more gracefully?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment