Mongrel users - Jun 2006 - mongrel (0.3.12.4) blows up

Hello, I don''t know if this is really relevant anymore because a new  
version is about to be released it seems, however I''ve been trying to  
run mongrel 0.3.12.4 on a development server in development mode  
(simply with mongrel_rails start). I try to access the server and the  
first page (static file) loads, but then the server dies and I get  
this in the logs.

I''m not sure if it''s a problem with me, my configuration, or
mongrel,
but I switched back to webrick for now. I am running ruby 1.8.4  
(2005-12-24) [i386-freebsd5].

** Starting Rails in environment development ...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready.  TERM => stop.  USR2 => restart.  INT => stop (no  
restart).
** Rails signals registered.  HUP => reload (without restart).  It  
might not work well.
** Running 0.0.0.0:3000 listener.
** Mongrel available at 0.0.0.0:3000
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/mongrel/ 
tcphack.rb:6:in `initialize_without_backlog'': Address already in use  
- bind(2) (Errno::EADDR
INUSE)
         from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/ 
mongrel/tcphack.rb:6:in `initialize''
         from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/ 
mongrel.rb:387:in `initialize''
         from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/ 
mongrel.rb:653:in `listener''
         from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/bin/ 
mongrel_rails:69:in `cloaker_''
         from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/ 
mongrel.rb:616:in `initialize''
         from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/bin/ 
mongrel_rails:61:in `run''
         from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/ 
mongrel/command.rb:163:in `run''
         from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/bin/ 
mongrel_rails:194
         from /usr/local/bin/mongrel_rails:18
** TERM signal received.
** Stopping 0.0.0.0:3000 listener.
Server stopped.  Exiting.

Thanks,
Carl

You already have something on that box (maybe even an daemonized  
mongrel_rails process) running on port 3000

Try doing a netstat -tlp (if your netstat supports that) and seeing  
what other process is holding on to port 3000.

Jason


On Jun 10, 2006, at 7:41 PM, Carl Lerche wrote:
> Hello, I don''t know if this is really relevant anymore because a
new
> version is about to be released it seems, however I''ve been trying
to
> run mongrel 0.3.12.4 on a development server in development mode
> (simply with mongrel_rails start). I try to access the server and the
> first page (static file) loads, but then the server dies and I get
> this in the logs.
>
> ** Mongrel available at 0.0.0.0:3000
> /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/mongrel/
> tcphack.rb:6:in `initialize_without_backlog'': Address already in
use
> - bind(2) (Errno::EADDR
> INUSE)



--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jason Young --  Systems Engineer, eXtension
  http://about.extension.org/wiki/Jason_Young
______________________________________