Problem with searcher component

4 views
Skip to first unread message

Bilford

unread,
Aug 12, 2009, 12:17:06 PM8/12/09
to hounder
I have hounder installed (I have tried this on both Ubuntu and Fedora)
but the searcher component won't start. Web interface says it's
"unreachable" and when I try to start it manually it says that it
started. Is there a memory requirement or something I'm missing?
Thanks for the help.


Billford

Bilford

unread,
Aug 12, 2009, 12:41:12 PM8/12/09
to hounder
I fixed this. SELinux was causing the problem. Now it just says "BAD"
which I expect is because the index is hosed because of all the
stopping.

Bilford

unread,
Aug 12, 2009, 1:37:13 PM8/12/09
to hounder
Well I thought I fixed this. It's still saying "unreachable"

Jorge Handl

unread,
Aug 12, 2009, 3:24:43 PM8/12/09
to hou...@googlegroups.com
Bilford, did you try using the command line start/status/stop scripts?

Bill Mathews

unread,
Aug 12, 2009, 5:04:54 PM8/12/09
to hou...@googlegroups.com
Jorge,

   Yes, they claim it is started but it isn't .

Billford
--

This is my gmail account, there are many like it
but this one is mine.

Jorge Handl

unread,
Aug 12, 2009, 5:37:03 PM8/12/09
to hou...@googlegroups.com
Try stopping the searcher, deleting the "indexes" directory and starting it again. Do it using the command line tools, and tell me how it goes. 

bill...@gmail.com

unread,
Aug 12, 2009, 10:50:54 PM8/12/09
to hou...@googlegroups.com
When I did that, it's reachable but the status is now "BAD"


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hounder" group.
To post to this group, send email to hou...@googlegroups.com
To unsubscribe from this group, send email to hounder+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hounder?hl=en
-~----------~----~----~----~------~----~------~--~---

signature.asc

Jorge Handl

unread,
Aug 12, 2009, 11:10:10 PM8/12/09
to hou...@googlegroups.com
Have you tried using the searcher through, for example, its web interface?

Bilford

unread,
Aug 13, 2009, 12:16:35 PM8/13/09
to hounder
It crashed sometime in the middle of the night and now it won't
restart.

On Aug 12, 11:10 pm, Jorge Handl <jha...@gmail.com> wrote:
> Have you tried using the searcher through, for example, its web interface?
>
> On Wed, Aug 12, 2009 at 11:50 PM, <billf...@gmail.com> wrote:
> > When I did that, it's reachable but the status is now "BAD"
>
> > On Wed, Aug 12, 2009 at 5:37 PM, Jorge Handl <jha...@gmail.com> wrote:
>
> >> Try stopping the searcher, deleting the "indexes" directory and starting
> >> it again. Do it using the command line tools, and tell me how it goes.
>
> >> On Wed, Aug 12, 2009 at 6:04 PM, Bill Mathews <billf...@gmail.com> wrote:
>
> >>> Jorge,
>
> >>>    Yes, they claim it is started but it isn't .
>
> >>> Billford
>
> >>> On Wed, Aug 12, 2009 at 3:24 PM, Jorge Handl <jha...@gmail.com> wrote:
>
> >>>> Bilford, did you try using the command line start/status/stop scripts?
>

Jorge Handl

unread,
Aug 13, 2009, 1:26:28 PM8/13/09
to hou...@googlegroups.com
How did it crash?

Bill Mathews

unread,
Aug 13, 2009, 1:43:38 PM8/13/09
to hou...@googlegroups.com
Not really sure. It just stopped running. The logs are empty and no core file.

Jorge Handl

unread,
Aug 13, 2009, 1:51:50 PM8/13/09
to hou...@googlegroups.com
Bill, the searcher doesn't just stop running, much less without any exception in the log. Something must have happened, maybe someone killed the process. You didn't say if the searcher was working after you started it.
A lot more information is needed to diagnose the problem.
- Jorge

Bill Mathews

unread,
Aug 13, 2009, 1:59:02 PM8/13/09
to hou...@googlegroups.com
*that should've been "no one stopped it"

On Thu, Aug 13, 2009 at 1:58 PM, Bill Mathews <bill...@gmail.com> wrote:
It's on a private VM server so no one started it.

