Confirming for https://en.wikipedia.org/w/index.php?search=Template:First government of Napoleon&title=Special%3ASearch&fulltext=Search&srbackend=LuceneSearch

but no error with our new CirrusSearch backend that will become default at some point: https://en.wikipedia.org/w/index.php?search=Template:First%20government%20of%20Napoleon&title=Special%3ASearch&fulltext=Search&srbackend=CirrusSearch

aymatth2 wrote:

This may be a database corruption problem, therefore not cirrus-fixed.(In reply to Andre Klapper from comment #1)

Confirming for https://en.wikipedia.org/w/index.php?search=Template:First
government of
Napoleon&title=Special%3ASearch&fulltext=Search&srbackend=LuceneSearch

but no error with our new CirrusSearch backend that will become default at
some point:
https://en.wikipedia.org/w/index.php?search=Template:
First%20government%20of%20Napoleon&title=Special%3ASearch&fulltext=Search&srb
ackend=CirrusSearch

Huh? Can you elaborate about DB corruption? I get search results listed when using the CirrusSearch backend, but primary backend currently is LuceneSearch.

aymatth2 wrote:

(In reply to Andre Klapper from comment #3)

Huh? Can you elaborate about DB corruption? I get search results listed when
using the CirrusSearch backend, but primary backend currently is
LuceneSearch.

When I try with test2.Wikipedia, https://test2.wikipedia.org/w/index.php?search=Template%3AFirst+government+of+Napoleon&title=Special%3ASearch&go=Go, I get the expected "There were no results matching the query." But that is obviously not pointing to the main live WP database.

In the production version, the error appears with any search starting with "Template:First government of", e.g. https://en.wikipedia.org/w/index.php?title=Special%3ASearch&profile=default&search=Template%3AFirst+government+of+xxx&fulltext=Search

It is hard to see that string being hard-coded into the software, so it seems more likely that there is something odd in the database. Just a guess... If it works for you with the CirrusSearch backend pointing to the production database, that is obviously not the problem. But it is a bit strange if the software is sensitive to that string.

aymatth2 wrote:

O.k. - duh - I see that you did try with CirrusSearch backend pointing to the production database, and results were o.k. Not worth worrying about.

It is a problem in lsearchd. Could be anything though .I've been suspecting enwiki search index corruption for some weeks now with lsearchd...

It's fixed by default in Cirrus because we don't report such vague errors like this nor is our index corrupted.

Moving and marking WONTFIX as appropriate.