That is a bit of a weird trace. I can't quite follow how a trace 
that looked like that could happen (I don't see how the inflector 
would want to get involved during the file opening process).

It's falling over during the writing of the .yml file (line 169),
I'm guessing that's due to multiple processes both trying to do
that writing. If you upgrade to current svn, you wont have the
problem with subsequent requests failing, but you might still
get the original error.

I'll have a look at putting a rescue in that code to make sure 
that if there's any problem trying to write out the cache that 
it just continues on without breaking the current request.

 
> SystemExit (exit):
>     
> /vendor/radiant/vendor/rails/railties/lib/fcgi_handler.rb:116:
> in `exit'
>     /vendor/radiant/vendor/rails/railties/lib/fcgi_handler.rb:116:in
> `exit_now_handler'
>     
> /vendor/radiant/vendor/rails/activerecord/lib/../../activesupp
> ort/lib/active_support/inflector.rb:250:in
> `to_proc'
>     /vendor/radiant/app/models/response_cache.rb:169:in `call'
>     /vendor/radiant/app/models/response_cache.rb:169:in `cache_page'
>     /vendor/radiant/app/models/response_cache.rb:169:in `open'
>     /vendor/radiant/app/models/response_cache.rb:169:in `cache_page'
>     
_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to