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

Unable to search in CS STD

Johnny

TS 6.5, Solaris 8

I think for the most part I have search configured (though I still can't get results with EA's)

In CS PRO .. when I click on search, the screens come up fine and results return.

However ins CS STD I get the following message in the search module

"There was a problem communicating with the search server"

Tailing the logs while opening the standard home page..

iweventsub.log
iwtrace.log
iwevents.log

servletd.log
access.log

nothing much moved.. or nothing at all.. except for access.log where I saw this


199.67.140.77 - - [10/Feb/2005:16:02:32 -0500] "POST /iw-cc/command/iw.ui HTTP/1.0" 200 129332 12 jc88151
199.67.140.77 - - [10/Feb/2005:16:02:32 -0500] "GET /iw-cc/base/images/div_pagination.gif HTTP/1.0" 304 - 0 jc88151
199.67.140.77 - - [10/Feb/2005:16:02:33 -0500] "POST /iw-cc/command/iw.ccstd.search.check_index_status HTTP/1.0" 200 681 0 jc88151
199.67.140.77 - - [10/Feb/2005:16:02:35 -0500] "POST /iw-cc/command/iw.ccstd.search.check_index_status HTTP/1.0" 200 681 0 jc88151
199.67.140.77 - - [10/Feb/2005:16:02:37 -0500] "POST /iw-cc/command/iw.ccstd.search.check_index_status HTTP/1.0" 200 681 0 jc88151
199.67.140.77 - - [10/Feb/2005:16:03:58 -0500] "GET /iw-cc/command/iw.ccstd.search.check_index_status HTTP/1.0" 200 681 0 jc88151

using that URL directly, I get a basic empty html page.

I don't think this is leading me anywhere.

I'm looking for a starting point, I haven't been able to find any information regarding this.

Any help would be greatly appreciated.

John Cuiuli

Find more posts tagged with

Comments

Johnny

No one has seen this?..

Are there any pointers for tracing this message?

John Cuiuli

jbum

When you say search module, do you mean the search portlet? Or do you mean when you click on "Advanced Search" from the search portlet?

Senior MTS
Interwoven

Johnny

Sorry I meant the search portlet... I've attached a screen shot.

I haven't had any succes so we've recently raised a support case (1215293). No word yet but this other post raised a few interesting things.

John Cuiuli

jbum

Can you turn on debugging level for the search log and email them to me? Find <teamsite>/httpd/webapps/content_center/WEB-INF/conf/search/log4j.xml
and set the debug level from "warn" to "debug". Restart the webapp (servletd) and try search again.

It would be nice to see logs for both ccpro and ccstd to see what the different is.

John

Senior MTS
Interwoven

Edited by jbum on 02/23/05 11:09 AM (server time).

Johnny

OK, just did that.

I tailed the log as I was running through
A) log into STD - no messages relating to search.
Error message appears above search portlet, unable to access any search options.

log into PRO - no messages relating to search
Able to search - no metadata results, limited text results (still looking at what the difference is)

Attached is a screen shot of the portlet and the servletd log file... I didn't see anything myself.
I think overall I haven't got search working, so I may be jumping ahead of myself; it's just been very hard to trace the problem.

These are the processes running



