nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Index Dying..

DavidMusser

Does anyone have the index server for search running on the TS server on windows? If so have you had a very large branch index properly? I have about 20 Gigs of content, and it seems to run for a long time, and then stop. No real errors... just some througout the log of files that are not to be indexed etc.

Just curious

-D

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

Find more posts tagged with

Comments

Migrateduser

While indexing any content, the index server could give out a bunch of messages in the log saying that "so-and-so file was not indexed". The problem here lies with the inherent (in)ability of the search backend (Verity) to crack and index the document. As and when, we upgrade to more recent versions of Verity, some of these problems will go away. But as new types of content keep coming up, it will always be in a catch-up mode.

I presume when you say that the index server stops, that it actually ran through the entire branch (which could take a few days based on your content size) , and completed indexing it (albeit with a few erros for specific files in the log message). If that happens, then that is reasonable. We can always go through the support channel for specific files that did not get indexed and run it by Verity. In the past, we have got responses from Verity that say something like "this has been fixed in a newer release" or "this will be looked at in an upcoming release".

Regards
--Anirudha

DavidMusser

Thanks for the response, but dying is actual death... I left it run for several days and it usually stops indexing (according to the last couldn't index that file message) about 15 hrs into it.

When I go to stop the index server service I get a message couldn't stop service already stoped... I'll get error code in the a.m.

Eventhough it gets this error on the service stop I can use the iwndx commands, but the branch always has status of 12...

I've pulled out 4 GIGS of content to see if it's something in the PDF's or DOCs that's causing the issue.

I'll let you know in the a.m. if it completes...

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

Migrateduser

If index server actually dies that is typically bad news. It is possible that some file messed up the index server so badly that it could not recover from it. If you do get the offending file or a set of files (one of which is the offending file), then you should report that as a support case and we will follow up with Verity.

Another thought is to change iw.index.maxbifsize property in the search.properties configuration file to a low number like 100 and re-run the index server and see if that works. There is some problem with Verity in that a large set of files submitted at a time in rare cases causes a problem.

Regards
--Anirudha

DavidMusser

It indexed everything except the doc, pdf, and graphics directories, so I've changed the bif size and am now testing again after adding the doc directory back... wish me luck :-)

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01