Last modified: 2014-02-13 21:58:25 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T50964, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 48964 - lucene-search failure: java.lang.RuntimeException: Index wiki.prefix doesn't exist
lucene-search failure: java.lang.RuntimeException: Index wiki.prefix doesn't ...
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
lucene-search-2 (Other open bugs)
unspecified
All Linux
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-30 10:21 UTC by oz42
Modified: 2014-02-13 21:58 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description oz42 2013-05-30 10:21:28 UTC
when searching witin Mediawiki + MWsearch, the lucene-search daemon says:

2098303 [pool-2-thread-1] INFO  org.wikimedia.lsearch.frontend.HttpHandler  - query:/prefix/wiki/E?namespaces=0&offset=0&limit=10&version=2.1&iwlimit=10&searchall=0 what:prefix dbname:wiki term:E
java.lang.RuntimeException: Index wiki.prefix doesn't exist

A fresh installation on another server makes no difference.

expected result:
./build 
or, more precise
java -cp LuceneSearch.jar org.wikimedia.lsearch.importer.BuildAll $dumpfile $dbname

should build this index at installation.
Comment 1 Andre Klapper 2013-05-30 15:32:50 UTC
Which MediaWiki version is this about?
Comment 2 oz42 2013-06-01 09:05:26 UTC
It is MW 1.20.6
Comment 3 Andre Klapper 2013-06-03 10:00:22 UTC
Also reported here (unfortunately without replies): https://www.mediawiki.org/wiki/Thread:Extension_talk:Lucene-search/Index_doesn%27t_exist
Comment 4 Chad H. 2014-02-13 21:58:25 UTC
lsearch has reached its end of life. All users are encouraged to migrate to CirrusSearch/Elasticsearch.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links