I'll update this for the group. It seems that some old mongrel processes were not successfully killed. My best guess is that these processes were picking up the requests and had loaded the older versions of the code.
Hunting down and killing those old processes, then verifying that the newly installed code came up cleanly resolved the issue. - pdp > From: Peter Degen-Portnoy <pport...@avenue100.com> > Reply-To: Radiant Mailing List <radiant@radiantcms.org> > Date: Wed, 10 Feb 2010 16:38:07 -0500 > To: Radiant Mailing List <radiant@radiantcms.org> > Subject: [Radiant] Capistrano, old release directories and cache > > Hi Folks, > > We are testing our application and I am delighted with how much we were able > to put together in a short time. Radiant is really working for us. > > I just tracked down some strange behavior and am hoping that this is > something that folks have encountered before and can help me understand. > > We use a series of tools to manage our deploys into our target environments, > amongst them Capistrano. Cap, as I¹m sure you are aware, creates new > directories in the releases folder and updates the symbolic link ³current² > to point to the newest release. > > I just encountered a problem in QA where a controller in the current > directory was getting an instance of a model in one of the older release > directories. It was clearly apparent because the paths are visible in the > stack trace. > > Because of that, I moved the older directory and did a number of page > refreshes to get the current content displayed correctly. > > What puzzles me the most is that with each install (the ³stuck² version was > a few installations back), the mongrel processes are killed, pids are > cleaned up, and the processes are re-started. Of course, one aspect of > Capistrano is that there is a shared tmp directory between all releases. I > checked to see if there were any files sitting in the tmp directory though > and all directories and sub directories were empty. > > Has anyone encountered something like this before? Thanks so much for your > time. > > - Peter > > _______________________________________________ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > List Site: http://lists.radiantcms.org/mailman/listinfo/radiant > Radiant: http://radiantcms.org > Extensions: http://ext.radiantcms.org _______________________________________________ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
