Mongrel rails cluster problem

Hi All,

I am new to RoR and I have issue accessing my app through mongrel
When I start only mongrel_rails, I can access my app at http://localhost:3000.
However, when I start mongrel_cluster, I cannot access it on
http://localhost:3001 ( which is what ideally expected?).

When I check the status, everything looks fine, and also i don't see
any errors on mongrel_3001.log or 3000.log.

    root 5043 11457 0 22:26:53 ? 0:01 /opt/local/bin/
ruby18 /opt/local/bin/mongrel_rails start -d
    root 4728 11457 0 22:24:52 ? 0:01 /opt/local/bin/
ruby18 /opt/local/bin/mongrel_rails start -d -e production -a 12
    root 4725 11457 0 22:24:52 ? 0:02 /opt/local/bin/
ruby18 /opt/local/bin/mongrel_rails start -d -e production -a 12

/opt/blog/log]# ll
total 50
-rw-rw-rw- 1 root root 16786 Jun 24 22:29 development.log
-rw-rw-rw- 1 root root 1079 Jun 24 22:24 mongrel.3000.log
-rw-rw-rw- 1 root root 1079 Jun 24 22:24 mongrel.3001.log
-rw-rw-rw- 1 root root 1023 Jun 24 22:26 mongrel.log
-rw-r--r-- 1 root root 4 Jun 24 22:26
-rw-rw-rw- 1 root root 0 Jun 24 21:40 production.log
-rw-rw-rw- 1 root root 0 Jun 24 21:40 server.log
-rw-rw-rw- 1 root root 0 Jun 24 21:40 test.log

/opt/blog/log]# tail -f mongrel.3001.log
** TERM signal received.
** Daemonized, any open files are closed. Look at tmp/pids/mongrel. and log/mongrel.3001.log for info.
** Starting Mongrel listening at
** Starting Rails with production environment...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready. TERM => stop. USR2 => restart. INT => stop (no
** Rails signals registered. HUP => reload (without restart). It
might not work well.
** Mongrel 1.1.5 available at
** Writing PID file to tmp/pids/

Please suggest what mistake I am doing.


This list is hopeless. I regret.

oh no! We have all been condemned!

Expecting a reply solving your problem before even half a day has
passed, and chastising us for failing to meet your unrealistic

With reference to you original post: no idea. It all looks good to me.
When you say "I cannot access it on 3001" can you expand on what
happens when you try? Do you get a 404 error in your browser or
something else?