We've recently started having this issue where the member index gets corrupted and we cannot search in the member section. Really annoying and we cannot figure out whats causing it. Anyone else seeing this?
eg:
Lucene.Net.Index.CorruptIndexException: invalid deletion count: 2 vs docCount=1 (resource: BufferedChecksumIndexInput(MMapIndexInput(path="C:\home\site\wwwroot\umbraco\Data\TEMP\ExamineIndexes\ExternalIndex\segments_ge")))
And we get this error in the backoffice in the browser console.
umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:147 Error: [ngRepeat:dupes] http://errors.angularjs.org/1.8.3/ngRepeat/dupes?p0=indexer%20in%20vm.indexerDetails&p1=string%3A%0D&p2=%0D
at umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:25:168
at umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:349:428
at umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:170:223
at m.$digest (umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:171:351)
at m.$apply (umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:174:484)
at k (umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:125:445)
at v (umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:131:40)
at y.onload (umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:131:464)
Just looking at your first error, but that seems to indicate a problem with the ExternalIndex rather than the Member one, so I'm wondering if the problem is there and that in turn is stopping your Member index from building successfully?
I'd probably try rebuilding the external index and if that's successful, then the member index and see if that generates member index files, are you getting any files at all for the member index? If you're still having problems then you could try deleting the index folder completely and restarting the web app as that should rebuild everything from scratch and should clear out any pesky corrupted files. Other things you could check for are disk space and if you have any custom code that's hooking into the indexing that might be causing an issue? Have you added an extra custom properties recently that could be causing an issue?
Yes I think there is/was an issue with the external index which was having a knock effect. Deleting all the examine indexes and restarting fixed the problem.
corrupted member examine index
Hi
umbraco v12.3.7 Azure webapp
We've recently started having this issue where the member index gets corrupted and we cannot search in the member section. Really annoying and we cannot figure out whats causing it. Anyone else seeing this?
eg:
And we get this error in the backoffice in the browser console.
umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:147 Error: [ngRepeat:dupes] http://errors.angularjs.org/1.8.3/ngRepeat/dupes?p0=indexer%20in%20vm.indexerDetails&p1=string%3A%0D&p2=%0D at umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:25:168 at umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:349:428 at umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:170:223 at m.$digest (umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:171:351) at m.$apply (umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:174:484) at k (umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:125:445) at v (umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:131:40) at y.onload (umbraco-backoffice-js.js.v3820ba0df2426ec64b6d83605de8183ed4d59af6:131:464)
I've deleted all the index files, restarted the webapp (a few times), its rebuilt the index but still getting errors and cannot search in members.
and its looking for the wrong index files.
System.IO.FileNotFoundException: Could not find file 'C:\home\site\wwwroot\umbraco\Data\TEMP\ExamineIndexes\MembersIndex_1k.si'.
_1k.si doesn't exist in the member index folder.
Just looking at your first error, but that seems to indicate a problem with the ExternalIndex rather than the Member one, so I'm wondering if the problem is there and that in turn is stopping your Member index from building successfully?
I'd probably try rebuilding the external index and if that's successful, then the member index and see if that generates member index files, are you getting any files at all for the member index? If you're still having problems then you could try deleting the index folder completely and restarting the web app as that should rebuild everything from scratch and should clear out any pesky corrupted files. Other things you could check for are disk space and if you have any custom code that's hooking into the indexing that might be causing an issue? Have you added an extra custom properties recently that could be causing an issue?
Hi
Yes there are index files in the MembersIndex folder. I will try and delete all the indexes rather than just the members
Yes I think there is/was an issue with the external index which was having a knock effect. Deleting all the examine indexes and restarting fixed the problem.
Good to hear! If you can mark that as the answer, that would be great.
Its actually a much bigger issue, https://github.com/umbraco/Umbraco-CMS/issues/16163
Clearing the indexes is a quick fix but there is underlying issue as its reoccuring.
is working on a reply...