bash-2.03# ps -ef |grep search | grep -v grep
    root 19747 19741  0   Feb 18 pts/1    0:00 /app/teamsite/Search/bin/iwsrchagent searchagent_5 search_agent /app/teamsite/S
    root 19744 19741  0   Feb 18 pts/1    0:00 /app/teamsite/Search/bin/iwsrchagent searchagent_2 search_agent /app/teamsite/S
    root 19750 19741  0   Feb 18 pts/1    0:00 /app/teamsite/Search/bin/iwsrchagent searchagent_8 search_agent /app/teamsite/S
    root 19713     1  0   Feb 18 pts/1    0:32 /app/teamsite/Search/jre/bin/java -server -Xms64m -Xmx512m -Diw.search.base.dir
    root 19748 19741  0   Feb 18 pts/1    0:00 /app/teamsite/Search/bin/iwsrchagent searchagent_6 search_agent /app/teamsite/S
    root 19741     1  0   Feb 18 pts/1    0:34 /app/teamsite/Search/jre/bin/java -server -Xms64m -Xmx512m -Diw.search.base.dir
    root 19746 19741  0   Feb 18 pts/1    0:00 /app/teamsite/Search/bin/iwsrchagent searchagent_4 search_agent /app/teamsite/S
    root 19751 19741  0   Feb 18 pts/1    0:00 /app/teamsite/Search/bin/iwsrchagent searchagent_9 search_agent /app/teamsite/S
    root 19745 19741  0   Feb 18 pts/1    0:00 /app/teamsite/Search/bin/iwsrchagent searchagent_3 search_agent /app/teamsite/S
    root 19742 19741  0   Feb 18 pts/1    0:01 /app/teamsite/Search/bin/iwsrchagent searchagent_0 search_agent /app/teamsite/S
    root 19743 19741  0   Feb 18 pts/1    0:01 /app/teamsite/Search/bin/iwsrchagent searchagent_1 search_agent /app/teamsite/S
    root 19749 19741  0   Feb 18 pts/1    0:00 /app/teamsite/Search/bin/iwsrchagent searchagent_7 search_agent /app/teamsite/S
bash-2.03# ps -ef |grep index | grep -v grep
    root 19717 19713  0   Feb 18 pts/1    0:00 /app/teamsite/Search/bin/iwsrchagent indexagent_1 index_agent /app/teamsite/Sea
    root 19718 19713  0   Feb 18 pts/1    0:00 /app/teamsite/Search/bin/iwsrchagent indexagent_2 index_agent /app/teamsite/Sea
    root 19716 19713  0   Feb 18 pts/1    0:01 /app/teamsite/Search/bin/iwsrchagent indexagent_0 index_agent /app/teamsite/Sea
bash-2.03# ps -ef |grep iw | grep -v search | grep -v index | grep -v grep
    root 29309     1  0 13:56:50 ?        0:00 /apps/teamsite/iw-home/bin/iwproxy
    iwui 29336     1  0 13:56:51 pts/1    4:36 /apps/teamsite/iw-home/tools/java/bin/java -server -Xms64m -Xmx512m -Djava.libr
    iwui 29323 29306  0 13:56:51 ?        0:00 /apps/teamsite/iw-home/iw-webd/bin/iwwebd -DUNIX -d /apps/teamsite/iw-home/iw-w
    iwui 29321 29306  0 13:56:51 ?        0:00 /apps/teamsite/iw-home/iw-webd/bin/iwwebd -DUNIX -d /apps/teamsite/iw-home/iw-w
    iwui 29319 29306  0 13:56:51 ?        0:00 /apps/teamsite/iw-home/iw-webd/bin/iwwebd -DUNIX -d /apps/teamsite/iw-home/iw-w
    iwui 29395 29306  0 13:57:43 ?        0:00 /apps/teamsite/iw-home/iw-webd/bin/iwwebd -DUNIX -d /apps/teamsite/iw-home/iw-w
    root 19454 19448  0   Feb 18 ?        0:34 iwserver.sol -e /apps/teamsite/iw-home/local/logs/iwevents.log /content/iw-stor
    iwui 29417 29306  0 13:58:29 ?        0:00 /apps/teamsite/iw-home/iw-webd/bin/iwwebd -DUNIX -d /apps/teamsite/iw-home/iw-w
    iwui 29326 29306  0 13:56:51 ?        0:00 /apps/teamsite/iw-home/iw-webd/bin/iwwebd -DUNIX -d /apps/teamsite/iw-home/iw-w
    root 29312 29309  0 13:56:50 ?        0:00 /apps/teamsite/iw-home/bin/iwproxy
    iwui 29418 29306  0 13:58:30 ?        0:00 /apps/teamsite/iw-home/iw-webd/bin/iwwebd -DUNIX -d /apps/teamsite/iw-home/iw-w
    iwui 29315 29306  0 13:56:50 ?        0:00 /apps/teamsite/iw-home/iw-webd/bin/iwwebd -DUNIX -d /apps/teamsite/iw-home/iw-w
    iwui 29419 29306  0 13:58:30 ?        0:00 /apps/teamsite/iw-home/iw-webd/bin/iwwebd -DUNIX -d /apps/teamsite/iw-home/iw-w
    root 19448     1  0   Feb 18 pts/1    0:00 /bin/sh /apps/teamsite/iw-home/private/bin/iwstart /content/iw-store
    root 20276     1  0   Feb 18 pts/1    0:04 /apps/teamsite/iw-home/tools/java/bin/java -Djava.library.path=/apps/teamsite/i
    iwui 29317 29315  0 13:56:50 ?        0:02 /apps/teamsite/iw-home/cssdk/wasp4.5.1/bin/fcgiwaspc
    iwui 29325 29306  0 13:56:51 ?        0:00 /apps/teamsite/iw-home/iw-webd/bin/iwwebd -DUNIX -d /apps/teamsite/iw-home/iw-w
    iwui 18421     1  0   Feb 18 pts/1   24:12 /apps/teamsite/iw-home/tools/java/bin/java -server -Xss4000000 -Djava.library.p
    root 19549     1  0   Feb 18 pts/1    0:34 /apps/teamsite/iw-home/eventsubsystem/../tools/java/jre/bin/java -server -Xmx25
    root 29306     1  0 13:56:50 ?        0:00 /apps/teamsite/iw-home/iw-webd/bin/iwwebd -DUNIX -d /apps/teamsite/iw-home/iw-w
    root 19443     1  0   Feb 18 pts/1    0:00 /bin/sh /apps/teamsite/iw-home/private/bin/iwprocdstart
    root 19464 19443  0   Feb 18 pts/1    0:00 /apps/teamsite/iw-home/bin/iwprocessd

