Application Error only in Detached Mode

Very strange one …

If I start my Radiant CMS with simply -

script/server -e production

it works without problem. However if I start it in detached mode with

script/server -e production -d

then I get -

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

There isn’t anything in the production.log to show a problem.

Any clues what gives ?

TIA

On Fri, Oct 16, 2009 at 12:57 AM, scotdb [email protected] wrote:

If I start my Radiant CMS with simply -
script/server -e production
it works without problem. However if I start it in detached mode with
script/server -e production -d

erm, that’s “daemon” mode, but regardless…

then I get -
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

There isn’t anything in the production.log to show a problem.
Any clues what gives ?

It would probably help you get better answers if you provided the
platform you’re on, the version of Ruby, the server (webrick, ?) etc.

Have you tried starting with the -u debugging flag?

Conversely, have you looked for where that error message is being
generated?


Hassan S. ------------------------ [email protected]
twitter: @hassan

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs