"rerun foreman start", the first re-run fails with "Errno::EADDRINUSE" (Ubuntu 12.10) about rerun HOT 8 OPEN

This is probably happening due to ddollar/foreman#779 in foreman, that's address by this PR: ddollar/foreman#780 – that PR has been released in an foreman fork called overman

from rerun.

I'm experiencing the same issue - any ideas on how to fix that ? I have tried multiple options for rerun (such as --signal KILL) but could not find any solution for it.

from rerun.

Sorry, I haven't worked on this issue yet... What version of foreman are
you using?

I would think --signal KILL would do it -- or even the normal TERM --
but a quick google shows other people are having trouble with foreman not
restarting its subprocesses gracefully...

On Wed, Jan 1, 2014 at 3:52 AM, Alan Rubin [email protected] wrote:

I'm experiencing the same issue - any ideas on how to fix that ? I have
tried multiple options for rerun (such as --signal KILL) but could not find
any solution for it.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/41#issuecomment-31421881
.

Alex Chaffee - [email protected]
http://alexchaffee.com
http://codelikethis.com
http://twitter.com/alexch

from rerun.

Same issue here. My foreman version is 0.63.0

Hope it helps!, thanks

from rerun.

Here's the relevant code: https://github.com/alexch/rerun/blob/master/lib/rerun/runner.rb#L218-L241

It looks like foreman is responding to SIGINT by sending SIGKILL to all its children. But it takes longer than 2 seconds for the children to die (how morbid!) so we escalate to sending SIGKILL and restart forecefully. Yeah, maybe increasing the SIGINT timeout would do it.

I'll bump up both timeouts to 5 seconds and push to master; you can then clone it locally and run rake install and see if that's enough.

A better solution would be to expand the --signal semantics to something like this:

--signal TERM:4,INT:2,KILL

which would do the current logic.

from rerun.

Stable Mac gems for rerun (0.10.0) and foreman (0.60.0) appear to still manifest this issue. Should those gems be more recent?

from rerun.

Seeing this on ubuntu 7 years later :(

from rerun.

ha, same problem on overmind :[

from rerun.