John Cuiuli

jbum

Wait,

What you posted earlier and what you just told me are two different things. The error message was initially somethig like "error communicating with the search server", correct? Now you're getting a message at the top of the search portlet? Is it the same message?

Senior MTS
Interwoven

jbum

sorry, i didn't see the attacment. i'll take a look at that now.

Senior MTS
Interwoven

jbum

Can you send me "search.log"? It's in the same location as servletd.log. If search is working for you in CCPro, it should technically
be working.

Senior MTS
Interwoven

Johnny

Thanks for looking at this... it could be a wild goose chase because I'm not sure I understand it enough. It makes sense that both should work so it seems most likely that search is incorrectly set up somehow.

The search.log is 0 in size.

I turned the logging to debug for the search components and attached those log files.
I didn't see anything that made sense to me.

John Cuiuli

jbum

Hmm. Are you sure you turn on debugging for the ContentCenter? The log files you sent me are for the search/index server components.
I also need to see the client logs for search. Check to make sure you set the debug level to "debug" in log4j.xml under <teamsite>/httpd/webapps/content_center/WEB-INF/conf/search and restart servletd. Also, make sure you access the the search pages in ccstd and ccpro
so we can get some meaningful logs.

Thanks,
John

Senior MTS
Interwoven

Johnny

I appreciate your patience on this, I know it can be frustrating.

The earlier attachment I sent (with the screen shot) contained the servletd.log file as well.
Debugging is turned on, I can see debug messages in servletd.log and I did hit each search screen once.

I repeated it all again...

