On Aug 14, 2007, at 1:03 AM, Paul Sturgess wrote:
> I have been trying to use the following simple task to restart mongrel
> (note I'm running a single instance):
do you have the mongrel_cluster gems installed? It adds all sorts of
tasks to capistrano, which makes those custom run clauses unnecessary.
also, I found that upgrading to cap2, and making changes in
namespaces adds a lot of ease to the process as well.
for example:
===
namespace :deploy do
desc "Restart mongrel"
task :restart, :roles => :app do
restart_mongrel_cluster
end
desc "Start mongrel"
task :start, :roles => :app do
start_mongrel_cluster
end
desc "Stop mongrel"
task :stop, :roles => :app do
stop_mongrel_cluster
end
end
===
> !!! PID file log/mongrel.pid does not exist. Not running?
> mongrel::stop reported an error. Use mongrel_rails mongrel::stop -h to
What's the status of the APP/current/log directory. Is it a link, or
an actual directory. Is the link good?
It ought to be a link into the shared/log directory.
> run "kill `ps | grep #{mongrel_port} | egrep -v grep | awk '{print
> $2}'`"
This ps command will not list all of the processes you need. You
probably want "ps -ax" or "ps -ef", depending on the system flavour.
Your ps|grep chain is returning no processes, which is why kill is
choking.
However, you shouldn't need this, if you can use the mongrel gems.
Cheers,
-j
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Capistrano" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.co.uk/group/capistrano?hl=en
-~----------~----~----~----~------~----~------~--~---
