Hi Joe:

If you've installed the mongrel_cluster script in /etc/init.d,  it
will by default use /etc/mongrel_cluster as the path for the
configuration files. That script calls 'mongrel_cluster_ctl' (which
also defaults to /etc/mongrel_cluster). So, an easy way to debug is
use 'sudo mongrel_cluster_ctl start -v' to see why the mongrels are
failing to start.

Regards,
Bradley Taylor
http://railsmachine.com


On Mar 20, 12:46 pm, Joe Zz <[EMAIL PROTECTED]> wrote:
> Bradley Taylor wrote:
> > Hi:
>
> > When not in RAILS_ROOT, you need to pass the path of the configuration
> > file to the start command. From RAILS_ROOT, the default is the
> > relative path of 'config/mongrel_cluster.yml'.
>
> > mongrel_rails cluster::start -C /etc/mongrel_cluster/
> > mongrel_cluster.yml
>
> > You can also use, 'mongrel_cluster_ctl start' which will start all
> > clusters in /etc/mongrel_cluster.
>
> > Regards,
> > Bradley Taylor
> >http://railsmachine.com
>
> Sorry Bradley, i forgot to mention it works when manually entering the
> path to the config... my bad. the problem is in situations where i don't
> have the option to pass the path... deployment and boot. i came across
> the info about setting the config path for cap in the deploy.rb. and am
> going to work that out right now, but how do i set the proper path to
> allow the service to start, and consequently get it to start on boot?
> looking at the boot.log there are 4 entries regarding the cluster, all
> at 12:05:45. first entry is the custom require.rb error mentioned above,
> next entry is "localhost mongrel_cluster: Starting all
> mongrel_clusters...", next entry is "localhost mongrel_cluster:
> mongrel_rails cluster::start returned an error", then strangely the next
> is "localhost rc: Starting mongrel_cluster: succeeded" but it doesn't.
> no process and no ports listening. so, like i mentioned, how do i get it
> to look at the right path for boot?
>
> thanks much.
>
> --
> Posted viahttp://www.ruby-forum.com/.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to