Mailing List Archive

> (Brion Vibber <brion@pobox.com>):
> On Thu, 2003-05-08 at 02:49, Andre Engels wrote:
> > When searching on WikipediaNL, I get the following error message:
> >
> > "1016: Can't open file: 'searchindex.MYI'. (errno: 145)".
>
> Fulltext indexes need to be rebuilt for mysql 4, IIRC...

English is done. I also had to restart mysqld after setting tempdir
to /usr/local/mysql/tmp, because /tmp didn't have enough space to
rebuild the index. I'll start on the others after I get up in the
morning.

--
Lee Daniel Crocker <lee@piclab.com> <http://www.piclab.com/lee/>
"All inventions or works of authorship original to me, herein and past,
are placed irrevocably in the public domain, and may be used or modified
for any purpose, without permission, attribution, or notification."--LDC

On Thu, 2003-05-08 at 02:49, Andre Engels wrote:
> When searching on WikipediaNL, I get the following error message:
>
> "1016: Can't open file: 'searchindex.MYI'. (errno: 145)".

Fulltext indexes need to be rebuilt for mysql 4, IIRC...

-- brion vibber (brion @ pobox.com)

On Thu, 2003-05-08 at 03:05, Lee Daniel Crocker wrote:
> > (Brion Vibber <brion@pobox.com>):
> > Fulltext indexes need to be rebuilt for mysql 4, IIRC...
>
> English is done. I also had to restart mysqld after setting tempdir
> to /usr/local/mysql/tmp, because /tmp didn't have enough space to
> rebuild the index. I'll start on the others after I get up in the
> morning.

Great. In the meantime, I'm just running a "repair table searchindex" on
the ones that are coming up with errors.

-- brion vibber (brion @ pobox.com)

--- Kurt Jansson <jansson@gmx.net> wrote:
> I'm getting this error message in the German
> Wikipedia:


errr....seconded on the french

Erreur de syntaxe dans la base de données. Cette
erreur peut être causée par une requête de recherche
incorrecte (voir Chercher dans Wikipédia), ou une
erreur dans le logiciel. La dernière requête traitée
par la base de données était :

SELECT cur_id,cur_namespace,cur_title,cur_text FROM
cur,searchindex WHERE cur_id=si_page AND ( (MATCH
(si_title) AGAINST ('résonance')) AND (MATCH
(si_title) AGAINST ('magnétique')) AND (MATCH
(si_title) AGAINST ('nucléaire')) ) AND cur_namespace
IN (0) LIMIT 0, 20
depuis la fonction "SearchEngine::showResults".
MySQL a renvoyé l'erreur "1016: Can't open file:
'searchindex.MYI'. (errno: 145)".

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

I'm getting this error message in the German Wikipedia:


Es gab einen Syntaxfehler in der Datenbankabfrage. Das könnte eine
illegale Suchanfrage sein (siehe Wikipedia durchsuchen), oder ein
Softwarefehler. Die letzte Datenbankabfrage lautete:

SELECT cur_id,cur_namespace,cur_title,cur_text FROM cur,searchindex
WHERE cur_id=si_page AND ( (MATCH (si_title) AGAINST ('test')) ) AND
cur_namespace IN (0) LIMIT 0, 50

aus der Funktion "SearchEngine::showResults". MySQL meldete den Fehler
"1016: Can't open file: 'searchindex.MYI'. (errno: 145)".

Erreur base de données

Pour la requête "picomètre"

Erreur de syntaxe dans la base de données. Cette erreur peut être causée
par une requête de recherche incorrecte (voir Chercher dans Wikipédia
<http://fr.wikipedia.org/wiki/Wikip%E9dia:Recherche>), ou une erreur
dans le logiciel. La dernière requête traitée par la base de données
était :

SELECT cur_id,cur_namespace,cur_title,cur_text FROM cur,searchindex
WHERE cur_id=si_page AND ( (MATCH (si_title) AGAINST ('picomètre'))
) AND cur_namespace IN (0) LIMIT 0, 20

depuis la fonction "SearchEngine::showResults". MySQL a renvoyé l'erreur
"1016: Can't open file: 'searchindex.MYI'. (errno: 145)".

On Sun, 2003-05-11 at 09:23, Kurt Jansson wrote:
> I'm getting this error message in the German Wikipedia:
>...
> aus der Funktion "SearchEngine::showResults". MySQL meldete den Fehler
> "1016: Can't open file: 'searchindex.MYI'. (errno: 145)".

Hmm, I'll run a REPAIR TABLES again...

Jason, I'm wondering if MySQL is getting shut down properly on reboot;
it's conceivable that that could corrupt the index files.

Next time you reboot it (when not crashed ;) try running a
"mysqladmin -u root -p shutdown" before shutting the machine down. If
that doesn't help, it's probably some weirdness with the MySQL 4
upgrade.

-- brion vibber (brion @ pobox.com)

I don't know if this is related to the other searching problems,
but when the "Go" and "Search" buttons were swapped, some
strange behavior was introduced. "Go" works fine, but
"Search" doesn't. Two problems:

1. An extraneous "search" value in the query is created.
For example, typing "George Mason" and pressing search should try to
GET http://www.wikipedia.org/w/wiki.phtml?search=George+Mason
but instead it tries to GET
http://www.wikipedia.org/w/wiki.phtml?search=George+Mason&search=Search
(note that "search=" appears twice).
Which means you can only search for the word "Search" :-).

