[Building Sakai] Search warnings

[Sean Keesler]

This instance runs and runs...no shutdowns here...and otherwise it behaves
as expected...just an annoying warning I want to get rid of. I have data in
there that I don't want to blow away with a fresh db...but I don't care if I
blow away search indices. WHat is the right procedure to do just that?

Sean Keesler
130 Academy Street
Manlius, NY 13104
315-663-7756



On Mon, Jul 20, 2009 at 9:44 AM, Matthew Jones <jonespm at umich.edu> wrote:

> I was having similar looking errors in my 2.5 QA server a few weeks
> ago that I was never able to fully resolve. I was tracking this SAK
> (http://jira.sakaiproject.org/browse/SAK-13127), one that made the cut
> into 2.6.0 even though it isn't marked as such. The workarounds on it
> "remove the indexwork directories on each restart" seem to make the
> error go away, and theres also the patch on the SAK. However  for some
> reason even if I did that my server started to automatically shutdown
> within a short time for no apparent reason. That might not have been
> related to search or removing that directory, but I don't know.
>
> Everything would start up and run great, then I'd log off and
> everything after a random (usually short ~30 minute period)
> INFO: Local Merge Operation
>  (2009-07-09 12:15:34,127
> Timer-1_org.sakaiproject.search.journal.impl.MergeUpda
> teOperation)
> INFO: Pausing Coyote HTTP/1.1 on http-8080 (2009-07-09 12:16:45,211
> Thread-40_or
> g.apache.coyote.http11.Http11BaseProtocol)
> INFO: Stopping service Catalina (2009-07-09 12:16:46,212
> Thread-40_org.apache.ca
> talina.core.StandardService)
>
> What I probably should have done looking back was try to drop all of
> the search_ tables, delete all of the search directories and recreate
> them fresh. What I did instead (since this was just a QA server) was
> to drop everything and start fresh to save time because I didn't see
> any jiras about that tomcat issue. ;) That does seem a little extreme
> though.
>
> I haven't seen these happen on the 2.6 QA yet, which is good news.
>
> -Matthew
>
> On Mon, Jul 20, 2009 at 9:07 AM, Sean Keesler<sean at keesler.org> wrote:
> > I am seeing a warning every couple of minutes from the search tool.
> > It is seeing that the searchjournal file "1.zip" doesn't exist. I can
> > confirm that it doesn't.
> > What is the right way to kick Sakai and reset its search back end?
> >
> > INFO: Local Merge Operation
> >  (2009-06-26 18:53:40,478
> > Timer-3_org.sakaiproject.search.journal.impl.MergeUpdateOperation)
> > WARN: Failed to compete merge of 1 (2009-06-26 18:55:20,481
> > Timer-3_org.sakaiproject.search.journal.impl.MergeUpdateOperation)
> > org.sakaiproject.search.transaction.api.IndexTransactionException: Failed
> to
> > delete documents
> >         at
> >
> org.sakaiproject.search.journal.impl.JournaledFSIndexStorageUpdateTransactionListener.prepare(JournaledFSIndexStorageUpdateTransactionListener.java:161)
> >         at
> >
> org.sakaiproject.search.transaction.impl.IndexTransactionImpl.firePrepare(IndexTransactionImpl.java:312)
> >         at
> >
> org.sakaiproject.search.transaction.impl.IndexTransactionImpl.prepare(IndexTransactionImpl.java:146)
> >         at
> >
> org.sakaiproject.search.journal.impl.MergeUpdateOperation.runOnce(MergeUpdateOperation.java:94)
> >         at
> >
> org.sakaiproject.search.journal.impl.IndexManagementTimerTask.run(IndexManagementTimerTask.java:135)
> >         at java.util.TimerThread.mainLoop(Timer.java:512)
> >         at java.util.TimerThread.run(Timer.java:462)
> > Caused by: java.io.FileNotFoundException:
> > /vol2/rsmart_clev2.5.5/files/searchjournal/searchjournal/1.zip (No such
> file
> > or directory)
> >         at java.io.FileInputStream.open(Native Method)
> >         at java.io.FileInputStream.<init>(FileInputStream.java:106)
> >         at
> >
> org.sakaiproject.search.journal.impl.SharedFilesystemJournalStorage.retrieveSavePoint(SharedFilesystemJournalStorage.java:160)
> >         at
> >
> org.sakaiproject.search.journal.impl.JournaledFSIndexStorageUpdateTransactionListener.prepare(JournaledFSIndexStorageUpdateTransactionListener.java:114)
> >         ... 6 more
> > WARN: Failed to start merge operation  (2009-06-26 18:55:20,482
> > Timer-3_org.sakaiproject.search.journal.impl.MergeUpdateOperation)
> > org.sakaiproject.search.journal.api.JournalErrorException: Journal is
> > stalled at ID 1
> >         at
> >
> org.sakaiproject.search.journal.impl.JournaledFSIndexStorageUpdateTransactionListener.open(JournaledFSIndexStorageUpdateTransactionListener.java:88)
> >         at
> >
> org.sakaiproject.search.transaction.impl.IndexTransactionImpl.fireOpen(IndexTransactionImpl.java:359)
> >         at
> >
> org.sakaiproject.search.transaction.impl.IndexTransactionImpl.open(IndexTransactionImpl.java:75)
> >         at
> >
> org.sakaiproject.search.journal.impl.MergeUpdateManager.openTransaction(MergeUpdateManager.java:48)
> >         at
> >
> org.sakaiproject.search.journal.impl.MergeUpdateOperation.runOnce(MergeUpdateOperation.java:92)
> >         at
> >
> org.sakaiproject.search.journal.impl.IndexManagementTimerTask.run(IndexManagementTimerTask.java:135)
> >         at java.util.TimerThread.mainLoop(Timer.java:512)
> >         at java.util.TimerThread.run(Timer.java:462)
> >
> > Sean Keesler
> > 130 Academy Street
> > Manlius, NY 13104
> > 315-663-7756
> >
> >
> >
> > _______________________________________________
> > sakai-dev mailing list
> > sakai-dev at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> > with a subject of "unsubscribe"
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090720/1ecbb07f/attachment.html