Last modified: 2010-05-15 15:33:36 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 3168 - Major database query error when viewing article
Major database query error when viewing article
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
PC Windows XP
: High critical (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-08-16 22:49 UTC by admin
Modified: 2010-05-15 15:33 UTC (History)
0 users

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


Description admin 2005-08-16 22:49:30 UTC
When trying to view the page
[] and
others on the same MediaWiki ([[]]) I
get an error similar to the following:

'''' A database query syntax error has occurred. This may indicate a bug in the
software. The last attempted database query was:

    (SQL query hidden)

from within function "MediaWikiBagOStuff:_doquery". MySQL returned error "1030:
Got error 134 from table handler (localhost)".''''

The site has been working fine until now and I cannot isolate what has caused
the bug. It only occurs on certain pages and I cannot find any continuity
between them.

Editing the page works entirely, it is merely viewing the article that causes
the error. Other users have encountered the same problem, using the latest IE
and Firefox browsers. The server recently ran an 'infinite loop' script which
slowed the server down tremendously about the same time this happened and may
have contributed to whatever has happened.
Comment 1 Brion Vibber 2005-08-17 00:45:56 UTC
When you encounter MySQL errors, please remember to look up the error number. This can be done with 
the 'perror' command-line utility:

$ perror 134
MySQL error:  134 = Record was already deleted (or record file crashed)

So, you should probably run REPAIR TABLES on your tables.
Comment 2 admin 2005-08-17 12:52:39 UTC
ah thank you. I don't have command line access to the server, but running a
horde of REPAIR QUICK statements did fix it.

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