1. stop the servlet process IWHOME/private/bin/iwuiboot stop
2. set debug level (log4j file below)
3. delete existing log files
4. start the servlet process IWHOME/private/bin/iwuiboot start
5. wait
6. log into std (unable to perform search
7. log into pro and perform search

Search results in PRO
full text - results returned
EA - template type - results returned
EA - custom EA - no results returned (may be a configuration issue, but have not identified any that looks wrong yet.

The same message above the search portlet still appears in STD.

I've attached servletd.log. search.log is 0 in size.



<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/"
                     debug="false">

  <!-- Define Appenders here -->

  <appender name="DEFAULT" class="org.apache.log4j.ConsoleAppender">
    <param name="Target" value="System.out"/>
    <layout class="org.apache.log4j.PatternLayout">
      <param name="ConversionPattern" value="%d [%t] %-5p %c (%x) - %m%n"/>
    </layout>
  </appender>

  <!-- Define Loggers here -->

  <!-- the additivity flag indicates whether messages for a logger should
       propogate to the logger above.  if you're simply defining a sublogger
       to go to the parent's appenders, additivity should be true.  you can add
       other appenders as well and messages will go to the parent's appenders as
       well as the new appenders.  but if you want the sublogger going to
       its own logfile and not the parent's, make sure additivity is false. -->

  <!-- leave root at the bottom -->
  <root>
    <level value="debug"/>
    <appender-ref ref="DEFAULT"/>
  </root>

</log4j:configuration>
~
~
"/app/teamsite/iw-home/httpd/webapps/content_center/WEB-INF/conf/log4j.xml" 31 lines, 1145 characters

John Cuiuli

jbum

I believe the log4j.xml you edited is for the default ConsoleAppender. That one is used by servletd.log I think.
That is not the one we need to change. Change the one under WEB-INF/conf/search (note: "search").
Try the steps again once you've done this. If you can, it would be nice to delete the log before you start a new one
so I won't get lost with the 100's of lines of logs.

Thanks,
John (be back in an hour or so, meeting)

Senior MTS
Interwoven

Johnny

oh man.. so sorry.. I didn't pick that up at all (and you wrote it twice!)

back we go...

John Cuiuli

Johnny

OK... here it is. The exact same steps above were repeated (with the right log4j configured)

When I log into STD I see this



2005-02-23 15:34:19,074 DEBUG com.interwoven.ui.search (jc88151) - Search server status: good
2005-02-23 15:34:37,935 DEBUG com.interwoven.ui.search (jc88151) - Search server status: unindexed

The first workarea in the drop down list is not indexed, there are only two branches set up for search at this point.
If I change the drop down field to an indexed branch - nothing different happens.
If I log out and back it, it still takes me back to the original branch/workarea (unindexed)
I'm assuming the drop down is just listed alphabetically.

John Cuiuli

jbum

I only see CCPro log statements in the attachment. You may have to turn on one more logging file
for you to get CCStd search logs. I believe you need to change the logger level to debug on CCStd's
log4j.xml as well. Look for this:

<logger name="com.interwoven.ui.teamsite.ccstd.search" additivity="false">
<level value="warn"/>
<appender-ref ref="CCSTD_SEARCH"/>
</logger>

Can you change that, restart servletd and send me the log after going to the search portlet? After selecting the drop down
item, give it a couple of seconds to make sure it processed.

The drop down list in CCStd is more or lese alphabetically ordered. There was a fix to preselect it with the last selection made
in TS6.5 SP1 if you're interested.

John

Senior MTS
Interwoven

Johnny

OK I saw that setting in /conf/ccstd/log4j.xml and changed it to debug.
I repeated the steps above.

When changing between workareas in the drop down the same messages were appearing in search.log


2005-02-24 09:48:44,964 DEBUG com.interwoven.ui.search (jc88151) - Search server status: unindexed
2005-02-24 09:49:02,012 DEBUG com.interwoven.ui.search (jc88151) - Search server status: good
2005-02-24 09:49:19,825 DEBUG com.interwoven.ui.search (jc88151) - Search server status: good
2005-02-24 09:49:23,022 DEBUG com.interwoven.ui.search (jc88151) - Search server status: unindexed
2005-02-24 09:49:25,837 DEBUG com.interwoven.ui.search (jc88151) - Search server status: unindexed
2005-02-24 09:49:27,825 DEBUG com.interwoven.ui.search (jc88151) - Search server status: unindexed
2005-02-24 09:49:29,712 DEBUG com.interwoven.ui.search (jc88151) - Search server status: good

I haven't been able to understand anything in servletd.log

Boy I'm confused.

John Cuiuli

jbum

from the logs, you should be getting the error message that you've been getting.

so have you tried selecting an area that is indexed and waiting for the previous error message to change or disappear?
it should.

Senior MTS
Interwoven

Johnny

I'm not exactly sure what you mean.

I think you're asking if I see the log file messages below tick over as I change the work area drop down.

If so, yes, that's the case.

I was tailing search.log while changing the workarea and those messages appeared below on each change. The messages (unindexed, good) come up correctly against those branches that are / are not indexed.

I have a screen shot, but it's too big to upload here (180KB) , I'll email it to you.

Let me know if I missed your point.



2005-02-24 09:48:44,964 DEBUG com.interwoven.ui.search (jc88151) - Search server status: unindexed
2005-02-24 09:49:02,012 DEBUG com.interwoven.ui.search (jc88151) - Search server status: good
2005-02-24 09:49:19,825 DEBUG com.interwoven.ui.search (jc88151) - Search server status: good
2005-02-24 09:49:23,022 DEBUG com.interwoven.ui.search (jc88151) - Search server status: unindexed
2005-02-24 09:49:25,837 DEBUG com.interwoven.ui.search (jc88151) - Search server status: unindexed
2005-02-24 09:49:27,825 DEBUG com.interwoven.ui.search (jc88151) - Search server status: unindexed
2005-02-24 09:49:29,712 DEBUG com.interwoven.ui.search (jc88151) - Search server status: good

John Cuiuli

jbum

The log file looks good. However, I was asking if the error message that comes up in the search portlet goes away if you select an
area that "is" indexed. The "... error communicating with the search server" should go away if you select an indexed area.

Senior MTS
Interwoven

Johnny

ohhh ok.. Nope, it stays there... for better or for worse...
Even if I select an indexed branch and go off to another porlet and do other work, it's persistant.

John Cuiuli

Johnny

Just to add on that... throughout the whole time, the text field is editable, but the search icon and advanced search link are disabled.

John Cuiuli

Migrateduser

John,

Was just curious if you was able to resolve this in the end? I just recently installed TS 6.5 & Search & getting exactly the same messages after logging into both STD & PRO (as in your attachments). Also the log4j configured as mentioned in the thread.

in STD
There was a problem communicating with the search server
in PRO
An error occurred executing command com.interwoven.ui.teamsite.ccpro.search.AdvancedSearchCommand

The setup looks good to me (including ccsdk.cfg change). The only difference is I have Search server is installed on a seperate machine. Can you share the details before I can catch the support on this?

The env I have is,
Solaris 9
TS6.5 SP1
Search Server with SP1
Carrying out tests using the available sample templating & search config files.

! Thanks
Anand

Migrateduser

Resolved.. it was a service pack problem.

fiquebem

We have TS 6.5 SP1, Search SP1 + the SP1 patch on a Solaris 9 box. We're seeing "There was a problem communicating with the search server." on CC Standard. We're having no trouble with CC Professional.

/usr/iw-home/local/logs/iwui/search.log shows:

2005-08-18 14:05:16,539 DEBUG com.interwoven.ui.search (skhatri) - Search server status: good

The ccstd.log file is empty, even though I have what's shown below in /usr/iw-home/httpd/webapps/content_center/WEB-INF/conf/ccstd/log4j.xml.

Even thoug the Search and Index servers are running on the same box as TS, I uncommented the following in /usr/iw-home/cssdk/cssdk.cfg and restarted TS:

search.server.host: localhost
search.server.port: 6720

We even ran "make_toolkit.ipl -target clobber" and then make_toolkit.ipl.

No joy. CC Standard still says: "There was a problem communicating with the search server."

Sigh ...

S.

<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/"
debug="false">



<appender name="DEFAULT" class="org.apache.log4j.ConsoleAppender">
<param name="Target" value="System.out"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d [%t] %-5p %c (%x) - %m%n"/>
</layout>
</appender>

<appender name="BIZUI" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="${log100.iwlogs}/iwui/ccstd.log"/>
<param name="MaxFileSize" value="1MB"/>
<param name="MaxBackupIndex" value="2"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c (%x) - %m%n"/>
</layout>
</appender>


<logger name="com.interwoven.ui.teamsite.ccstd.search" additivity="false">
<level value="debug"/>
<appender-ref ref="BIZUI"/>
</logger>

</log4j:configuration>