Search not working

What

Hi,

When I click on search it is taking long time and at the end it is saying:

The Interwoven Web Daemon was unable to contact the Interwoven Servlet Engine. The Interwoven Servlet Engine may be down, or running on an unexpected host or port.

But teamsite is working fine.

In TS logs I see: /tsmount/local/logs/iwui/search.log

2011-07-21 01:37:32,475 ERROR com.interwoven.ui.search.AbstractAdvancedSearchCommand ( commandID iw.search.ccpro.advanced_search) - An unknown error occurred communicating with the search server.
2011-07-21 01:50:47,034 ERROR com.interwoven.ui.search.AbstractAdvancedSearchCommand ( commandID iw.search.ccpro.advanced_search) - An error occurred communicating with the search server: Unable to contact the Search Server


When I checked logs at Search server it is giving error:

[21 Jul 2011 01:54:57,218] INFO com.interwoven.hunter.index.IndexServer (main) - *************************************************
[21 Jul 2011 01:54:57,220] INFO com.interwoven.hunter.index.IndexServer (main) - Server starting....
[21 Jul 2011 01:54:57,226] INFO com.interwoven.hunter.index.IndexServer (main) - Trying to bind to port 6715
[21 Jul 2011 01:54:57,230] FATAL com.interwoven.hunter.index.IndexServer (main) - java.net.BindException: Address already in use

in log: /opt/webapps/interwoven/Search/log/iw.tsindex.log

process name & ID: /opt/webapps/interwoven/Search/jre/bin/java 14348, Running On Port: 6715


I have restarted the search server many times.
But not able to make the Search link work in TS.

Please assist.

Thanks.

Rick Poulin

[21 Jul 2011 01:54:57,226] INFO com.interwoven.hunter.index.IndexServer (main) - Trying to bind to port 6715 [21 Jul 2011 01:54:57,230] FATAL com.interwoven.hunter.index.IndexServer (main) - java.net.BindException: Address already in use

This is obviously the source of the problem. It's quite likely that your CLTs have gotten mixed up PIDs. Shutdown both search services, then check your running processes. I would expect to see an instance still running, and you'll have to kill the process manually before starting up the services again.