# Mongrel rails cluster problem

**URL:** <https://www.ruby-forum.com/t/mongrel-rails-cluster-problem/190707>\
**Category:** Rails\
**Created:** [June 25, 2010, 12:21pm UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-problem/190707 "2010-06-25T12:21:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [June 25, 2010, 12:21pm UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-problem/190707/1 "2010-06-25T12:21:57Z")

</div>

Hi All,

I am new to RoR and I have issue accessing my app through mongrel  
cluster.  
When I start only mongrel\_rails, I can access my app at  
[http://localhost:3000](http://localhost:3000).  
However, when I start mongrel\_cluster, I cannot access it on  
[http://localhost:3001](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 mongrel.pid  
-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.  
3001.pid and log/mongrel.3001.log for info.  
\*\* Starting Mongrel listening at 127.0.0.1:3001  
\*\* Starting Rails with production 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 1.1.5 available at 127.0.0.1:3001  
\*\* Writing PID file to tmp/pids/mongrel.3001.pid

Please suggest what mistake I am doing.

Thanks,  
Sri

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [June 25, 2010, 4:51pm UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-problem/190707/2 "2010-06-25T16:51:17Z")

</div>

This list is hopeless. I regret.

On Fri, Jun 25, 2010 at 4:12 AM, removed\_email\_address@domain.invalid \<

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [June 25, 2010, 4:55pm UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-problem/190707/3 "2010-06-25T16:55:23Z")

</div>

oh no! We have all been condemned!

On Fri, Jun 25, 2010 at 9:47 AM, Sriram N.

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [June 28, 2010, 11:15am UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-problem/190707/4 "2010-06-28T11:15:48Z")

</div>

On 25 June 2010 15:47, Sriram N. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> This list is hopeless. I regret.
> 
> On Fri, Jun 25, 2010 at 4:12 AM, removed\_email\_address@domain.invalid
> 
> > Please suggest what mistake I am doing.

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

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?
