"Can't create listen socket: Address already in use" after SIGINT

[Aaron]

I was running an app using morbo and had to kill it as it had become unresponsive.  Once I tried to restart, I got an error back "Can't create listen socket: Address already in use at /sastore/bossert/lib/perl5/site_perl/5.16.1/Mojo/IOLoop.pm line 147."

When I run netstat, I don't see anything that jumps out at me as still bound...but not an expert with that...Does anyone know how to handle this?  I also tried listening on a different port...but that gave the same error.

[Stefan Adams]

This may not help you, but I've had this on occasion as well.  For me, every time I came to the realization that the morbo executable was still running despite not being listed by netstat.  `pkill -9 -f morbo' took care of it for me.  Then no more listening complaints.

HTH!

On Wed, Mar 13, 2013 at 3:59 PM, Aaron <mabo...@gmail.com> wrote:

I was running an app using morbo and had to kill it as it had become unresponsive.  Once I tried to restart, I got an error back "Can't create listen socket: Address already in use at /sastore/bossert/lib/perl5/site_perl/5.16.1/Mojo/IOLoop.pm line 147."

When I run netstat, I don't see anything that jumps out at me as still bound...but not an expert with that...Does anyone know how to handle this?  I also tried listening on a different port...but that gave the same error.

--
You received this message because you are subscribed to the Google Groups "Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojolicious...@googlegroups.com.
To post to this group, send email to mojol...@googlegroups.com.
Visit this group at http://groups.google.com/group/mojolicious?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Stefan Adams]

On Wed, Mar 13, 2013 at 4:05 PM, Stefan Adams <ste...@cogentinnovators.com> wrote:

This may not help you, but I've had this on occasion as well.  For me, every time I came to the realization that the morbo executable was still running despite not being listed by netstat.  `pkill -9 -f morbo' took care of it for me.  Then no more listening complaints.

Careful with the 'morbo' search term tho in case you have other morbo daemons running that you care about...  Try a more specific search phrase instead.  Or be safe and just grep the process table and see which PIDs exist.  `pgrep -f morbo'...

[M. Aaron Bossert]

Thanks to all...will try that shortly, had to step away from my desk for a bit...

Aaron