Lock obtain timed out - Search indexing problem

This is an open forum for any mojoPortal topics that don't fall into the other categories.

This thread is closed to new posts. You must sign in to post in the forums.

9/26/2013 2:10:05 AM

Sandy@HH

Total Posts 53

View Posts

Lock obtain timed out - Search indexing problem

I am currently getting the following errors in my System Log:

2013-09-26 14:56:58,245 ERROR (null) - (null) - (null) - mojoPortal.SearchIndex.IndexWriterTask - Lucene.Net.Store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@C:\inetpub\wwwroot\MojoPortal\Data\Sites\1\index\write.lock
   at Lucene.Net.Store.Lock.Obtain(Int64 lockWaitTimeout)
   at Lucene.Net.Index.DirectoryReader.AcquireWriteLock()
   at Lucene.Net.Index.IndexReader.DeleteDocument(Int32 docNum)
   at Lucene.Net.Index.IndexReader.DeleteDocuments(Term term)
   at mojoPortal.SearchIndex.IndexWriterTask.ProcessQueue(DataTable q, Int32 siteId, String indexPath)

When I check my Index folder and its contents, I see the majority of files have not updated since 11.30am. I have tried removing these files and rebuilding the index, but I get "no results".

The only thing I think I changed this morning was the setting to "Allow users to Choose Editor Preference". We needed to use TinyMCE editor to enable us to insert a hyperlink with a target <popup window>. This generates the javascript in the HTML:

onclick="window.open(this.href, '', 'resizable=no,status=no,location=no,toolbar=no,menubar=no,fullscreen=no,scrollbars=yes,dependent=no,width=800,height=500'); return false;

Could this have broken anything?

I have restarted IIS to no avail. Please help!

Thanks
Sandy

9/26/2013 11:27:26 AM

Joe Audette

Total Posts 18439

View Posts

Re: Lock obtain timed out - Search indexing problem

Rebuilding the search index can take a while and if you recycle the app pool while it is working you are killing the process that is working on rebuilding the search index. once you kill it it will not start back up on its own, you have to rebuild it again. Be very patient, don't touch web.config or recycle it while it is rebuilding the index.