Stopping index server on Linux?

I'm working with TS 7.2.1 and Search on Linux (separate servers) - and I'm trying to tweak the customizations for search (FieldMapping.xml on Search side and search_custom.xml on TS side).

The instructions in the manuals indicate that you should stop and restart the index and search services - so I do:

% sudo /etc/init.d/iw.tsindex stop
... wait a couple of seconds ...
% sudo /etc/init.d/iw.tssearch stop
... wait a second ...

I then notice that the iw.tsindex.log is still growing - and has been for several minutes (nearly 10 right now) since after I tried to stop the index service.

And if I try to issue the command (/etc/init.d/iw.tsindex stop) again - I get an error from iwndxmgrstop - which tells me to look at it's log file - which says I need to make sure the search and index server are running!

So - am I supposed to restart the search and index services (not sure if I can right now) and then run indexmgrstop and then stop and restart the search and index services again???

Or should I just get someone with 'root' privileges to kill off the index server process so I can start it all over again (I'd much rather do it "gracefully")

Any one with this specific experience have any advice?

Find more posts tagged with

Comments

nipper

That is all I have ever done though I usually stop search first.

nipper

I just did that from my VM. Stopped index with your command, tail -f did not show any activity.

What log were you looking at and can you do a tail -f on it ?

OK, I do see activity on iw.tsindex.stdout maybe that is what you are seeing. I think that is IDOL.

Adam Stoller

That is all I have ever done though I usually stop search first.

Hmm - it's been over an hour since I tried to stop the index service gracefully - and it's still running - I guess I'll have to find someone with root abilities to kill the **** thing (*sigh*) - the last hidden edition it processed was #252891, and I know that the latest hidden edition on that branch is around #272572 - that's like another 20,000 submit operations to process; although to be fair, I can see that sometimes it processes a whole bunch in less than a second - so it probably depends on the amount of files changed during the submit (which makes sense) - but it's been chewing on 252891 for about 15 minutes now....

nipper

So if you do a ps -ef | grep index

Do you see it ? it is pretty obvious, kicked off by a Java command.

Adam Stoller

So if you do a ps -ef | grep index

Do you see it ? it is pretty obvious, kicked off by a Java command.

Yeah - I know about that - and it was there.
After over an hour had elapsed since running /etc/init.d/iw.tsindex stop, we decided to just kill the process and restart both the search and index services again. Not exactly the way I wanted to do things - especially since I really wanted to purge the branch in question first to force it to reindex everything based on changed made in the FieldMapping.xml file - but, I figure with 20000 unnamed editions to process, there will be enough done to verify what we wanted (this is their DEV system).

Hopefully sometime tomorrow I'll be able to verify if the changes I made in both FieldMapping.xml and search_custom.xml actually work (sigh).

Migrateduser

I am late to the party (as usual) but I have had to stop a rogue hunter_index process several times because the indexer doesn't stop gracefully. We've received more than one patch for the hunter*.jar files on our Linux server as well, for various issues with Search/Indexing. Search is killing me right now with a problem IW can't seem to patch for me (the thread I started with the NOT logic nonsense).

Luckily for me, we have sudo rights for the iwts user so we can kill our own processes on the Search box.

Adam Stoller

I am late to the party (as usual) but I have had to stop a rogue hunter_index process several times because the indexer doesn't stop gracefully. We've received more than one patch for the hunter*.jar files on our Linux server as well, for various issues with Search/Indexing. Search is killing me right now with a problem IW can't seem to patch for me (the thread I started with the NOT logic nonsense).

Luckily for me, we have sudo rights for the iwts user so we can kill our own processes on the Search box.

Well - the good news (for me) is that the indexer actually finished sometime overnight - and at least some of the custom search directives I added through custom_search.xml and FieldMapping.xml seem to work (integers and dates seem to work reasonably well, strings seem to be hit-or-miss as to whether or not they match what they should, match nothing, or match too much, or result in an UNKNOWN_SEARCH_FAILURE)

The bad news (for me) is that I had to make some changed to the FieldMapping.xml yesterday, and since the indexer picked up where it had left off before - a lot of the data is probably not correctly indexed - so I need to purge the branch from the indexer and re-do it... however, since this is a DEV system, I'm planning to probably delete a bunch of the older editions first -- perhaps migrate only the last edition to a new store and swap it in...

More fun ...

Adam Stoller

Anyone know how to forcibly purge a branch from TeamSite Search 7.2.1 (on Linux)?

I tried running iwndxpurgebr vpath but I get back an error:[indent]Failure. Error: 10002. Detail: The collection for branch vpath could not be purged.[/indent]The branch is fully indexed and unfrozen (as shown with iwndxstatus -a -f) yet it won't let me purge it.

I'm not sure if it matters, but it's the only branch being indexed.

nipper

The Admin manual lists that error and says to use iwndxrmbr instead

Adam Stoller

The Admin manual lists that error and says to use iwndxrmbr instead

That would be really helpful - if such a CLT existed!

I see:

But no iwndxrmbr.Anyone else with a 7.x version of search installed able to find that CLT?

nipper

My bad, I searched for 10002 on the support site and it brought up that in the 6.7.2 docs.

Adam Stoller

My bad, I searched for 10002 on the support site and it brought up that in the 6.7.2 docs.

Chances are it's the same error condition, but they neglected to provide the CLT for working around it (sigh) :-)

Adam Stoller

Anyone know how to forcibly purge a branch from TeamSite Search 7.2.1 (on Linux)?

I tried running iwndxpurgebr vpath but I get back an error:[indent]Failure. Error: 10002. Detail: The collection for branch vpath could not be purged.[/indent]The branch is fully indexed and unfrozen (as shown with iwndxstatus -a -f) yet it won't let me purge it.

I'm not sure if it matters, but it's the only branch being indexed.

FYI - apparently I missed the part in the manual that says the branch should be frozen (iwndxfreezebr) and/or the index [and search?] services stopped before you run iwndxpurgebr.

Unfortunately, having tried to delete a bunch of old editions in preparation for re-indexing, I neglected to stop the indexer then and everything is in a weird state right now (TS is still cleaning up old [unnamed] editions from between the [named] editions I deleted yesterday; index has generated tons of data on the disk and is back to not shutting down quickly / gracefully)

I'm expecting to be in contact with Support sometime this afternoon - hopefully I'll be able to get this resolved (potentially by "force") before the EOD tomorrow...

Migrateduser

We upgraded to 7.3.2 TeamSite and Search yesterday (on Linux) to try to get Search working in general. The upgrade (from 7.3.1) went pretty quickly.

They changed iw.tsindex to now be named iw.tsconnector.

The first thing I'm trying to do is remove a branch's indexing and am running into the 10002. I froze the branch and turned off the indexer (connector) and the Search process. Still a 10002.

I'm going to move onto indexing another branch and see how that goes!

Adam Stoller

I don't remember all the details of that case - but assuming I found the right one when I looked - it came down to this:[indent]The steps to clear everything out of the index as if it's never been run are below:
1. Stop search, index, and idol services
2. Backup the branches.db and branches.db.bak files in the search-home/etc directory
3. Delete or remove the original branches.db and branches.db.bak files from the /etc directory
4. Start the idol, index, and search services
5. Run iwndxstatus -a to see the status of the indexer on the branches listed in branches.cfg, or look into the index log file to see if the indexer is working properly.[/indent]Not sure if that helps, but that's all I can find (sorry, I'm usually better at following up my threads with resolutions, but it's been almost a year now and I just cannot remember)
Keep in mind, the above was for 7.2.1....

sheikh1

Did you tried this? http://servername:IndexPort/DREINITIAL - this will purge all branches. If I remember correctly when I ran last time the response code was -1 and indexer started indexing content again. Remeber after this you should also run the steps mentioned by Ghoti in the previous psot

The IndexPort by default should be 9001, so if this wasn't changed during install that should be ok.

Migrateduser

I had the server bounced and was able to then purge the branch. Thanks!