Instiki users - Apr 2009 - [Instiki] Instiki 0.16.5 crash on Server 2k8

I am running Instiki 0.16.5 on a Windows Server 2008 box with MySQL
5.1.31.  I have had Instiki crash twice, both times during a basic page
edt.  I was editing a page, clicked submit, and received the Apache error.
 From the production.log:

Processing WikiController#save (for 10.5.17.24 at 2009-04-14 16:16:16)
[POST]
  Parameters: {"author"=>"Joel Garman",
"id"=>"Ghostserver",
"content"=>"[a lot of text]", 
"web"=>"libraryitdeptdocumentation"}

Nothing unusual during the page edt but I do have a bunch of "Expired
Fragment:" entries

Received the general Apache error...

"Application error (Apache)
Something very bad just happened. I just know it. Do you smell smoke?"

I restarted instiki...

"D:\instiki>ruby.exe script\server -e production
=> Booting WEBrick
=> Rails 2.3.2 application starting on http://0.0.0.0:2500
=> Call with -d to detach
=> Ctrl-C to shutdown server
[2009-04-14 16:25:14] INFO  WEBrick 1.3.1
[2009-04-14 16:25:14] INFO  ruby 1.8.6 (2007-09-24) [i386-mswin32]
[2009-04-14 16:25:14] INFO  WEBrick::HTTPServer#start: pid=1656 port=2500"

And still receive the general Apache error with no error or info on screen
or in the log...

"Application error (Apache)
Something very bad just happened. I just know it. Do you smell smoke?"

Thanks,
Joel

Instiki-users <instiki-users at rubyforge.org>
writes:
>
>
>Did Instiki crash, or did you (just) get a generic "Do you smell  
>smoke?" Application error?
It was the generic "Do you smell smoke?" application
error.
>
>
>If you got a "Do you smell smoke?" error, then there should be a  
>corresponding backtrace in the logfile.
>If you want help tracking down the source of the error, including a  
>copy of that backtrace would be important.
There was no backtrace in the production.log or onscreen.  After an
Instiki restart, HTTP server would start but I still got the application
error.  When attempting to go to the HomePage or web_list there was no
[get] command, merely the application error.

I deleted the existing Instiki directory and created it again, recreating
all the files from the .zip of 0.16.5.  This seemed to solve the problem.

I know not many of you have Windows Server 2008 so there isn''t much
testing but I would like to know if anyone has experienced anything like
this.  This has happened multiple times.
>
>
>Jacques
>_______________________________________________
>Instiki-users mailing list
>Instiki-users at rubyforge.org
>http://rubyforge.org/mailman/listinfo/instiki-users
Joel