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; } } }

Problem communicating with the search server

Aleks

Hi all,

I set up our TS server, index server, and search server as like cssdk.cfg in TS, also search/index host name, port, and java.naming on search/index server.

but now it still tell me there is a problem communicating with search server.

If i am right, it should modify cssdk.cfg from TS, then go to search/index server, only need to modify the file is called search.properties.
But i am not sure about iw.index.agent.idxdir/iw.search.agent.inxdir if correct or not.

On search server: iw.search.agent.idxdir=e:/iw-indexes;
on index server: iw.index.agent.idxdir=//vldsearchqa1/e$/iw-indexes

Am i missing something?

Thank,
TS 6.7.1 Win2003 with seperated index and search server on Win 2003

Find more posts tagged with

Comments

nipper

1st, is it running ?

Open the services and see. Is the DB available ? Are there any entries in the logs or the event log ? Is the event subsystem running ?

Aleks

1st, is it running ?

Open the services and see. Is the DB available ? Are there any entries in the logs or the event log ? Is the event subsystem running ?

Yes, these 3 servers are running.
log file-> i am not sure which log you mentioned, but i checked the event.log, it did not say any thing about this.
DB available -> do you mean in TS server or index/search server? TS: Yes.
event subsystem running -> Yes.

nipper

Are the Search SERVICES (index & search) running ? They are on the search server. Look around on the search server for the logs.

Aleks

Are the Search SERVICES (index & search) running ? They are on the search server. Look around on the search server for the logs.

Thank you for your quick response. Index service is in different box with Search service.
Index server is running. Search was running before. but it is not now after i changed the index directory. I tried to restart it, but it says no.
Here is logs:
One search log (iw.tssearch.log) shows below:
Search server could not be started
java.io.IOException: Could not access the path: e:\iw-indexes
at com.interwoven.hunter.search.SearchServer.main(SearchServer.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:136)
at java.lang.Thread.run(Thread.java:595)

Another one(iwtssearchwrapper.log) shows below:
STATUS | wrapper | 2008/09/02 12:21:21 | <-- Wrapper Stopped
STATUS | wrapper | 2008/09/02 12:21:57 | --> Wrapper Started as Service
STATUS | wrapper | 2008/09/02 12:21:57 | Launching a JVM...
INFO | jvm 1 | 2008/09/02 12:21:58 | Wrapper (Version 3.1.0) http://wrapper.tanukisoftware.org
INFO | jvm 1 | 2008/09/02 12:21:58 |

But i just found there is no IIS on these 2 servers. Is it needs?

nipper

Is search on a different system than the index supported ?

This certainly implies the index does not like e:\iw-indexes as the index dir.

but it is not now after i changed the index directory. I tried to restart it, but it says no.
Here is logs:

java.io.IOException: Could not access the path: e:\iw-indexes

Aleks

Is search on a different system than the index supported ?

This certainly implies the index does not like e:\iw-indexes as the index dir.

The search server is on different box than index server.

Because of e:\iw-indexes, i created the folder for search directory, then it running.

But i went back to Ts, this time it shows "The selected area is not indexed for search."

Where is wrong for this error message?

brvhrt

The search server is on different box than index server.

Because of e:\iw-indexes, i created the folder for search directory, then it running.

But i went back to Ts, this time it shows "The selected area is not indexed for search."

Where is wrong for this error message?

it simply means that the index server didnt index your area. most likely ur search server is down.

you should be looking at iw.tsindex.log , and iw.tssearch.log files under Search/log dir . they should give you a better idea about the errors u r getting

nipper

But i went back to Ts, this time it shows "The selected area is not indexed for search."

Where is wrong for this error message?

Nothing wrong with that error message. You need to edit the branches.cfg file and add the branches you want indexed. Then restart the indexer.

Aleks

it simply means that the index server didnt index your area. most likely ur search server is down.

you should be looking at iw.tsindex.log , and iw.tssearch.log files under Search/log dir . they should give you a better idea about the errors u r getting

In iw.tsindex.log, it shows below:
[02 Sep 2008 15:22:43,046] ERROR com.interwoven.hunter.index.IncrementalRequestCollection (Thread-25) - Sci error locating edition
TeamSite Code :5000059
com.interwoven.hunter.common.TSException
at com.interwoven.hunter.common.Repository.lookupByVpath(Repository.java:382)
at com.interwoven.hunter.common.Repository.lookupByVPath(Repository.java:349)
at com.interwoven.hunter.common.Repository.getBranchInfoFromVPath(Repository.java:174)
at com.interwoven.hunter.index.IncrementalRequestCollection.addEvent(IncrementalRequestCollection.java:57)
at com.interwoven.hunter.index.Listener.onMessage(Listener.java:237)
at org.exolab.jms.client.JmsMessageConsumer.onMessage(Unknown Source)
at org.exolab.jms.client.JmsSession.execute(Unknown Source)
at org.exolab.jms.client.JmsSession.onMessage(Unknown Source)
at org.exolab.jms.client.mipc.IpcJmsMessageListener.onMessage(Unknown Source)
at org.exolab.jms.client.mipc.IpcJmsMessageListener.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
[02 Sep 2008 15:22:43,046] ERROR com.interwoven.hunter.index.IncrementalRequestCollection (Thread-25) - Event ignored

but in iw.tssearch.log is fine, no errors, it shows: Registered vldsearchqa1:6720

do you have any ideas what is that?

Frederik

The search server is on different box than index server.

from the TS 6.7.2 release notes (I suppose same applies for 6.7.1)

[INDENT]You could use one server to install TeamSite and another server for the index manager and search manager. (...) Installing search manager, index manager, and TeamSite on three different servers is not supported.[/INDENT]

intervowen

Was this thread got into any conclusion.
I am getting the same TeamSite Code :5000059 error.
Please let me know if you guys have any findings or solutions.

Migrateduser

Wow...thread is 3 years old and wants an update.

intervowen

Thats why we sometimes need to close the thread, if we get any solutions.
Just that it might be helpful for some one in future. Like me today.

Anyways.
The patch that the support gave us, helped.

1.In search_home/lib folder, back up the current hunter_common.jar and hunter_search.jar
2. Stop search server
3. Copy over the 2 new jars
4. Start search server

Index the list of WA.

Thanks!

Frederik

from the description of your patch, I'm concluding you are on 7.2.0 - we had the same problem and the same patch. The thread above, is 3+ years old, and most definitely about another version (6.7.x)