2. Even if you hand-fix the search, the title search doesn't work
at all, nor is there any hint that the search wasn't performed.
It should either do a title search (that's not expensive), or
at least say "No title search performed, server too overwhelmed".

I hope that's clear..!

On Mon, 12 May 2003, David A. Wheeler wrote:
> 1. An extraneous "search" value in the query is created.

Oops, fixed.

> 2. Even if you hand-fix the search, the title search doesn't work
> at all, nor is there any hint that the search wasn't performed.
> It should either do a title search (that's not expensive), or
> at least say "No title search performed, server too overwhelmed".

Jeebus, how many more disclaimers do I have to put into that thing?

-- brion vibber (brion @ pobox.com)

Brion - thanks for fixing the "search" button.

I said:
> > 2. Even if you hand-fix the search, the title search doesn't work
> > at all, nor is there any hint that the search wasn't performed.
> > It should either do a title search (that's not expensive), or
> > at least say "No title search performed, server too overwhelmed".

Brion Vibber <vibber@aludra.usc.edu> replied:
>
> Jeebus, how many more disclaimers do I have to put into that thing?

You don't need MORE disclaimers. I think part of the problem is
that the text labelled "Results:" above the disclaimer makes it
appear that the disclaimer is irrelevant.
The current display looks like the system _did_ do a
search, with null results. It's then followed by some sort of
disclaimer, saying that sometimes searching is disabled
(during your peak hours). But since I got search results,
clearly it's not your peak hours and searching is currently
enabled. At least, that's what I thought the Wikipedia meant.
Apparantly that's not what was meant.
At least, I find it very confusing, and I suspect others will too.

When searching is disabled, I believe Wikipedia should
NOT display the following text:
"Showing below 20 results starting with #1.
View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)."
Instead, it should IMMEDIATELY display the disclaimer, and _explicitly_
state that searching is CURRENTLY disabled. How about this?:
"Sorry, but searching is currently disabled.
Wikipedia's internal search capability is disabled during
peak hours (16:00-04:00 UTC / 9:00-17:00 PDT) to reduce
server strain. As a temporary measure, you can search for
text appearing in Wikipedia pages via Google, but be aware that
the index is incomplete and some pages will be out of date.
If you know the exact name of the article, just enter the title's
name and press the 'Go' button at the top right side of the display."

If title searching is being disabled - and not just article title
searching - I think the disclaimer should say that "text search"
is disabled, not "full-text search" (as I've shown above).
Some people (including me!) would presume "full-text search" to mean
searching inside every single article's body, and wouldn't think
that "title search" is the same as "full-text search".

If my understanding is right, this isn't really a "bug" -
it's a user interface issue. I think the current
text could confuse some people (it's certainly confusing me).
By NOT displaying potentially confusing information,
I think it'd be better.

Anyway, I hope I caused no offense. I really appreciate the
work you do!

Sounds good... Also sounds somewhat forgettable, so apologies ahead
of time if I forget.

Just curious: Why don't we use the /etc/rc.d/init.d scripts for
startup and shutdown of apache and mysql? apachectl itself can be
used as an init.d init script, and I imagine that the mysql
distribution came with one as well.

Jason

Brion Vibber wrote:

> On Sun, 2003-05-11 at 09:23, Kurt Jansson wrote:
> > I'm getting this error message in the German Wikipedia:
> >...
> > aus der Funktion "SearchEngine::showResults". MySQL meldete den Fehler
> > "1016: Can't open file: 'searchindex.MYI'. (errno: 145)".
>
> Hmm, I'll run a REPAIR TABLES again...
>
> Jason, I'm wondering if MySQL is getting shut down properly on reboot;
> it's conceivable that that could corrupt the index files.
>
> Next time you reboot it (when not crashed ;) try running a
> "mysqladmin -u root -p shutdown" before shutting the machine down. If
> that doesn't help, it's probably some weirdness with the MySQL 4
> upgrade.
>
> -- brion vibber (brion @ pobox.com)



--
"Jason C. Richey" <jasonr@bomis.com>