Index Server Port 6715 doesn't come up

HI,

we are using TS 7.3.2 Windows server 2008 R2 64 Bit. For Somehow when we Restarted the TS server , on the Idol SErver the Index Port is not Available. We try restarting all the service in the order they require but still not luck. Keeo getting the following error when I try to run iwndxstatus -a

[15 Oct 2014 22:21:45,117] DEBUG com.interwoven.hunter.search.SearchServer (Thread-14) - The search manager is unable to contact the index manager.
com.interwoven.hunter.search.SearchingException
	at com.interwoven.hunter.search.BranchMapping.reload(BranchMapping.java:130)
	at com.interwoven.hunter.search.BranchMapping.getInstance(BranchMapping.java:195)
	at com.interwoven.hunter.search.commands.GetIndexStatusByVpathCommand.execute(GetIndexStatusByVpathCommand.java:65)
	at com.interwoven.hunter.search.SearchWorker.run(SearchWorker.java:88)
	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
	at java.lang.Thread.run(Thread.java:619)
[15 Oct 2014 22:21:45,118] DEBUG com.interwoven.hunter.search.SearchWorker (Thread-14) - is_get_index_status_vpath@7 was processed successfully :true
[15 Oct 2014 22:21:45,118] DEBUG com.interwoven.hunter.search.SearchWorker (Thread-14) - End of command is_get_index_status_vpath@7
[15 Oct 2014 22:21:45,118] DEBUG com.interwoven.hunter.common.LoggingPrintStream (Thread-14) - XMLDataGram.send:
[<dataGram>
  <data>
    <return_code>20007</return_code>
    <return_detail>The search manager is unable to contact the index manager.</return_detail>
  </data>
</dataGram>

Find more posts tagged with

Comments

Reji Varghese

May be there are services which was still running like view.exe, community.exe, category.exe etc.

Also, stop TeamSite Search, then all the other Search services, (Autonomy*.exe).

Then start the services in the order :

- start idol

- start search

- start tsconnector

Adam Stoller

Also make sure that there isn't something else using that port -- use netstat to find out (it's a system command - so check OS help / manuals for more information about what flags to use, etc.)

nipper

The index manager has a log, please find it and post any errors.

Vendim Birbili

Is not Writing to the log at all...

Vendim Birbili

reji_kv wrote:
May be there are services which was still running like view.exe, community.exe, category.exe etc.

Also, stop TeamSite Search, then all the other Search services, (Autonomy*.exe).

Then start the services in the order :
- start idol
- start search
- start tsconnector

We Did this many time in that order.

Rick Poulin

Are you looking at the right log? Search/logs/iw.tsindex.log

It should have at least a little something when you bounce the TeamSiteConnector service.

Vendim Birbili

Yes,

thats the correct log. Nothing at all .

Reji Varghese

Hope you have enough space in the disk for the logs to be written Smiley Wink

Rick Poulin

Or perhaps you've turned down the logging level.. In search.properties and search.private.properties, make sure the log4j level is set to either DEBUG or INFO -- might be worth putting it on debug for the time being while you troubleshoot.

Vendim Birbili

Thanks All for replying. Fixed the Issue by cleaning the indexes. The teamsite Connector was causing the issue .Just in case someone else run into this issue here are the steps.

Stop the Search/Connector services

Under the TeamsiteConnector Folder delete:

Action folder

temp folder

logs folder

uid folder

portinfo.dat file

TeamSiteConnector.lck file

then Restart the services