Last modified: 2010-05-15 15:34:02 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 1626 - searchindex.MYI gets corrupt
searchindex.MYI gets corrupt
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
1.4.x
PC Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-03-03 12:52 UTC by Stefan Pausch
Modified: 2010-05-15 15:34 UTC (History)
0 users

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


Attachments

Description Stefan Pausch 2005-03-03 12:52:20 UTC
CPU: AMD64 
PHP: 5.3
MySql: 4.1.9
System: Suse Linux 9.1
Tableprefix: wiki_

For some reasons the wiki_searchindex.MYI file gets corrupt and can't accessed anymore. The File itself exists. If i 
view it in phpmyadmin the table self is shown as "in use". (Maybe the table is locked and for some reasons isn't 
unlocked after processing). I discovered this "bug" the second time now. First time right after installation.

Errormessage from logfile: 
SearchUpdate::doUpdate 1016 Can't open file: 'wiki_searchindex:MYI' (errno: 145)
Comment 1 Domas Mituzas 2005-03-03 12:53:42 UTC
This is a bug of MySQL engine or a host running it. No application (mediawiki
either) would be able to work directly with that file. You can try fixing your
tables with 'REPAIR TABLE'. 
Comment 2 Paul N 2005-08-09 23:42:59 UTC
The below was a dialog with a support person at my hosting company.  I have been
having this problem repeatedly.   It will show up when editing a page or doing a
search.   This is the third time I have had to have them repair the table.  Any
ideas or further information you may or maynot need?

The problem was a corrupted .MYI file (bang_searchindex.MYI). Generally when you
see 'Can't open file:' errors, that's the cause. I'd say since this seems to be
reoccurring on the same script that there's something not quite right with the
queries the script is using, but I can't be more specific than that. It might
potentially be a mysql version issue, so if it helps any the mysqld version on
this server is 4.0.24.

Thanks!
Support

==( Ticket Thread #[ 85094 ] Summary )===========================[ BEGIN ]
Username, *******
Request, problem again.<br>an issue with a db error keeps popping up.  at first
it showed up during page updates, but now it shows up on searches.  please try a
search on the
site...<br>http://www.bayareanightgame.com<br><br>http://www.bayareanightgame.com/index.php/Special:Search?search=something&go=Go<br><br>the
error should say...<br> A database query syntax error has occurred. This may
indicate a bug in the software. The last attempted database query was:<br><br> 
  (SQL query hidden)<br><br>from within function ''. MySQL returned error '1016:
Can't open file: 'bang_searchindex.MYI'. (errno: 145) (localhost)'.<br><br><br>I
have researched this on the mediawiki site, and they say that it is a db error.
 please advise, and if there is a solution, please include what that is in your
fix / reply. <br><br>fyi, this is the second time i have reported this.<br>
=====================================================================[ END ]
Comment 3 Brion Vibber 2005-08-11 06:26:28 UTC
MySQL error:  145 = Table was marked as crashed and should be repaired

This means that MySQL crashed or was shut down improperly while the table was open.
No error in MediaWiki could possibly cause this -- it is either a bug in MySQL, a bug in
the operating system that the database server is running on, or improper maintenance
of the database server (unclean shutdowns, or hardware errors causing crashes).

You need to ask your host to check their MySQL error log for problems, such as crashes
(MySQL normally restarts itself if the server daemon itself crashes, and they might not
be noticing until someone reports an error).

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


Navigation
Links