[Instiki] Apache Application Error after Save
Joel W. Garman
joel.w.garman at biola.edu
Tue Jun 30 15:24:56 EDT 2009
Instiki-users <instiki-users at rubyforge.org> writes:
>
>
>And you're sure it's not MySQL that's died?
>(If the database is unavailable, that would surely result in an
>application error, no matter what page you attempted to access.)
>
>And does "reinstalling" also involve restarting MySQL?
Reinstalling Instiki does not involve restarting MySQL. I just extract
the folder from the zip again, change my database.yml and I'm up and
running.
>ruby should produce an error output that tells a little more about
>what happened.
>i am not sure where the windows version of ruby keeps that, on unix
>based systems this is usually in the console.
>
>what about the window from where you start instiki.cmd ?
The window instiki.cmd starts in is not visible because the user account
does not have access to the desktop. Would the error show up in the
production log at all? I can run Instiki in a visible window under a
different user for a couple of days to see if the error occurs and I get
any ruby errors. I don't suppose there is any error log that ruby keeps?
Thanks,
Joel
More information about the Instiki-users
mailing list