A 500 error is coming from your application server and not the application.
Check your mongrel log (for example, if you're using mongrel).
On Sat, Mar 20, 2010 at 11:42 AM, Earl Chew <earl_c...@yahoo.com> wrote:
> I'm upgrading my small Radiant installation from way back (0.6 or
> thereabouts).
>
> I've got most of it working, but when running as a mongrel_cluster (with
> user/group mongrel) I get a public/500.html when accessing some pages.
>
> I look in production.log and only see:
>
> Processing SiteController#show_page (for 127.0.0.1 at 2010-03-20 08:39:16)
> [GET]
> Parameters: {"url"=>["public", "hacking", "misc"], "action"=>"show_page",
> "controller"=>"site"}
> Completed in 1839ms (DB: 63) | 200 [http://localhost/public/hacking/misc/]
>
>
> but the browser renders:
>
>
> Application error
>
> Change this error message for exceptions thrown outside of an action (like in
> Dispatcher setups or broken Ruby code) in public/500.html
>
>
> I'm puzzled because the Radiant log doesn't show any problem.
>
> Where should I look next to debug this ?
>
>
> Earl
>
--
Jim Gay
http://www.saturnflyer.com
_______________________________________________
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
