Last modified: 2014-10-22 20:58:56 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 T68259, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66259 - Valid Page name resulting in backend search error
Valid Page name resulting in backend search error
Status: NEW
Product: Wikimedia
Classification: Unclassified
lucene-search-2 (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 69730 71722 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-06 15:42 UTC by Adam Hyland
Modified: 2014-10-22 20:58 UTC (History)
6 users (show)

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


Attachments

Description Adam Hyland 2014-06-06 15:42:19 UTC
Searching for "Wikipedia talk:Articles for creation/2012: A Year Of No Significance ... Colonial Penetrations in the First World - Part 1 in the Sound and Light of India series" (yes, that's the exact title, see here https://en.wikipedia.org/wiki/Wikipedia talk:Articles for creation/2012: A Year Of No Significance ... Colonial Penetrations in the First World - Part 1 in the Sound and Light of India series) results in the following error: 

* "An error has occurred while searching: The search backend returned an error: Internal error in SearchEngine: Trying to extract field from zero-length list of terms"


STR:

1. Paste in "Wikipedia talk:Articles for creation/2012: A Year Of No Significance ... Colonial Penetrations in the First World - Part 1 in the Sound and Light of India series" (without quotes) to the search box and click search/hit enter
2. There is no step 2

I don't know how Cirrus is implemented so I'm not sure what is causing this, though I'd guess it expects `...` as a range operator.
Comment 2 Nik Everett 2014-06-06 16:03:19 UTC
That's a notorious lsearchd error that I've spent a day or two trying to track down only to come up empty handed.  Its probably caching related and probably will go away with time.  I've tried restarting the services to clear that cache in the past but that just causes lsearchd to break across the site and doesn't fix the problem.

Cirrus doesn't spit out any errors when I search with that string but it doesn't find the page because it is deleted.  Searching for <all:Articles for creation/2012: A Year Of No Significance ... Colonial Penetrations in the First World - Part 1 in the Sound and Light of India series> does bring up discussion about it.

Cirrus doesn't use ... as a range operator.  Cirrus's is syntax is documented here: https://www.mediawiki.org/wiki/Search/CirrusSearchFeatures .  Its reasonably up to date.
Comment 3 Nik Everett 2014-06-06 16:04:44 UTC
If you are sure you got the error from cirrus feel free to swap the component back.  I did try it myself and got it on lsearchd and not cirrus.
Comment 4 Adam Hyland 2014-06-06 16:54:48 UTC
Hey Nik,

I'm indeed not sure I got it from Cirrus. Until I convince myself otherwise I'll stick with that change.

As some additional info, it appears that searching for "Wikipedia talk:Articles for creation/2012: A Year Of No Significance ." will also trigger the error, with the minimum case so far being something like 

"Wikipedia:A/b: c ."

Which is still (AFAIK) a valid page name. Interestingly (or maybe not), removing the period returns an error, but it is "An error has occurred while searching: The search backend returned an error:"

HTH,

-Adam
Comment 5 Nik Everett 2014-06-06 16:58:00 UTC
When I've seen these in the past they were based on the search finding a certain results not the query itself.  I could find the code actually throwing the exception but couldn't really do anything about it :(

Unfortunately, I'd suggest checking back in a week and seeing if its still broken.  This is one of the weird bugs that comes up from time to time that made us really want to make cirrus.  As flawed as it is right now we're able to debug it much more easily for a bunch of reasons.  I'm honestly afraid that anything that I do to fix this will break lsearchd more.
Comment 6 Adam Hyland 2014-06-06 17:27:06 UTC
> Unfortunately, I'd suggest checking back in a week and seeing if its still broken.

Can do. 

Dumb question, if I set up a local install on a VM, how would I get at the lucerne errors getting dumped out?
Comment 7 Nik Everett 2014-06-06 17:34:28 UTC
(In reply to Adam Hyland from comment #6) 
> Dumb question, if I set up a local install on a VM, how would I get at the
> lucerne errors getting dumped out?

Setting up lucene search is a bit difficult.  I've actually never gotten it 100% working in a development environment.  I think you are even less likely to get these errors because you'd need to set up replication.....  
Setting up Cirrus is easier and I'll volunteer it here even if it isn't helpful!  Because posterity!

1.  Set this up:  https://www.mediawiki.org/wiki/MediaWiki-Vagrant
2.  vagrant enable-role cirrussearch
3.  vagrant provision


Sorry I couldn't be more help.
Comment 8 Adam Hyland 2014-06-26 21:51:36 UTC
Just a minor update. Searching again for "Wikipedia:A/b: c ." results in the same error. That's not really dispositive as it could be the same caching issue cropping up again, but I said I'd check back later. :)
Comment 9 Chad H. 2014-06-30 19:32:49 UTC
It's an issue the old search is having with punctuation in search queries. It's been like this for weeks (months?) now and I've never managed to run it down. Nothing to do with caching.
Comment 10 Adam Hyland 2014-06-30 21:17:14 UTC
(In reply to Chad H. from comment #9)
> It's an issue the old search is having with punctuation in search queries.
> It's been like this for weeks (months?) now and I've never managed to run it
> down. Nothing to do with caching.

So Nik notes that setting up Lucerne + replication in a development environment will be prohibitively difficult. Is there anything else I can do to help track this down?
Comment 11 Chad H. 2014-10-06 22:46:29 UTC
*** Bug 71722 has been marked as a duplicate of this bug. ***
Comment 12 Chad H. 2014-10-22 20:58:56 UTC
*** Bug 69730 has been marked as a duplicate of this bug. ***

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


Navigation
Links