thr3ads.net - Instiki users - [Instiki] Apache Application Error after Save [Jun 2009]

If this information is useful, please help other people find it:
Share via:

Joel W. Garman

2009-Jun-16 20:59 UTC

[Instiki] Apache Application Error after Save

I have has this same problem a couple of times.  When a user goes to save
a page (not all the time just some of the time), the Apache app error
shows up, halting the wiki.  No pages are rendered, simply the app error
(can''t get to HomePage or web_list or any specific pages).  To solve
the
problem I have to delete and recreate the Instiki directory.  

Thoughts of dsnbl malfunctioning were considered but the error occurs with
0.16.6

Here is the production.log just before the crash (what are the expired
fragments):

Processing WikiController#edit (for 10.5.17.24 at 2009-06-09 10:43:28)
[GET]
  Parameters: {"id"=>"HomePage",
"web"=>"circulation"}
Reading page ''HomePage'' from web
''circulation''
Page ''HomePage''  found
Rendering template within layouts/default
Rendering wiki/edit
Completed in 125ms (View: 78, DB: 31) | 200 OK
[http://libweb.biola.edu/circulation/edit/HomePage]


Processing WikiController#save (for 10.5.17.24 at 2009-06-09 10:43:37)
[POST]
  Parameters:
{"_form_key"=>"ccabfefae197829322efcfab19ff6e755714aeee",
"author"=>"Joel Garman",
"id"=>"HomePage", "content"=>"h2.
Welcome to the
Circulation Manual\r\n\r\nTable of Contents",
"web"=>"circulation"}
Reading page ''HomePage'' from web
''circulation''
Page ''HomePage''  found
10.5.17.24
Reading page ''HomePage'' from web
''circulation''
Page ''HomePage''  found
Expired fragment: views/circulation/recently_revised (0.0ms)
Expired fragment: views/circulation/recently_revised/S (0.0ms)
Expired fragment: views/circulation/recently_revised/W (0.0ms)
Expired fragment: views/circulation/recently_revised/I (0.0ms)
Expired fragment: views/circulation/recently_revised/R (0.0ms)
Expired fragment: views/circulation/recently_revised/S (0.0ms)
Expired fragment: views/circulation/recently_revised/G (0.0ms)
Expired fragment: views/circulation/recently_revised/R (0.0ms)
Expired fragment: views/circulation/recently_revised/S (0.0ms)
Expired fragment: views/circulation/recently_revised/A (15.0ms)
Expired fragment: views/circulation/recently_revised/L (0.0ms)
Expired fragment: views/circulation/recently_revised/C (0.0ms)
Expired fragment: views/circulation/recently_revised/I (0.0ms)
Expired fragment: views/circulation/recently_revised/D (0.0ms)
Expired fragment: views/circulation/recently_revised/W (0.0ms)
Expired fragment: views/circulation/recently_revised/R (0.0ms)
Expired fragment: views/circulation/recently_revised/M (0.0ms)
Expired fragment: views/circulation/recently_revised/M (0.0ms)
Expired fragment: views/circulation/recently_revised/S (0.0ms)
Expired fragment: views/circulation/recently_revised/P (0.0ms)
Expired fragment: views/circulation/recently_revised/E (0.0ms)
Expired fragment: views/circulation/recently_revised/E (0.0ms)
Expired fragment: views/circulation/recently_revised/L (16.0ms)
Expired fragment: views/circulation/recently_revised/A (0.0ms)
Expired fragment: views/circulation/recently_revised/B (0.0ms)
Expired fragment: views/circulation/recently_revised/B (0.0ms)
Expired fragment: views/circulation/recently_revised/B (0.0ms)
Expired fragment: views/circulation/recently_revised/P (0.0ms)
Expired fragment: views/circulation/recently_revised/S (0.0ms)
Expired fragment: views/circulation/recently_revised/B (0.0ms)
Expired fragment: views/circulation/recently_revised/B (0.0ms)
Expired fragment: views/circulation/recently_revised/L (0.0ms)
Expired fragment: views/circulation/recently_revised/C (0.0ms)
Expired fragment: views/circulation/recently_revised/C (0.0ms)
Expired fragment: views/circulation/recently_revised/S (0.0ms)
Expired fragment: views/circulation/list (0.0ms)
Expired fragment: views/circulation/list/S (0.0ms)
Expired fragment: views/circulation/list/W (0.0ms)
Expired fragment: views/circulation/list/I (0.0ms)
Expired fragment: views/circulation/list/R (0.0ms)
Expired fragment: views/circulation/list/S (0.0ms)
Expired fragment: views/circulation/list/G (0.0ms)
Expired fragment: views/circulation/list/R (0.0ms)
Expired fragment: views/circulation/list/S (0.0ms)
Expired fragment: views/circulation/list/A (0.0ms)
Expired fragment: views/circulation/list/L (0.0ms)
Expired fragment: views/circulation/list/C (0.0ms)
Expired fragment: views/circulation/list/I (0.0ms)
Expired fragment: views/circulation/list/D (0.0ms)
Expired fragment: views/circulation/list/W (15.0ms)
Expired fragment: views/circulation/list/R (0.0ms)
Expired fragment: views/circulation/list/M (0.0ms)
Expired fragment: views/circulation/list/M (0.0ms)
Expired fragment: views/circulation/list/S (0.0ms)
Expired fragment: views/circulation/list/P (0.0ms)
Expired fragment: views/circulation/list/E (0.0ms)
Expired fragment: views/circulation/list/E (0.0ms)
Expired fragment: views/circulation/list/L (0.0ms)
Expired fragment: views/circulation/list/A (0.0ms)
Expired fragment: views/circulation/list/B (0.0ms)
Expired fragment: views/circulation/list/B (0.0ms)
Expired fragment: views/circulation/list/B (0.0ms)
Expired fragment: views/circulation/list/P (0.0ms)
Expired fragment: views/circulation/list/S (0.0ms)
Expired fragment: views/circulation/list/B (0.0ms)
Expired fragment: views/circulation/list/B (0.0ms)
Expired fragment: views/circulation/list/L (0.0ms)
Expired fragment: views/circulation/list/C (0.0ms)
Expired fragment: views/circulation/list/C (0.0ms)
Expired fragment: views/circulation/list/S (0.0ms)

Mag. Matthias Tarasiewicz

2009-Jun-17 09:52 UTC

head link

[Instiki] Apache Application Error after Save

can you tell us which version of apache you are using, under which os?  
are you using phusion passenger to run instiki?

to me this looks like the fragments are not writable/modifyable -- i  
think this could be related to your instiki file access rights (or  
user/group rights) are not the same as the phusion passenger user.

-m


On 16.06.2009, at 22:59, Joel W. Garman wrote:
> I have has this same problem a couple of times.  When a user goes to  
> save
> a page (not all the time just some of the time), the Apache app error
> shows up, halting the wiki.  No pages are rendered, simply the app  
> error
> (can''t get to HomePage or web_list or any specific pages).  To
solve
> the
> problem I have to delete and recreate the Instiki directory.
>
> Thoughts of dsnbl malfunctioning were considered but the error  
> occurs with
> 0.16.6
>
> Here is the production.log just before the crash (what are the expired
> fragments):
>
> Processing WikiController#edit (for 10.5.17.24 at 2009-06-09 10:43:28)
> [GET]
>  Parameters: {"id"=>"HomePage",
"web"=>"circulation"}
> Reading page ''HomePage'' from web
''circulation''
> Page ''HomePage''  found
> Rendering template within layouts/default
> Rendering wiki/edit
> Completed in 125ms (View: 78, DB: 31) | 200 OK
> [http://libweb.biola.edu/circulation/edit/HomePage]
>
>
> Processing WikiController#save (for 10.5.17.24 at 2009-06-09 10:43:37)
> [POST]
>  Parameters:
{"_form_key"=>"ccabfefae197829322efcfab19ff6e755714aeee",
> "author"=>"Joel Garman",
"id"=>"HomePage", "content"=>"h2.
Welcome
> to the
> Circulation Manual\r\n\r\nTable of Contents",
"web"=>"circulation"}
> Reading page ''HomePage'' from web
''circulation''
> Page ''HomePage''  found
> 10.5.17.24
> Reading page ''HomePage'' from web
''circulation''
> Page ''HomePage''  found
> Expired fragment: views/circulation/recently_revised (0.0ms)
> Expired fragment: views/circulation/recently_revised/S (0.0ms)
> Expired fragment: views/circulation/recently_revised/W (0.0ms)
> Expired fragment: views/circulation/recently_revised/I (0.0ms)
> Expired fragment: views/circulation/recently_revised/R (0.0ms)
> Expired fragment: views/circulation/recently_revised/S (0.0ms)
> Expired fragment: views/circulation/recently_revised/G (0.0ms)
> Expired fragment: views/circulation/recently_revised/R (0.0ms)
> Expired fragment: views/circulation/recently_revised/S (0.0ms)
> Expired fragment: views/circulation/recently_revised/A (15.0ms)
> Expired fragment: views/circulation/recently_revised/L (0.0ms)
> Expired fragment: views/circulation/recently_revised/C (0.0ms)
> Expired fragment: views/circulation/recently_revised/I (0.0ms)
> Expired fragment: views/circulation/recently_revised/D (0.0ms)
> Expired fragment: views/circulation/recently_revised/W (0.0ms)
> Expired fragment: views/circulation/recently_revised/R (0.0ms)
> Expired fragment: views/circulation/recently_revised/M (0.0ms)
> Expired fragment: views/circulation/recently_revised/M (0.0ms)
> Expired fragment: views/circulation/recently_revised/S (0.0ms)
> Expired fragment: views/circulation/recently_revised/P (0.0ms)
> Expired fragment: views/circulation/recently_revised/E (0.0ms)
> Expired fragment: views/circulation/recently_revised/E (0.0ms)
> Expired fragment: views/circulation/recently_revised/L (16.0ms)
> Expired fragment: views/circulation/recently_revised/A (0.0ms)
> Expired fragment: views/circulation/recently_revised/B (0.0ms)
> Expired fragment: views/circulation/recently_revised/B (0.0ms)
> Expired fragment: views/circulation/recently_revised/B (0.0ms)
> Expired fragment: views/circulation/recently_revised/P (0.0ms)
> Expired fragment: views/circulation/recently_revised/S (0.0ms)
> Expired fragment: views/circulation/recently_revised/B (0.0ms)
> Expired fragment: views/circulation/recently_revised/B (0.0ms)
> Expired fragment: views/circulation/recently_revised/L (0.0ms)
> Expired fragment: views/circulation/recently_revised/C (0.0ms)
> Expired fragment: views/circulation/recently_revised/C (0.0ms)
> Expired fragment: views/circulation/recently_revised/S (0.0ms)
> Expired fragment: views/circulation/list (0.0ms)
> Expired fragment: views/circulation/list/S (0.0ms)
> Expired fragment: views/circulation/list/W (0.0ms)
> Expired fragment: views/circulation/list/I (0.0ms)
> Expired fragment: views/circulation/list/R (0.0ms)
> Expired fragment: views/circulation/list/S (0.0ms)
> Expired fragment: views/circulation/list/G (0.0ms)
> Expired fragment: views/circulation/list/R (0.0ms)
> Expired fragment: views/circulation/list/S (0.0ms)
> Expired fragment: views/circulation/list/A (0.0ms)
> Expired fragment: views/circulation/list/L (0.0ms)
> Expired fragment: views/circulation/list/C (0.0ms)
> Expired fragment: views/circulation/list/I (0.0ms)
> Expired fragment: views/circulation/list/D (0.0ms)
> Expired fragment: views/circulation/list/W (15.0ms)
> Expired fragment: views/circulation/list/R (0.0ms)
> Expired fragment: views/circulation/list/M (0.0ms)
> Expired fragment: views/circulation/list/M (0.0ms)
> Expired fragment: views/circulation/list/S (0.0ms)
> Expired fragment: views/circulation/list/P (0.0ms)
> Expired fragment: views/circulation/list/E (0.0ms)
> Expired fragment: views/circulation/list/E (0.0ms)
> Expired fragment: views/circulation/list/L (0.0ms)
> Expired fragment: views/circulation/list/A (0.0ms)
> Expired fragment: views/circulation/list/B (0.0ms)
> Expired fragment: views/circulation/list/B (0.0ms)
> Expired fragment: views/circulation/list/B (0.0ms)
> Expired fragment: views/circulation/list/P (0.0ms)
> Expired fragment: views/circulation/list/S (0.0ms)
> Expired fragment: views/circulation/list/B (0.0ms)
> Expired fragment: views/circulation/list/B (0.0ms)
> Expired fragment: views/circulation/list/L (0.0ms)
> Expired fragment: views/circulation/list/C (0.0ms)
> Expired fragment: views/circulation/list/C (0.0ms)
> Expired fragment: views/circulation/list/S (0.0ms)
>
> _______________________________________________
> Instiki-users mailing list
> Instiki-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/instiki-users

Joel W. Garman

2009-Jun-17 19:03 UTC

head link

[Instiki] Apache Application Error after Save

Instiki-users <instiki-users at rubyforge.org>
writes:>can you tell us which version of apache you are using, under which os?  
>are you using phusion passenger to run instiki?
I''m running Instiki 0.16.6 on Win2008 Server.  Whatever version of
Apache
is bundled with Instiki is what I''m using.  I''m also running
mysql as the
database engine for instiki.>
>to me this looks like the fragments are not writable/modifyable -- i  
>think this could be related to your instiki file access rights (or  
>user/group rights) are not the same as the phusion passenger user.
>The account that is running the Instiki service has modify rights to the
whole Insiki folder as well as the location of my Ruby installation. 
Should I have to add rights anywhere else?>
Thanks,
Joel

Joel W. Garman

2009-Jun-18 18:11 UTC

head link

[Instiki] Apache Application Error after Save

As a test I granted administrator rights to the account that is running
Instiki.  Still getting the expired fragments so don''t think its a file
access right issue with the OS.  Any other ideas?

Am I getting shunned because I''m running Instiki on a Windows box?  (I
knew I shouldn''t have listened to that little devil.)

Instiki-users <instiki-users at rubyforge.org>
writes:>can you tell us which version of apache you are using, under which os?  
>are you using phusion passenger to run instiki?
>
>to me this looks like the fragments are not writable/modifyable -- i  
>think this could be related to your instiki file access rights (or  
>user/group rights) are not the same as the phusion passenger user.
>
>-m
>
>
>On 16.06.2009, at 22:59, Joel W. Garman wrote:
>
>> I have has this same problem a couple of times.  When a user goes to  
>> save
>> a page (not all the time just some of the time), the Apache app error
>> shows up, halting the wiki.  No pages are rendered, simply the app  
>> error
>> (can''t get to HomePage or web_list or any specific pages).  To
solve
>> the
>> problem I have to delete and recreate the Instiki directory.
>>
>> Thoughts of dsnbl malfunctioning were considered but the error  
>> occurs with
>> 0.16.6
>>
>> Here is the production.log just before the crash (what are the expired
>> fragments):
>>
>> Processing WikiController#edit (for 10.5.17.24 at 2009-06-09 10:43:28)
>> [GET]
>>  Parameters: {"id"=>"HomePage",
"web"=>"circulation"}
>> Reading page ''HomePage'' from web
''circulation''
>> Page ''HomePage''  found
>> Rendering template within layouts/default
>> Rendering wiki/edit
>> Completed in 125ms (View: 78, DB: 31) | 200 OK
>> [http://libweb.biola.edu/circulation/edit/HomePage]
>>
>>
>> Processing WikiController#save (for 10.5.17.24 at 2009-06-09 10:43:37)
>> [POST]
>>  Parameters:
{"_form_key"=>"ccabfefae197829322efcfab19ff6e755714aeee",
>> "author"=>"Joel Garman",
"id"=>"HomePage", "content"=>"h2.
Welcome
>> to the
>> Circulation Manual\r\n\r\nTable of Contents",
"web"=>"circulation"}
>> Reading page ''HomePage'' from web
''circulation''
>> Page ''HomePage''  found
>> 10.5.17.24
>> Reading page ''HomePage'' from web
''circulation''
>> Page ''HomePage''  found
>> Expired fragment: views/circulation/recently_revised (0.0ms)
>> Expired fragment: views/circulation/recently_revised/S (0.0ms)
>> Expired fragment: views/circulation/recently_revised/W (0.0ms)
>> Expired fragment: views/circulation/recently_revised/I (0.0ms)
>> Expired fragment: views/circulation/recently_revised/R (0.0ms)
>> Expired fragment: views/circulation/recently_revised/S (0.0ms)
>> Expired fragment: views/circulation/recently_revised/G (0.0ms)
>> Expired fragment: views/circulation/recently_revised/R (0.0ms)
>> Expired fragment: views/circulation/recently_revised/S (0.0ms)
>> Expired fragment: views/circulation/recently_revised/A (15.0ms)
>> Expired fragment: views/circulation/recently_revised/L (0.0ms)
>> Expired fragment: views/circulation/recently_revised/C (0.0ms)
>> Expired fragment: views/circulation/recently_revised/I (0.0ms)
>> Expired fragment: views/circulation/recently_revised/D (0.0ms)
>> Expired fragment: views/circulation/recently_revised/W (0.0ms)
>> Expired fragment: views/circulation/recently_revised/R (0.0ms)
>> Expired fragment: views/circulation/recently_revised/M (0.0ms)
>> Expired fragment: views/circulation/recently_revised/M (0.0ms)
>> Expired fragment: views/circulation/recently_revised/S (0.0ms)
>> Expired fragment: views/circulation/recently_revised/P (0.0ms)
>> Expired fragment: views/circulation/recently_revised/E (0.0ms)
>> Expired fragment: views/circulation/recently_revised/E (0.0ms)
>> Expired fragment: views/circulation/recently_revised/L (16.0ms)
>> Expired fragment: views/circulation/recently_revised/A (0.0ms)
>> Expired fragment: views/circulation/recently_revised/B (0.0ms)
>> Expired fragment: views/circulation/recently_revised/B (0.0ms)
>> Expired fragment: views/circulation/recently_revised/B (0.0ms)
>> Expired fragment: views/circulation/recently_revised/P (0.0ms)
>> Expired fragment: views/circulation/recently_revised/S (0.0ms)
>> Expired fragment: views/circulation/recently_revised/B (0.0ms)
>> Expired fragment: views/circulation/recently_revised/B (0.0ms)
>> Expired fragment: views/circulation/recently_revised/L (0.0ms)
>> Expired fragment: views/circulation/recently_revised/C (0.0ms)
>> Expired fragment: views/circulation/recently_revised/C (0.0ms)
>> Expired fragment: views/circulation/recently_revised/S (0.0ms)
>> Expired fragment: views/circulation/list (0.0ms)
>> Expired fragment: views/circulation/list/S (0.0ms)
>> Expired fragment: views/circulation/list/W (0.0ms)
>> Expired fragment: views/circulation/list/I (0.0ms)
>> Expired fragment: views/circulation/list/R (0.0ms)
>> Expired fragment: views/circulation/list/S (0.0ms)
>> Expired fragment: views/circulation/list/G (0.0ms)
>> Expired fragment: views/circulation/list/R (0.0ms)
>> Expired fragment: views/circulation/list/S (0.0ms)
>> Expired fragment: views/circulation/list/A (0.0ms)
>> Expired fragment: views/circulation/list/L (0.0ms)
>> Expired fragment: views/circulation/list/C (0.0ms)
>> Expired fragment: views/circulation/list/I (0.0ms)
>> Expired fragment: views/circulation/list/D (0.0ms)
>> Expired fragment: views/circulation/list/W (15.0ms)
>> Expired fragment: views/circulation/list/R (0.0ms)
>> Expired fragment: views/circulation/list/M (0.0ms)
>> Expired fragment: views/circulation/list/M (0.0ms)
>> Expired fragment: views/circulation/list/S (0.0ms)
>> Expired fragment: views/circulation/list/P (0.0ms)
>> Expired fragment: views/circulation/list/E (0.0ms)
>> Expired fragment: views/circulation/list/E (0.0ms)
>> Expired fragment: views/circulation/list/L (0.0ms)
>> Expired fragment: views/circulation/list/A (0.0ms)
>> Expired fragment: views/circulation/list/B (0.0ms)
>> Expired fragment: views/circulation/list/B (0.0ms)
>> Expired fragment: views/circulation/list/B (0.0ms)
>> Expired fragment: views/circulation/list/P (0.0ms)
>> Expired fragment: views/circulation/list/S (0.0ms)
>> Expired fragment: views/circulation/list/B (0.0ms)
>> Expired fragment: views/circulation/list/B (0.0ms)
>> Expired fragment: views/circulation/list/L (0.0ms)
>> Expired fragment: views/circulation/list/C (0.0ms)
>> Expired fragment: views/circulation/list/C (0.0ms)
>> Expired fragment: views/circulation/list/S (0.0ms)
>>
>> _______________________________________________
>> Instiki-users mailing list
>> Instiki-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/instiki-users
>
>_______________________________________________
>Instiki-users mailing list
>Instiki-users at rubyforge.org
>http://rubyforge.org/mailman/listinfo/instiki-users


Thanks,
Joel

Joel W. Garman

2009-Jun-30 16:33 UTC

head link

[Instiki] Apache Application Error after Save

Its not reproducible 100% of the time.  Only sometimes.  The user who last
posted (original post: 6-24) has a similar problem as me.  Here is the
issue:

##################################
1. Instiki is running fine and dandy.  I am running Instiki on Windows
2008 server with MySQL and Ruby 1.8.6 one-click installer

2. Edit a page in the wiki or create a new page

3. After modifying or entering text, click Submit.

EXPECTED BEHAVIOR:
	Instiki processes the information and displays the updated page.

ACTUAL BEHAVIOR:
	Instiki displays the following error "Application error (Apache)
Something very bad just happened. I just know it. Do you smell smoke?" 
None of the pages in the wiki display.  The command window does not show
any new entries in response to the multiple page queries.  Usually the
application stops responding while displaying the list of expired
fragments (as seen in the production log and command window).  I have to
delete the existing Instiki installation and create a new one.
#################################

Instiki-users <instiki-users at rubyforge.org>
writes:>
>What is the issue?
>
>####################
>Steps to reproduce:
>1. ...
>2. ...
>3. ...
>Expected behaviour:
>   ...
>Actual behaviour:
>   ...
>####################

Joel W. Garman

2009-Jun-30 18:43 UTC

head link

[Instiki] Apache Application Error after Save

Instiki-users <instiki-users at rubyforge.org>
writes:>
>Is there really nothing that distinguishes those instances where this  
>error occurs from those where the application behaves normally?
I can''t determine anything.  If you want I can send you the
production.log
files.  I have a copy of the log the last 4 times this error has occurred.
 I can''t find a common thread.  At first I thought it was when a large
amount of text was submitted but is has occurred with one or two words
submitted.>
>
>Not just the desired (just-saved) page?
>
>None of the pages display?
>
>Even if you restart the application?
>
>When you say, "none of the pages display", what precisely happens?
Do
>you get an error message? Nothing?
Not just the desired page.  Any queried page displays the "Application
Error".  All wikis, all pages (web_list, HomePage, etc) display the
application error.>
>So what happens when you restart the application? Nothing? An error  
>message?
>Same error message occurs when the application is restarted.  The
"Application Error... Do you smell smoke?">
>>  I have to
>> delete the existing Instiki installation and create a new one.
>
>Why?
This is the only way to recover from the error.  Restarting the app
doesn''t work.>

Thanks,
Joel

Mag. Matthias Tarasiewicz

2009-Jun-30 18:47 UTC

head link

[Instiki] Apache Application Error after Save

hello joel.
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 ?

On 30.06.2009, at 20:43, Joel W. Garman wrote:
> Instiki-users <instiki-users at rubyforge.org> writes:
>>
>> Is there really nothing that distinguishes those instances where this
>> error occurs from those where the application behaves normally?
>
> I can''t determine anything.  If you want I can send you the  
> production.log
> files.  I have a copy of the log the last 4 times this error has  
> occurred.
> I can''t find a common thread.  At first I thought it was when a
large
> amount of text was submitted but is has occurred with one or two words
> submitted.
>>
>>
>> Not just the desired (just-saved) page?
>>
>> None of the pages display?
>>
>> Even if you restart the application?
>>
>> When you say, "none of the pages display", what precisely
happens? Do
>> you get an error message? Nothing?
>
> Not just the desired page.  Any queried page displays the "Application
> Error".  All wikis, all pages (web_list, HomePage, etc) display the
> application error.
>>
>> So what happens when you restart the application? Nothing? An error
>> message?
>>
> Same error message occurs when the application is restarted.  The
> "Application Error... Do you smell smoke?"
>>
>
>>> I have to
>>> delete the existing Instiki installation and create a new one.
>>
>> Why?
>
> This is the only way to recover from the error.  Restarting the app
> doesn''t work.
>>
>
>
> Thanks,
> Joel
>
> _______________________________________________
> Instiki-users mailing list
> Instiki-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/instiki-users

Joel W. Garman

2009-Jun-30 19:24 UTC

head link

[Instiki] Apache Application Error after Save

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

Joel W. Garman

2009-Jun-30 20:07 UTC

head link

[Instiki] Apache Application Error after Save

Instiki-users <instiki-users at rubyforge.org>
writes:>
>I don''t understand what reinstalling the application achieves.
>
>What files have been modified since the last installation?
>The obvious ones are "secret", the contents of the
"cache/views/"
>directory, and perhaps the contents of the "webs/" directory (if
there
>are uploaded files). Everything else should be completely unaltered.
>
>What does reinstallation achieve, that (say) clearing the cache would  
>not?
>True, these are the only files that have been modified (well, and the log
file).  In my ignorance that was the only way I knew of to recover from
the problem.  Next time the error occurs, should I simply delete the cache
files and restart the application to see if this corrects the problem?  If
it is a poisoned cache problem what might be causing this issue?

Thanks,
Joel

Joel W. Garman

2009-Jul-02 22:08 UTC

head link

[Instiki] Apache Application Error after Save

Instiki-users <instiki-users at rubyforge.org>
writes:>I wouldn''t think that a bad cache file (or two) would make every  
>single page on your wiki unreadable. On the other hand, removing cache/ 
>views/* is harmless. Similarly, deleting or moving the "log/*"
files
>should be harmless.
>
>It would seem important to track down what, exactly, is getting  
>corrupted, and preventing you from just relaunching the application. 

So I experienced my problem again today.  I had Instiki running in a
command window (still 0.16.6).  Ruby displayed no error messages.  I
deleted the cache which did not restore the wiki to functionality.  I
restored the cache folder then renamed the production.log file.  This
action restored the wiki.  Hard to believe that one damn file locks up my
whole wiki.>

Thanks,
Joel

Joel W. Garman

2009-Jul-02 23:45 UTC

head link

[Instiki] Apache Application Error after Save

Instiki-users <instiki-users at rubyforge.org> writes:
>    config.action_controller.logger = Logger.new("#{RAILS_ROOT}/log/ 
>#{RAILS_ENV}.log", 25, 1024000)
I commented this line out>
>I wonder if Windows has a problem with log rotation.
>Each time Instiki is launched is it suppose to create a new log file or
just append the existing file?

Joel W. Garman

2009-Jul-06 19:47 UTC

head link

[Instiki] Apache Application Error after Save

Instiki-users <instiki-users at rubyforge.org>
writes:>
>
>Append to the existing one.
>
>The above line is designed to rotate the active log file when it  
>reaches 1MB in size (keeping the latest 25 log files). I''m
wondering
>whether that works under Windows.
>The log rotation feature does not work in Windows.  I tested this in
Window Server 2008 and Windows XP with Instiki 0.16.6.  Should I make a
bug report?>

Thanks,
Joel

Mag. Matthias Tarasiewicz

2009-Jul-06 20:45 UTC

head link

[Instiki] Apache Application Error after Save

hi there!
yes, please file a bug at bug.to so we can take a look into that!

-m

On 06.07.2009, at 21:47, Joel W. Garman wrote:
> Instiki-users <instiki-users at rubyforge.org> writes:
>>
>>
>> Append to the existing one.
>>
>> The above line is designed to rotate the active log file when it
>> reaches 1MB in size (keeping the latest 25 log files). I''m
wondering
>> whether that works under Windows.
>>
> The log rotation feature does not work in Windows.  I tested this in
> Window Server 2008 and Windows XP with Instiki 0.16.6.  Should I  
> make a
> bug report?
>>
>
>
> Thanks,
> Joel
>
> _______________________________________________
> Instiki-users mailing list
> Instiki-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/instiki-users

Instiki users - Jun 2009 - [Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save

[Instiki] Apache Application Error after Save