When I did get it started and the status in the web interface was "BAD" the searcher interface came up but didn't return any results. (I meant to respond). I'm going to try this on a physical machine shortly. 

I've been working with software for many years (mostly on Unix) and I assure you that lots of software stops working without any log messages. :-)

Bill Mathews

unread,
Aug 13, 2009, 1:58:38 PM8/13/09
to hou...@googlegroups.com
It's on a private VM server so no one started it.

When I did get it started and the status in the web interface was "BAD" the searcher interface came up but didn't return any results. (I meant to respond). I'm going to try this on a physical machine shortly. 

I've been working with software for many years (mostly on Unix) and I assure you that lots of software stops working without any log messages. :-)




Bill Mathews

unread,
Aug 13, 2009, 2:10:10 PM8/13/09
to hou...@googlegroups.com
Okay,

1) moved it to a physical machine

2) search status still says "bad"

3) 47012/websearch won't connection (47012 is NOT listening on the server)

4) removed searcher/indexes -- restarted -- same results.

logs/searcher.out is empty
logs/searcher.err says:

 cat logs/searcher.err
2009-08-13 14:07:59.815::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
Exception in thread "main" java.lang.IllegalStateException: Property xmlsearch.transformMap not found
        at com.flaptor.util.Config.get(Config.java:181)
        at com.flaptor.util.Config.getString(Config.java:326)
        at com.flaptor.util.Config.getStringArray(Config.java:334)
        at com.flaptor.hounder.searcher.XmlSearchHandler.<init>(XmlSearchHandler.java:98)
        at com.flaptor.hounder.searcher.MultipleRpcSearcher.<init>(MultipleRpcSearcher.java:100)
        at com.flaptor.hounder.searcher.MultipleRpcSearcher.main(MultipleRpcSearcher.java:135)

Jorge Handl

unread,
Aug 13, 2009, 3:17:25 PM8/13/09
to hou...@googlegroups.com
Ok, that is what we needed. It was a missing property, the searcher didn't really start.
I uploaded the fixed binaries and source.
- Jorge

Bill Mathews

unread,
Aug 13, 2009, 3:34:00 PM8/13/09
to hou...@googlegroups.com
YAY! Going to test now. Thanks!

Bill Mathews

unread,
Aug 13, 2009, 3:38:31 PM8/13/09
to hou...@googlegroups.com
Same problem it seems.

Bill Mathews

unread,
Aug 13, 2009, 3:49:15 PM8/13/09
to hou...@googlegroups.com
oh wait, just noticed the version numbers didn't change.

*waits a bit*

Jorge Handl

unread,
Aug 13, 2009, 4:05:35 PM8/13/09
to hou...@googlegroups.com
That is strange. Are you sure you replaced the .jar files and that the searcher failed with the same message?

Bill Mathews

unread,
Aug 13, 2009, 4:18:05 PM8/13/09
to hou...@googlegroups.com
Yes, I'm sure. I think I might've just grabbed a cached copy (stupid proxies)


Just re-downloaded, it's installed, working. The searcher status still says "BAD" but I can get to the websearch interface on 47012/websearch. I'll give it a bit to build out the index.

Jorge Handl

unread,
Aug 13, 2009, 4:26:21 PM8/13/09
to hou...@googlegroups.com
Ok, glad it worked now. Keep us posted.
- Jorge

Bill Mathews

unread,
Aug 13, 2009, 4:28:03 PM8/13/09
to hou...@googlegroups.com
Will do. It's still not searchable (no IndexID active).

Bill Mathews

unread,
Aug 13, 2009, 4:31:02 PM8/13/09
to hou...@googlegroups.com
Okay, now instead of no indexid active I get another search box with my query in it (so there are two on the screen). I am searching for something that should definitely be in the index. I can send a screenshot if required.


Bill

Jorge Handl

unread,
Aug 13, 2009, 4:35:06 PM8/13/09
to hou...@googlegroups.com
I just tested the search in a clean install and had no problem.
Please send a screenshot.

Bill Mathews

unread,
Aug 13, 2009, 4:50:30 PM8/13/09
to hou...@googlegroups.com
Got it. I just re-installed and all good. Thanks for all your help!

Jorge Handl

unread,
Aug 13, 2009, 4:51:07 PM8/13/09
to hou...@googlegroups.com
No problem!
Reply all
Reply to author
Forward
0 new messages