No IndexIdActive

0 views
Skip to first unread message

Nico

unread,
Jul 11, 2008, 11:52:40 AM7/11/08
to hounder
Hi, i've installed hounder following the 5 minute tutorial on an
ubuntu server. I've emptied the parameter
IndexLibrary.rsyncAccessString in the indexer properties. All the
services are in "good" state except for the searcher service. When i
access the websearch interface and i do a query i have the error "No
IndexId Active".

Do you know what it can be?

Thanks in advance.

Nicolas Bottarini

dbu...@gmail.com

unread,
Jul 11, 2008, 2:36:32 PM7/11/08
to hounder
You should check the logs for errors (indexer/logs/indexer.log and
searcher/logs/searcher.log).

Assuming you have the searcher and the indexer installed on the same
machine, emptying that configuration value should be enough.

Also, check that you have rsync installed, as indexes are copied
locally using rsync (even if IndexLibrary.rsyncAccessString is empty).

Diego

Nico

unread,
Jul 11, 2008, 2:56:27 PM7/11/08
to hounder
I have rsynch installed. The indexer and the searcher are in the same
machine.
I copy you a extract of the log files

indexer/logs/hounder.log (there is no indexer.log):

ERROR [IndexLibrary$IndexUpdaterThread]
com.flaptor.hounder.indexer.IndexLibrary - [While sending index
(localhost:/var/local/hounder/indexer/indexes/copies/
index-1214510427684) : java.rmi.ConnectIOException: error during JRMP
connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out] 2008-06-26
16:02:15,222
java.rmi.ConnectIOException: error during JRMP connection
establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:
274)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:
171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
at
java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:
179)
at
java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:
132)
at $Proxy5.setNewIndex(Unknown Source)
at
com.flaptor.hounder.searcher.IndexUpdatesListenerStub.setNewIndex(IndexUpdatesListenerStub.java:
49)
at com.flaptor.hounder.indexer.IndexLibrary
$IndexUpdaterThread.run(IndexLibrary.java:213)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at java.io.DataInputStream.readByte(DataInputStream.java:241)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:
215)


searcher/logs/hounder.log (there is no searcher.log):
ERROR [btpool0-9] com.flaptor.hounder.searcher.OpenSearchHandler -
[SEARCHING] 2008-07-11 14:18:19,340
com.flaptor.hounder.searcher.NoIndexActiveException: No indexId active
at
com.flaptor.hounder.searcher.ReloadableIndexHandler.search(ReloadableIndexHandler.java:
252)
at com.flaptor.hounder.searcher.Searcher.searchImpl(Searcher.java:
161)
at com.flaptor.hounder.searcher.Searcher.search(Searcher.java:113)
at
com.flaptor.hounder.searcher.SnippetSearcher.search(SnippetSearcher.java:
190)
at
com.flaptor.hounder.searcher.QueryParams.executeInSearcher(QueryParams.java:
77)
at
com.flaptor.hounder.searcher.TrafficLimitingSearcher.executeSearchAndPoll(TrafficLimitingSearcher.java:
128)
at
com.flaptor.hounder.searcher.TrafficLimitingSearcher.search(TrafficLimitingSearcher.java:
86)
at
com.flaptor.hounder.searcher.QueriesInProgressSearcher.search(QueriesInProgressSearcher.java:
73)
at
com.flaptor.hounder.searcher.QueryParams.executeInSearcher(QueryParams.java:
77)
at
com.flaptor.hounder.searcher.CacheSearcher.search(CacheSearcher.java:
67)
at
com.flaptor.hounder.searcher.StatisticSearcher.search(StatisticSearcher.java:
42)
at
com.flaptor.hounder.searcher.CompositeSearcher.search(CompositeSearcher.java:
137)
at
com.flaptor.hounder.searcher.OpenSearchHandler.doQuery(OpenSearchHandler.java:
318)
at
com.flaptor.hounder.searcher.OpenSearchHandler.doQuery(OpenSearchHandler.java:
92)
at org.apache.jsp.search_jsp._jspService(org.apache.jsp.search_jsp:
242)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:
373)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:
477)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:371)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
491)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:
367)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:
185)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:
181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:
689)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
391)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:268)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:
414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
491)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:
367)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:
185)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:
181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:
689)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
391)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:
114)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
139)
at org.mortbay.jetty.Server.handle(Server.java:285)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
457)
at org.mortbay.jetty.HttpConnection
$RequestHandler.headerComplete(HttpConnection.java:751)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)
at org.mortbay.jetty.bio.SocketConnector
$Connection.run(SocketConnector.java:217)
at org.mortbay.thread.BoundedThreadPool
$PoolThread.run(BoundedThreadPool.java:475)


Thanks

Nicolas

jhandl

unread,
Jul 11, 2008, 3:42:50 PM7/11/08
to hounder
Nico, please check the following settings:

- In both the indexer and searcher conf/common.properties files, check
that the base port is commented or set to 47000.

- In the indexer/conf/indexer.properties file, check that the
IndexLibrary.remoteIndexUpdaters line is as follows:
IndexLibrary.remoteIndexUpdaters=

- ping localhost and check that you get responses from 127.0.0.1 (if
not, add localhost to your /etc/hosts file).

- With the indexer and searcher running, type the following command:
netstat -lnp | grep java
Check that the output includes lines like these:
tcp 0 0 0.0.0.0:47040
0.0.0.0:* LISTEN 10321/java
Here you can see the process 10321 (a "ps aux | grep 10321" will
show you this is the searcher) is listening on the port 47040, which
corresponds to the searcher listening for new indexes.

Please check back with your results.

-- Jorge

Nico

unread,
Jul 11, 2008, 3:54:32 PM7/11/08
to hounder
All the config files are ok. And localhost is configured correctly.
When i execute the netstat i have this sort of processes:
tcp6 0 0 :::47001 :::*
LISTEN 4684/java

(note tcp6 instead of tcp).

Do you think this may be causing the problem?

Thanks

nicolas

jhandl

unread,
Jul 11, 2008, 4:23:09 PM7/11/08
to hounder
No, we have a client working ok with tcp6, so that should not be the
problem.

Try executing the following line:

ssh localhost

You should get a prompt, without being asked for confirmation or
password. If you are being asked for a password, you should create a
private-public key pair and add the public key to your ~/.ssh/
authorized_keys file. If you are being asked to authorize the host,
just answer yes and the problem should go away.

-- Jorge

Nico

unread,
Jul 11, 2008, 4:53:30 PM7/11/08
to hounder
I execute the ssh localhost command and i can connect via ssh without
beign prompted for password.
> ...
>
> read more »

jhandl

unread,
Jul 14, 2008, 11:17:31 AM7/14/08
to hounder
Hi Nico,

Do you actually get a line where the searcher is listening on port
47040?

-- Jorge

On Jul 11, 4:54 pm, Nico <nicolasbottar...@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages