Rails Address already in use - bind 2 Errno EADDRINUSE

Question

I am trying to deploy Rails app with the Puma web server  When trying to start Puma server with a config file bundle exec puma -C config puma rb I get an error that the address is already in use   Does someone know how to fix this   bundle exec puma -C config puma rb  23699  Puma starting in cluster mode     23699    Version 2 11 3  ruby 2 0 0-p353   codename  Intrepid Squirrel  23699    Min threads  5  max threads  5  23699    Environment  development  23699    Process workers  2  23699    Preloading application Jdbc-MySQL is only for use with JRuby  23699    Listening on tcp   0 0 0 0 3000   rvm gems ruby-2 0 0-p353 gems puma-2 11 3 lib puma binder rb 210 in  initialize   Address already in use - bind 2   Errno  EADDRINUSE      from   rvm gems ruby-2 0 0-p353 gems puma-2 11 3 lib puma binder rb 210 in  new      from  Users lexi87  rvm gems ruby-2 0 0-p353 gems puma-2 11 3 lib puma binder rb 210 in  add tcp listener      from   rvm gems ruby-2 0 0-p353 gems puma-2 11 3 lib puma binder rb 96 in  block in parse      from   rvm gems ruby-2 0 0-p353 gems puma-2 11 3 lib puma binder rb 82 in  each      from   rvm gems ruby-2 0 0-p353 gems puma-2 11 3 lib puma binder rb 82 in  parse      from   rvm gems ruby-2 0 0-p353 gems puma-2 11 3 lib puma runner rb 119 in  load and bind      from   rvm gems ruby-2 0 0-p353 gems puma-2 11 3 lib puma cluster rb 302 in  run      from   rvm gems ruby-2 0 0-p353 gems puma-2 11 3 lib puma cli rb 216 in  run      from  rvm gems ruby-2 0 0-p353 gems puma-2 11 3 bin puma 10 in   lt top  required  gt       from   rvm gems ruby-2 0 0-p353 bin puma 23 in  load      from   rvm gems ruby-2 0 0-p353 bin puma 23 in   lt main gt       from   rvm gems ruby-2 0 0-p353 bin ruby executable hooks 15 in  eval      from   rvm gems ruby-2 0 0-p353 bin ruby executable hooks 15 in   lt main gt

User · Answer

If the above solutions don t work on ubuntu linux then you can try this  sudo fuser -k -n tcp port   Run it several times to kill processes on your port of choosing  port could be 3000 for example  You would have killed all the processes if you see no output after running the command

User · Answer

It might be old but in my case  it was because of docker  Hope it will help others

User · Answer

you can also try this trick  ps aux   grep puma  sample output  myname           77921   0 0  0 0  2433828   1972 s000  R    11 17AM   0 00 00 grep puma myname           67661   0 0  2 3  2680504 191204 s002  S    11 00AM   0 18 38 puma 3 11 2  tcp   localhost 3000   my proj   then  kill -9 67661

User · Answer

You can find and kill the running processes  ps aux   grep puma Then you can kill it with kill PID

User · Answer

You need to use kill -9 59780 with 59780 replaced with found PID number  use lsof -wni tcp 3000 to see which process used 3000 port and get the process PID    Or you can just modify your puma config change the tcp port tcp   127 0 0 1 3000 from 3000 to 9292 or other port that not been used   Or you can start your rails app by using   bundle exec puma -C config puma rb -b tcp   127 0 0 1 3001

User · Answer

Found the script below in this github issue  Works great for me      usr bin env ruby port   ARGV first    3000 system  sudo echo kill-server-on   port     pid    sudo lsof -iTCP -sTCP LISTEN -n -P   grep   port    awk    print  2      head -n 1  strip puts  PID    pid    kill -9   pid   unless pid empty    You can either run it in irb or inside a ruby file   For the latter  create server killer rb then run it with ruby server killer rb

User · Answer

To kill the puma process first run       lsof -wni tcp 3000    to show what is using port 3000  Then use the PID that comes with the result to run the kill process    For example after running        lsof -wni tcp 3000 you might get something like       COMMAND  PID  USER   FD   TYPE DEVICE SIZE OFF NODE NAME     ruby    3366 dummy    8u  IPv4  16901      0t0  TCP 127 0 0 1 3000  LISTEN    Now run the following to kill the process   where 3366 is the PID   kill -9 3366   Should resolve the issue

[ruby-on-rails] Rails: Address already in use - bind(2) (Errno::EADDRINUSE)

Examples related to ruby-on-rails

Examples related to puma