[Mongrel] mongrel 1.0.3

Luis Lavena luislavena at gmail.com
Sat Oct 27 13:24:12 EDT 2007


On 10/27/07, Alexander Logvinov <freebsd at akavia.ru> wrote:
> Hello!
>
> # /usr/local/bin/ruby18 /usr/local/bin/mongrel_rails start -d -e development -a 10.164.28.7 -c /var/www/data/site/ --user root --group wheel -p 8080 -P log/mongrel.8080.pid -l log/mongrel.8080.log
>
> Mongrel 1.0.1:
>
> ** Starting Mongrel listening at 10.164.28.7:8080
>                                  ^^^^^^^^^^^^^^^^
> ** Changing group to wheel.
> ** Changing user to root.
> ** Starting Rails with development environment...
> ** 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.
> ** Mongrel available at 10.164.28.7:8080
> ** Writing PID file to log/mongrel.8080.pid
>
> Mongrel 1.0.3:
>
> ** Starting Mongrel listening at :8080
>                                  ^^^^^ ???
> ** Starting Rails with development environment...
> ** 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.
> ** Mongrel available at 10.164.28.7:8080
> ** Writing PID file to log/mongrel.8080.pid
>
>

It seems is not handling the IP binding...

Could you try the following in a IRB console?

require 'rubygems'
require 'mongrel'
s = Mongrel::HttpServer.new("127.0.0.1", 8081)
puts "Host: #{s.host}, Port: #{s.port}"

It's using a TCPServer inside, so it should work, unless mongrel_rails
is doing something else with the address (host) passed by.

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi


More information about the Mongrel-users mailing list