Hi Geoff,

Thanks for your thoughts.  Here is the results of my test.

*From Windows*
> cap show_path
  * executing `show_path'
  * executing "echo $PATH"
    servers: ["hostname.local"]
Password:
    [EMAIL PROTECTED] executing command
 ** [out :: [EMAIL PROTECTED]
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
    command finished

*From cap shell*
cap> echo $PATH
 ** [out :: [EMAIL PROTECTED]
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games


Thanks,
Ben



>
> Just wondering if its a path issue, try adding and running
>
> task :show_path do
>     run "echo $PATH"
> end
>
> then try running the show_path task from both the command line and the
> cap shell.
>
> Additionally the cluster restart command may be run through sudo
> unless you've turned off sudo usage.
>
> Geoff
>
> On 3 Jun, 07:14, BenL <[EMAIL PROTECTED]> wrote:
>> Hi Guys,
>>
>> I am using cap to deploy a ruby on rails project.  The deployment is
>> working fine, but the restarting of the mongrel service is not
>> working.
>>
>> When I execute "cap mongrel:cluster:restart" I get the following
>> error:
>> command "mongrel_rails cluster::restart -C /home/username/deployed/
>> current/config/mongrel_cluster.yml" failed on [EMAIL PROTECTED]
>>
>> If I run "cap shell" and manually enter the command that failed, the
>> mongrel_restart will work as expected.
>>
>> Cap deploy and the like all execute normally.
>>
>> The only thing that is not default about my setup is that I needed to
>> enter this line into my deploy.rb to get the ssh commands to execute
>> at all (all the remote commands were failing).  I have no idea if this
>> is related or not.
>> default_run_options[:pty] = true
>>
>> Any thoughts on this would be greatly appreciated!
>>
>> ~Ben
> >
>



--~--~---------~--~----~------------~-------~--~----~
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