Thanks guys for the reply!
Max,
Your problem seems familiar. We also did this mistake once. The result
was that root owned some uploaded documents which then couldn't be
changed by a mongrel cluster not started as root. I will definitely
look closer at this. I don't know if this problem got fixed after we
solved the root problem.
We solved the root problem by creating a simple script:
echo 'password' | sudo -u www-user -S /usr/bin/mongrel_rails cluster::
${1} -C /etc/mongrel_cluster/boass${2}.yml
If you are not familiar with bash this script takes two arguments.
Argument one is: start, stop, restart or status. And argument two is
which stage. We have two: staging and production. We have stored the
configuration files for each stage in /etc/mongrel_cluster/.
Thanks!
On Oct 16, 11:43 am, max <[EMAIL PROTECTED]> wrote:
> Hi
>
> I've just experienced a similar problem with a rails app deployed with
> capistrano, and served by apache2 + mongrel cluster.
>
> The problem had nothing to do with capistrano or any cache mechanism
> (server or client - side) ...
> but was due to the way we started / stopped our mongrel cluster.
>
> It appeared we accidentally restarted the cluster as "root" on one of
> our app servers, with our previous release.
> Other app servers still ran mongrel instances as "www-data" user
> (replace by whatever user do you use to start your mongrels).
>
> When deploying the new version, cap couldn't stop mongrel processes
> launched as "root", but still started new processes as "www-data".
>
> So, "root" mongrel processes pointed to old release, and "www-data"
> mongrel processes to new one, giving us a weird mix of the 2 releases
> when loading a page.
>
> We add to manually kill the "mongrel_rails" processes", and start
> again all mongrel clusters (on every app server) as "www-data".
>
> Problem fixed.
>
> Hope that helped !
>
> ++
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
