Errno::EADDRINUSE #174

jonleighton opened this Issue Oct 8, 2012 · 1 comment


None yet
2 participants

jonleighton commented Oct 8, 2012

Saw this on our CI, presumably due to the change to a fixed port number. Possibly a bug with Poltergeist not handling failure properly in order to free up the port for a restart.

acme commented Oct 11, 2012

We're running tests in parallel and were hit by this bug.

@jonleighton jonleighton added a commit that referenced this issue Oct 15, 2012

@jonleighton jonleighton Use any available port
This reverts the default port setting to how it was before the 1.0
release. However the `:port` configuration option is still available for
those who need to set it to something static.

The reason for changing this back is that I have seend EADDRINUSE errors
crop up and in general had second thoughts on whether it was a good idea
to use a static port number as the default. I think it's much better and
less error prone to use any available port by default but to allow the
port number to be configured in the small number of cases where that's

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