Hi i hv problem in gems pack......in ruby on rails pls help

ash · December 31, 2009, 9:04am

Error:

Exiting
/home/ashok/rubystack-2.0-0/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in
initialize_without_backlog': Address already in use - bind(2) (Errno::EADDRINUSE) from /home/ashok/rubystack-2.0-0/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:ininitialize’
from
/home/ashok/rubystack-2.0-0/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:93:in
new' from /home/ashok/rubystack-2.0-0/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:93:ininitialize’
from
/home/ashok/rubystack-2.0-0/ruby/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/handler/mongrel.rb:10:in
new' from /home/ashok/rubystack-2.0-0/ruby/lib/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/handler/mongrel.rb:10:inrun’
from
/home/ashok/rubystack-2.0-0/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/commands/server.rb:111
from
/home/ashok/rubystack-2.0-0/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
gem_original_require' from /home/ashok/rubystack-2.0-0/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:inrequire’
from script/server:3

ash · December 31, 2009, 9:15am

you have more than one instance of rails (mongrel server) running, i
think.
see if you have another ruby process (which should be running
script/server) already.

ash · December 31, 2009, 9:24am

On 31.12.2009 09:04, Ashok Bhandari wrote:

Error:

Exiting
/home/ashok/rubystack-2.0-0/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in
`initialize_without_backlog’: Address already in use - bind(2)

Bind is using the address your Mongrel wants to use already.

ash · December 31, 2009, 9:29am

On 31.12.2009 09:19, Phillip G. wrote:

On 31.12.2009 09:04, Ashok Bhandari wrote:

Error:

Exiting
/home/ashok/rubystack-2.0-0/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in

`initialize_without_backlog’: Address already in use - bind(2)

Bind is using the address your Mongrel wants to use already.

Right, disregard that. I forgot that Ruby outputs the offending method,
not the offending program using the address/port.