瘦Web服务器:`start_tcp_server':git branch checkout后没有acceptor(RuntimeError)

时间:2012-03-07 16:31:41

标签: ruby-on-rails-3 git thin

一个Rails 3.2.0应用程序,可与本地和Heroku雪松堆栈上的瘦Web服务器一起使用。

后:

$ git branch work
$ git checkout work
$ rails server

我明白了:

=> Booting Thin
=> Rails 3.2.0 application starting in development on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
>> Thin web server (v1.3.1 codename Triple Espresso)
>> Maximum connections set to 1024
>> Listening on 0.0.0.0:3000, CTRL+C to stop
Exiting
/Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/eventmachine-0.12.10/lib/eventmachine.rb:572:in `start_tcp_server': no acceptor (RuntimeError)
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/eventmachine-0.12.10/lib/eventmachine.rb:572:in `start_server'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/thin-1.3.1/lib/thin/backends/tcp_server.rb:16:in `connect'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/thin-1.3.1/lib/thin/backends/base.rb:53:in `block in start'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `call'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/thin-1.3.1/lib/thin/backends/base.rb:61:in `start'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/thin-1.3.1/lib/thin/server.rb:159:in `start'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/rack-1.4.1/lib/rack/handler/thin.rb:13:in `run'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/rack-1.4.1/lib/rack/server.rb:265:in `start'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/railties-3.2.0/lib/rails/commands/server.rb:70:in `start'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/railties-3.2.0/lib/rails/commands.rb:55:in `block in <top (required)>'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/railties-3.2.0/lib/rails/commands.rb:50:in `tap'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/gems/railties-3.2.0/lib/rails/commands.rb:50:in `<top (required)>'
from script/rails:6:in `require'
from script/rails:6:in `<main>'

另外,当我这样做时:

sudo bundle exec rails server thin -p 3000

我明白了:

/Users/peter/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in `to_specs': Could not find bundler (>= 0) amongst [bigdecimal-1.1.0, io-console-0.3, json-1.5.4, minitest-2.5.1, rake-0.9.2.2, rdoc-3.9.4] (Gem::LoadError)
from /Users/peter/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in `to_spec'
from /Users/peter/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/site_ruby/1.9.1/rubygems.rb:1210:in `gem'
from /Users/peter/.rvm/gems/ruby-1.9.3-p125/bin/bundle:18:in `<main>'

我安装了bundler 1.0.22。更新并安装它。似乎没什么用。有什么想法吗?

9 个答案:

答案 0 :(得分:225)

这对我有用。查找(僵尸?)服务器(在服务器运行时退出终端时可能会发生):

$ ps ax | grep rails

如果它返回如下内容:

33467 s002 S+ 0:00.00 grep rails
33240 s003 S+ 0:15.05 /Users/Arta/.rbenv/versions/1.9.2-p290/bin/ruby script/rails s -p 3000

杀了它,然后重新开始:

$ kill -9 33240
$ rails s

答案 1 :(得分:63)

答案 2 :(得分:46)

pgrep ruby查看正在运行的服务器然后

kill -9 serverNumber

答案 3 :(得分:45)

如果有任何其他进程锁定端口,您可以找出它有这样的PID:

$ lsof -i :3000
COMMAND     PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
Passenger 40466 josh    5u  IPv4 0x7cae9332073ed4df      0t0  TCP *:hbci (LISTEN)
Passenger 40467 josh    5u  IPv4 0x7cae9332073ed4df      0t0  TCP *:hbci (LISTEN)

然后简单地杀死他/他们:

$ kill -9 40466
$ kill -9 40467

答案 4 :(得分:8)

  

rvmsudo rails server thin -p 3000

对我而言

答案 5 :(得分:6)

我有这个错误,因为我在里面运行了rails-dev-box和Rails。

Port 3000 in the host computer is forwarded to port 3000 in the virtual machine. 
Thus, applications running in the virtual machine can be accessed via 
localhost:3000 in the host computer.

所以从Vagrant退出并关闭它:

vagrant@rails-dev-box:/vagrant/rails$ exit
$ vagrant halt

这帮助了我。

答案 6 :(得分:5)

我遇到了这个错误,因为我已经在另一个终端运行rails了。关闭我的其他项目解决了这个问题。

答案 7 :(得分:2)

我从假期回到办公室后遇到了类似的问题。我在本地IP上运行我的服务器:

rails s thin -b <my_ip>

问题是我的IP发生了变化,我只需要使用新的IP。

答案 8 :(得分:2)

在终端

中执行此操作
sudo netstat -lpn |grep rails

然后

sudo kill <job id>