nyshadhamsriram-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2010-Jun-24 22:42 UTC
Mongrel rails cluster problem
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.
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 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
--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
This list is hopeless. I regret. On Fri, Jun 25, 2010 at 4:12 AM, nyshadhamsriram-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org < nyshadhamsriram-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> 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. > 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 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 > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<rubyonrails-talk%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
oh no! We have all been condemned! On Fri, Jun 25, 2010 at 9:47 AM, Sriram Nyshadham <nyshadhamsriram-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> This list is hopeless. I regret. > > > > > On Fri, Jun 25, 2010 at 4:12 AM, nyshadhamsriram-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org > <nyshadhamsriram-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: >> >> 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. >> 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 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 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Talk" group. >> To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org >> To unsubscribe from this group, send email to >> rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org >> For more options, visit this group at >> http://groups.google.com/group/rubyonrails-talk?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On 25 June 2010 15:47, Sriram Nyshadham <nyshadhamsriram-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> This list is hopeless. I regret. > > On Fri, Jun 25, 2010 at 4:12 AM, nyshadhamsriram-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org >> 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? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.