I used api to search articles but it occured exception as missing index.
Exception Detail:
System.IO.FileNotFoundException: no segments* file found in Lucene.Net.Store.SimpleFSDirectory \App_Data\TEMP\ExamineIndexes\InternalArticle\Index lockFactory=Lucene.Net.Store.NativeFSLockFactory: files: write.lock _3y.fdt _3y.fdx _3y.frq _3y.nrm _3y.prx _3y.tis _3y.tvd _3y.tvf _3y.tvx _3z.cfs _40.cfs _41.cfs
at Lucene.Net.Index.SegmentInfos.FindSegmentsFile.Run(IndexCommit commit)
at Lucene.Net.Index.SegmentInfos.Read(Directory directory)
at Lucene.Net.Index.DirectoryReader.IsCurrent()
at Examine.LuceneEngine.LuceneExtensions.GetReaderStatus(IndexReader reader)
at Examine.LuceneEngine.Providers.LuceneSearcher.ValidateSearcher(Boolean forceReopen)
at UmbracoExamine.UmbracoExamineSearcher.GetSearchFields()
at UmbracoExamine.UmbracoExamineSearcher.CreateSearchCriteria(String type, BooleanOperation defaultOperation)
I remove examine folder, rebuilt, restart IIS and it work fine. But this exception occurs and it make my server is down frequently. Anyone can help me for a solution.
Not sure I can provide you with the concrete solution but I think it would be nice if you can tell us a bit more about your Umbraco solution.
What version of Umbraco are you seeing this on? Have you done some custom stuff that does anything with the examine indexes or is it just vanilla Umbraco? No extension of backoffice functionality using the Umbraco API? What 3rd party packages are you using? Is it happening locally or only in production or both places?
I use umbraco 7.2.2 and this bug was occured in my production three months ago (I built project above one year).
Currently, I search on my website which throw an exception "System.IO.FileNotFoundException: no segments* file found in Lucene.Net.Store.SimpleFSDirectory" in log file. I don't use third party and just use basic umbraco. It also relates this post
Missing index when use lucene search
Hi,
I used api to search articles but it occured exception as missing index.
Exception Detail:
System.IO.FileNotFoundException: no segments* file found in Lucene.Net.Store.SimpleFSDirectory \App_Data\TEMP\ExamineIndexes\InternalArticle\Index lockFactory=Lucene.Net.Store.NativeFSLockFactory: files: write.lock _3y.fdt _3y.fdx _3y.frq _3y.nrm _3y.prx _3y.tis _3y.tvd _3y.tvf _3y.tvx _3z.cfs _40.cfs _41.cfs
at Lucene.Net.Index.SegmentInfos.FindSegmentsFile.Run(IndexCommit commit)
at Lucene.Net.Index.SegmentInfos.Read(Directory directory)
at Lucene.Net.Index.DirectoryReader.IsCurrent()
at Examine.LuceneEngine.LuceneExtensions.GetReaderStatus(IndexReader reader)
at Examine.LuceneEngine.Providers.LuceneSearcher.ValidateSearcher(Boolean forceReopen)
at UmbracoExamine.UmbracoExamineSearcher.GetSearchFields()
at UmbracoExamine.UmbracoExamineSearcher.CreateSearchCriteria(String type, BooleanOperation defaultOperation)
I remove examine folder, rebuilt, restart IIS and it work fine. But this exception occurs and it make my server is down frequently. Anyone can help me for a solution.
Thanks.
Hi Tam
Not sure I can provide you with the concrete solution but I think it would be nice if you can tell us a bit more about your Umbraco solution.
What version of Umbraco are you seeing this on? Have you done some custom stuff that does anything with the examine indexes or is it just vanilla Umbraco? No extension of backoffice functionality using the Umbraco API? What 3rd party packages are you using? Is it happening locally or only in production or both places?
/Jan
Hi Jan
I use umbraco 7.2.2 and this bug was occured in my production three months ago (I built project above one year).
Currently, I search on my website which throw an exception "System.IO.FileNotFoundException: no segments* file found in Lucene.Net.Store.SimpleFSDirectory" in log file. I don't use third party and just use basic umbraco. It also relates this post
https://our.umbraco.org/forum/developers/extending-umbraco/27569-Examine-not-indexing-at-all
My solutions are:
+ Removing Examine Index folder in App_Data
+ Restarting IIS again and waiting for a few minutes.
My Site was worked again but it can occur more. I don't see this exception at local, I think local is not enough to show this exception.
Tam,
When not go to developer section and rebuild the index from there?
Regards
Ismail
Ismail Mayat,
This can not do because developer section is not shown information of index, you can see my image as below.
click on indexers, or is that not working? if not working then chrome f12 and see if you are getting any console errors.
Regards
Ismail
@Ismail Mayat,
I also debug on chrome F12 and my console just show information.
It is difficulty to debug it.
is working on a reply...