Hi Nik, As I was reading the docs for MWSearch, I considered whether I should switch to CirrusSearch, so it may not be a difficult sell. I'd even volunteer to try to update the documentation if you're willing to help walk me through it.
But to show how clueless I am... I'm not sure how to check the other end, since I'm not clear on what it's trying to do. Here's my undoubtedly deeply flawed understanding of what happens (this reflects that I'm a biologist by training and badly self-taught on wikis and linux/unix/osx). I'm assuming that the problem is in this first step of the update script java -cp LuceneSearch.jar org.wikimedia.lsearch.oai.IncrementalUpdater -l $@ \ It's listing a bunch of update items (the ... in my first post). I am guessing that it pulls info on revisions from the mysql database and converts them to some format that gets sent to the indexer, which I assume is part of apache Lucene. From the error, it's failing to pass that through some socket to the indexer. But I don't know how to see a log for activity on that socket. My similarly uninformed reading about CirrusSearch is that it uses elasticsearch, which in turn uses Lucene. So if the problem is between the incrementalUpdater and Lucene, I might have similar issues with CirrusSearch. But if CirrusSearch gives more informative errors, that would help!! And maybe I should switch anyway, as it sounds like support for MWsearch will go away at some point. Jim On Nov 7, 2013, at 7:37 AM, Nikolas Everett wrote: > On Wed, Nov 6, 2013 at 7:04 PM, Jim Hu <[email protected]> wrote: > >> Our MWsearch stopped updating a while ago. I'm wondering if one of >> Apple's Java updates caused a problem. >> > > I'm work on the system that will replaceMWsearch/LuceneSearch so I have to > try to sell it to you first: > https://www.mediawiki.org/wiki/Extension:CirrusSearch > > Now that that is out of the way I'll try to do what I can to help you fix > what you have. > > First: Apple's Java has grown famous over the past few years for not being > quite right. I don't think that is the problem, but it might be. > > >> >> Release notes say the backend is it's Lucene Sarch 2.1.3. Checking the >> Java version: >> >> $ java -version >> java version "1.6.0_51" >> Java(TM) SE Runtime Environment (build 1.6.0_51-b11-457-10M4509) >> Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01-457, mixed mode) >> > > We're running > $ java -version > java version "1.6.0_38" > Java(TM) SE Runtime Environment (build 1.6.0_38-b05) > Java HotSpot(TM) 64-Bit Server VM (build 20.13-b02, mixed mode) > > with LuceneSearch, for reference. There is no reason why the newer one > shouldn't work as well. > > >> >> When I try to do >> >> sudo sh update >> >> from the Lucene-search directory, I get a bunch of messages and then: >> >> 14420 [main] WARN >> org.wikimedia.lsearch.interoperability.RMIMessengerClient - Error >> invoking remote method enqueueFrontend() on host Hexamer : error >> marshalling arguments; nested exception is: >> java.net.SocketException: Broken pipe >> <snip> >> > > What does the other side say about the error? Is it logging any complaints? > > >> >> It worked before, but the person who helped set it up has left my group. >> Java problem? conf problem? Any help would be appreciated >> > > Are you running the same Java and LuceneSearch version on the client > machine and the server machine? I'm not super familiar with that part of > LuceneSearch but this might be important. > > Nik > _______________________________________________ > MediaWiki-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ===================================== Jim Hu Professor Dept. of Biochemistry and Biophysics 2128 TAMU Texas A&M Univ. College Station, TX 77843-2128 979-862-4054 _______________________________________________ MediaWiki-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
