Error in Search server

I am trying to search contents in a Teamsite branch, for which a TS search server has been configured .
TS Index and Search server resides on a separate m/c.

Its not returning anything.

In the iw.tssearch.log I receive the following message:

[10 Sep 2008 23:20:24,476] INFO com.interwoven.hunter.search.SearchWorker (Thread-71) - Connection terminated by client.

also when I try to run iwndxmgrstatus.exe on command line,it won't return anything.
also None of the exe is returning anything ,which resides under c:\Interwoven\TeamSiteSearch\bin

Need your sincere help.Please provide solution asap.

Thanks
Neeraj Kumar.

Find more posts tagged with

Comments

Frederik

looks like something or someone stopped your Search server (and quite possibly your Index server - if none of the $IWSEARCH commands respond). Question of course is why... you'll need to do some more digging in the logs.

btw, platform? ts version?

neeraj_forever

looks like something or someone stopped your Search server (and quite possibly your Index server - if none of the $IWSEARCH commands respond). Question of course is why... you'll need to do some more digging in the logs.

btw, platform? ts version?

Thanks for the reply

Actually only iw.tssearch.log changes and the message shows like

[10 Sep 2008 23:20:24,476] INFO com.interwoven.hunter.search.SearchWorker (Thread-71) - Connection terminated by client.
when i do search.

brvhrt

most likely your index server is down . i think the search server is trying to connect to the index server as it doesnt find it running the connection then gets terminated.

make sure u start the index server and see the iw.tsindex.log file. it should give some idea in what is happening with ur index server.

pdasarat

Check if your port is open on the firewall between your search and index servers. The port number can be picked up from index.properties & search.properties

Pradeep

neeraj_forever

Check if your port is open on the firewall between your search and index servers. The port number can be picked up from index.properties & search.properties

Pradeep

I have checked the port number and log files only iw.tssearch.log changes and the message shows like

[10 Sep 2008 23:20:24,476] INFO com.interwoven.hunter.search.SearchWorker (Thread-71) - Connection terminated by client.
when i do search.

neeraj_forever

most likely your index server is down . i think the search server is trying to connect to the index server as it doesnt find it running the connection then gets terminated.

make sure u start the index server and see the iw.tsindex.log file. it should give some idea in what is happening with ur index server.

neeraj_forever

looks like something or someone stopped your Search server (and quite possibly your Index server - if none of the $IWSEARCH commands respond). Question of course is why... you'll need to do some more digging in the logs.

btw, platform? ts version?

I have checked the ts version ,seach server version,everything seems fine but not reached to the solution.Also
I have checked the port number and log files only iw.tssearch.log changes and the message shows like

[10 Sep 2008 23:20:24,476] INFO com.interwoven.hunter.search.SearchWorker (Thread-71) - Connection terminated by client.
when i do search.

neeraj_forever

looks like something or someone stopped your Search server (and quite possibly your Index server - if none of the $IWSEARCH commands respond). Question of course is why... you'll need to do some more digging in the logs.

btw, platform? ts version?

The Environment are as follow:
TS server: Win server 2003 enterprise edition SP1 with TS 6.5.0 SP3, event subsystem is configured and running.
Search server: Win server 2003 Standard edition SP2 with TS search SP2 and TS Search SP3.

Adam Stoller

The Environment are as follow:
TS server: Win server 2003 enterprise edition SP1 with TS 6.5.0 SP3, event subsystem is configured and running.
Search server: Win server 2003 Standard edition SP2 with TS search SP2 and TS Search SP3.

Have you opened a case with IWOV Support (I see no indication of such in this thread) - if not, I'd suggest doing so.

neeraj_forever

Have you opened a case with IWOV Support (I see no indication of such in this thread) - if not, I'd suggest doing so.

Thanks for your reply.

I have checked everything what I need to do search but not able to find the solution.

Thanks
Neeraj

Adam Stoller

Thanks for your reply.

I have checked everything what I need to do search but not able to find the solution.

Thanks
Neeraj

That doesn't answer my question - have you opened a case with IWOV Support? Have you tried working with them to figure out the source (and fix) for the problem you are encountering?

Frederik

stop search service
stop index service
start index service
start search service

and if you still have a problem, attach the entire index log and search log for today.

All of this "I checked and everything seems fine" is not helping us to help you.

neeraj_forever

That doesn't answer my question - have you opened a case with IWOV Support? Have you tried working with them to figure out the source (and fix) for the problem you are encountering?

No I havn't opened a case with IWOV Support.

neeraj_forever

stop search service
stop index service
start index service
start search service

and if you still have a problem, attach the entire index log and search log for today.

All of this "I checked and everything seems fine" is not helping us to help you.

please find the iwsearch.log as an attachment.Also
No changes are seen in the following logs
iwtsindexwrapper.log
iwtssearchwrapper.log
iw.tsindex.log

Pawan

Please attach the attachment

please find the iwsearch.log as an attachment.Also
No changes are seen in the following logs
iwtsindexwrapper.log
iwtssearchwrapper.log
iw.tsindex.log

neeraj_forever

Please attach the attachment

I have attached the log file.

Thanks
Neeraj

Frederik

No changes are seen in the following logs
iwtsindexwrapper.log
iwtssearchwrapper.log
iw.tsindex.log

if you restart the index server, and nothing is printed to the iw.tsindex.log, than I STRONGLY suspect there is sth wrong with the index server. Can you confirm it is running at all? If the index server isn't running, there isn't much the Search server can do, I believe

Usage: iwndxmgrstatus [-h|-v]
Get the current status of index server. The index server may be in ACTIVE or FROZEN state.