Should overriding deploy:restart looks something like this?

set (:mongrel_conf) { "#{current_path}/config/mongrel_cluster.yml" }

namespace :deploy do
  task :restart do
    run "mongrel_rails cluster::restart -C #{mongrel_conf}"
  end
end

I'm only asking because it appeared to start the server, but I'm not
seeing the mongrel processes running.  :/

Thanks for the help!


On Jun 22, 3:10 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
> The defaultdeploy:restarttask uses script/process/reaper, so if you  
> aren't using script/process/spawner to start things up, you'll need to  
> overridedeploy:restartto use the correct restart commands.
>
> - Jamis
>
> On Jun 22, 2008, at 12:11 PM, CathyM wrote:
>
>
>
> > Still not fully resolved this issue.  After running deploy:cold after
> > setting up the mongrel cluster I thought it was resolved, as it went
> > through completion without errors.  However, subsequent deploy
> > commands now give me this error.
>
> >  * executing `deploy:restart'
> >  * executing "sudo -p 'sudo password: ' -u melvin /home/melvin/
> > public_html/fibj
> > productions.com/current/script/process/reaper"
> >    servers: ["fibjproductions.com"]
> >    [fibjproductions.com] executing command
> > *** [err :: fibjproductions.com] sudo: /home/melvin/public_html/
> > fibjproductions.
> > com/current/script/process/reaper: command not found
> >    command finished
> > command "sudo -p 'sudo password: ' -u melvin /home/melvin/public_html/
> > fibjproduc
> > tions.com/current/script/process/reaper" failed on fibjproductions.com
>
> > I have this line in my deploy.rb
>
> > set(:mongrel_conf){"#{current_path}/config/mongrel_cluster.yml"}
> > the mongrel_cluster_ctl status shows found for the pids file and
> > rails port file.
>
> > I don't understand why i am still getting the reaper error if I am
> > using mongrel clusters that seem to be working.
>
> > On Jun 20, 12:06 pm, CathyM <[EMAIL PROTECTED]> wrote:
> >> I changed my script/spin file to use mongrel_cluster instead of the
> >> process/spawner and it worked, at least the deploy:cold ended with no
> >> more errors.
>
> >> Thanks for all help provided.
>
> >> On Jun 20, 9:22 am, CathyM <[EMAIL PROTECTED]> wrote:
>
> >>> I think ~/process/spawner is called by the spin script that I had to
> >>> make executable with the following command: svn propset  
> >>> svn:executable
> >>> on script/spin
>
> >>> On Jun 20, 3:02 am, "Rafael G." <[EMAIL PROTECTED]> wrote:
>
> >>>> CathyM escribió:> *** [err :: fibjproductions.com] script/spin:  
> >>>> 1: /home/melvin/
> >>>>> public_html/fibjproductions.com/current/script/process/spawner:
> >>>>> Permission denied
>
> >>>> Does it execution permissions?
>
> >>>> --
> >>>> Rafael Garcia Ortega
>
> >>>> rgo.vcf
> >>>> 1KDownload
>
>
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to