From joel.w.garman at biola.edu Tue Jun 16 16:59:25 2009 From: joel.w.garman at biola.edu (Joel W. Garman) Date: Tue, 16 Jun 2009 13:59:25 -0700 Subject: [Instiki] Apache Application Error after Save Message-ID: 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) From parasew at 5uper.net Wed Jun 17 05:52:59 2009 From: parasew at 5uper.net (Mag. Matthias Tarasiewicz) Date: Wed, 17 Jun 2009 11:52:59 +0200 Subject: [Instiki] Apache Application Error after Save In-Reply-To: References: Message-ID: <57C0E44E-5E6F-4233-9990-A43C02CFF596@5uper.net> 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 From joel.w.garman at biola.edu Wed Jun 17 15:03:41 2009 From: joel.w.garman at biola.edu (Joel W. Garman) Date: Wed, 17 Jun 2009 12:03:41 -0700 Subject: [Instiki] Apache Application Error after Save In-Reply-To: <57C0E44E-5E6F-4233-9990-A43C02CFF596@5uper.net> References: <57C0E44E-5E6F-4233-9990-A43C02CFF596@5uper.net> Message-ID: Instiki-users 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 From joel.w.garman at biola.edu Thu Jun 18 14:11:36 2009 From: joel.w.garman at biola.edu (Joel W. Garman) Date: Thu, 18 Jun 2009 11:11:36 -0700 Subject: [Instiki] Apache Application Error after Save In-Reply-To: <57C0E44E-5E6F-4233-9990-A43C02CFF596@5uper.net> References: <57C0E44E-5E6F-4233-9990-A43C02CFF596@5uper.net> Message-ID: 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 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 From parasew at 5uper.net Tue Jun 23 11:36:16 2009 From: parasew at 5uper.net (Mag. Matthias Tarasiewicz) Date: Tue, 23 Jun 2009 17:36:16 +0200 Subject: [Instiki] Instiki 0.17 released Message-ID: <9F27ED5A-966B-477F-8E5C-F3CD0E346254@5uper.net> for those of you that don't already know: instiki 0.17 is the latest instiki version out there! http://rubyforge.org/frs/?group_id=186&release_id=35703 CHANGELOG New features: * Ability to rename pages * Ability to redirect Wikilinks, using [[!redirect ...]] * HTTP 302 redirects, for redirected/renamed pages Bugs Fixed: * Rails gets very unhappy with "." in page or author names. Make sure that doesn't happen. * Fix a Maruku escaping bug. * WEBrick should respond to TERM signals (needed by MacOSX and, perhaps, others). * Add a flash message for redirection to "new" page when the target of "show" action is not found. * Flash[:info] messages use Web's colour scheme. * Uploaded files in published webs should be accessible From shadowcat0 at comcast.net Wed Jun 24 18:25:32 2009 From: shadowcat0 at comcast.net (shadowcat0 at comcast.net) Date: Wed, 24 Jun 2009 22:25:32 +0000 (UTC) Subject: [Instiki] Application Error In-Reply-To: <323966661.6969091245881943137.JavaMail.root@sz0048a.emeryville.ca.mail.comcast.net> Message-ID: <376589817.6971081245882332416.JavaMail.root@sz0048a.emeryville.ca.mail.comcast.net> Hey, I'm real new to all this, and really still just trying to figure it out. Anyway my question is this: Everything was going fine, then the other day while trying to submit a page I got the following error : Application error (Apache) Something very bad just happened. I just know it. Do you smell smoke? the application itself crashes with the following message : The DL driver for sqlite3-ruby is deprecated and will be removed in a future release. Please update your installation to use the Native driver. I'm running ruby 186-27 rc2 with instiki 0.16.6 on windows XP. Anyone have any ideas how to fix this? -------------- next part -------------- An HTML attachment was scrubbed... URL: From parasew at 5uper.net Thu Jun 25 07:16:09 2009 From: parasew at 5uper.net (Mag. Matthias Tarasiewicz) Date: Thu, 25 Jun 2009 13:16:09 +0200 Subject: [Instiki] Application Error In-Reply-To: <376589817.6971081245882332416.JavaMail.root@sz0048a.emeryville.ca.mail.comcast.net> References: <376589817.6971081245882332416.JavaMail.root@sz0048a.emeryville.ca.mail.comcast.net> Message-ID: <7140A182-4077-4081-9323-9692DB091B7F@5uper.net> hi there, this looks like an issue of the ruby-one-click installer for windows; please can you try to update your ruby installation and see if the error still exists? -m On 25.06.2009, at 00:25, shadowcat0 at comcast.net wrote: > Hey, > > I'm real new to all this, and really still just trying to figure it > out. Anyway my question is this: > > Everything was going fine, then the other day while trying to > submit a page I got the following error : > > Application error (Apache) > Something very bad just happened. I just know it. Do you smell smoke? > > the application itself crashes with the following message : > > The DL driver for sqlite3-ruby is deprecated and will be removed > in a future release. Please update your installation to use the > Native driver. > > I'm running ruby 186-27 rc2 with instiki 0.16.6 on windows XP. > > Anyone have any ideas how to fix this? > > > > > _______________________________________________ > Instiki-users mailing list > Instiki-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/instiki-users From shadowcat0 at comcast.net Thu Jun 25 20:34:16 2009 From: shadowcat0 at comcast.net (shadowcat0 at comcast.net) Date: Fri, 26 Jun 2009 00:34:16 +0000 (UTC) Subject: [Instiki] Application Error Message-ID: <674208995.7376271245976456740.JavaMail.root@sz0048a.emeryville.ca.mail.comcast.net> No Joy. Things moved from bad to worse. now when I run instiki.cmd I get is... 'ruby.exe' is not recognized as an internal or external command, operable program or batch file. -------------- next part -------------- An HTML attachment was scrubbed... URL: From parasew at 5uper.net Fri Jun 26 04:48:43 2009 From: parasew at 5uper.net (Mag. Matthias Tarasiewicz) Date: Fri, 26 Jun 2009 10:48:43 +0200 Subject: [Instiki] Application Error In-Reply-To: <674208995.7376271245976456740.JavaMail.root@sz0048a.emeryville.ca.mail.comcast.net> References: <674208995.7376271245976456740.JavaMail.root@sz0048a.emeryville.ca.mail.comcast.net> Message-ID: <689EF073-6952-4A44-8842-691F44799F4E@5uper.net> so did you already try to update your ruby? get: http://rubyforge.org/projects/rubyinstaller/ On 26.06.2009, at 02:34, shadowcat0 at comcast.net wrote: > No Joy. > > Things moved from bad to worse. > > now when I run instiki.cmd I get is... 'ruby.exe' is not recognized > as an internal or external command, operable program or batch file. > > > _______________________________________________ > Instiki-users mailing list > Instiki-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/instiki-users From shadowcat0 at comcast.net Fri Jun 26 16:28:14 2009 From: shadowcat0 at comcast.net (shadowcat0 at comcast.net) Date: Fri, 26 Jun 2009 20:28:14 +0000 (UTC) Subject: [Instiki] Application error Message-ID: <1627050956.148301246048094541.JavaMail.root@sz0048a.emeryville.ca.mail.comcast.net> Sorry, I left that pat out. Yes, I went and downloaded the current installer, and ran that. That's when I started getting the message that ruby.exe was invalid. I then reinstalled the version I had previously downloaded, and got my original error again. Finally, I tried downloading the latest installer once more, loaded that, and was back to the ruby.exe is not a recognized... -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.w.garman at biola.edu Tue Jun 30 12:33:23 2009 From: joel.w.garman at biola.edu (Joel W. Garman) Date: Tue, 30 Jun 2009 09:33:23 -0700 Subject: [Instiki] Apache Application Error after Save In-Reply-To: <150C96B7-5166-4DE9-BD74-70118055420C@golem.ph.utexas.edu> References: < > <57C0E44E-5E6F-4233-9990-A43C02CFF596@5uper.net> < > <150C96B7-5166-4DE9-BD74-70118055420C@golem.ph.utexas.edu> Message-ID: 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 writes: > >What is the issue? > >#################### >Steps to reproduce: >1. ... >2. ... >3. ... >Expected behaviour: > ... >Actual behaviour: > ... >#################### From joel.w.garman at biola.edu Tue Jun 30 14:43:33 2009 From: joel.w.garman at biola.edu (Joel W. Garman) Date: Tue, 30 Jun 2009 11:43:33 -0700 Subject: [Instiki] Apache Application Error after Save In-Reply-To: References: < > < > <57C0E44E-5E6F-4233-9990-A43C02CFF596@5uper.net> < > < > < > <150C96B7-5166-4DE9-BD74-70118055420C@golem.ph.utexas.edu> < > Message-ID: Instiki-users 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 From parasew at 5uper.net Tue Jun 30 14:47:27 2009 From: parasew at 5uper.net (Mag. Matthias Tarasiewicz) Date: Tue, 30 Jun 2009 20:47:27 +0200 Subject: [Instiki] Apache Application Error after Save In-Reply-To: References: < > < > <57C0E44E-5E6F-4233-9990-A43C02CFF596@5uper.net> < > < > < > <150C96B7-5166-4DE9-BD74-70118055420C@golem.ph.utexas.edu> < > Message-ID: <39572162-5F6A-454F-8110-A30A04B5E68A@5uper.net> 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 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 From joel.w.garman at biola.edu Tue Jun 30 15:24:56 2009 From: joel.w.garman at biola.edu (Joel W. Garman) Date: Tue, 30 Jun 2009 12:24:56 -0700 Subject: [Instiki] Apache Application Error after Save In-Reply-To: <19047CB1-D77E-4CD2-9F8B-BCCA64FBA687@golem.ph.utexas.edu> References: < > < > < > <57C0E44E-5E6F-4233-9990-A43C02CFF596@5uper.net> < > < > < > < > < > <150C96B7-5166-4DE9-BD74-70118055420C@golem.ph.utexas.edu> < > < > < > < > <19047CB1-D77E-4CD2-9F8B-BCCA64FBA687@golem.ph.utexas.edu> Message-ID: Instiki-users 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 From joel.w.garman at biola.edu Tue Jun 30 16:07:49 2009 From: joel.w.garman at biola.edu (Joel W. Garman) Date: Tue, 30 Jun 2009 13:07:49 -0700 Subject: [Instiki] Apache Application Error after Save In-Reply-To: References: < > < > < > < > <57C0E44E-5E6F-4233-9990-A43C02CFF596@5uper.net> < > < > < > < > < > < > < > < > <150C96B7-5166-4DE9-BD74-70118055420C@golem.ph.utexas.edu> < > < > < > < > < > < > < > < > <19047CB1-D77E-4CD2-9F8B-BCCA64FBA687@golem.ph.utexas.edu> < > Message-ID: Instiki-users 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 From shadowcat0 at comcast.net Tue Jun 30 17:10:30 2009 From: shadowcat0 at comcast.net (shadowcat0 at comcast.net) Date: Tue, 30 Jun 2009 21:10:30 +0000 (UTC) Subject: [Instiki] Application Error Message-ID: <399237976.862631246396230629.JavaMail.root@sz0048a.emeryville.ca.mail.comcast.net> Thanks for all of the help, I've gotten it working. I finally had to shift to instiki 0.17.0 as well as reinstall ruby, but it's working now. -------------- next part -------------- An HTML attachment was scrubbed... URL: