Page MenuHomePhabricator

on bug submit: Incorrect key file for table './bugzilla/bugs_fulltext.MYI
Closed, ResolvedPublic


Software error:

DBD::mysql::db do failed: Incorrect key file for table:


try to repair it

[for Statement "UPDATE bugs_fulltext SET comments = ?, comments_noprivate = ? WHERE bug_id = ?"] at Bugzilla/ line 1091
Bugzilla::Bug::_sync_fulltext('Bugzilla::Bug=HASH(0x3f4c0f0)', 'update_short_desc', undef, 'update_comments', 'ARRAY(0x4294a08)') called at Bugzilla/ line 1023
Bugzilla::Bug::update('Bugzilla::Bug=HASH(0x3f4c0f0)') called at /srv/org/wikimedia/bugzilla/process_bug.cgi line 366
For help, please send mail to the webmaster (, giving this error message and the time and date of the error.

Version: wmf-deployment
Severity: normal



Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:23 AM
bzimport set Reference to bz65762.
bzimport added a subscriber: Unknown Object (MLST).

Happened on a few bugs this morning. The last one was adding a comment and resolving . The change went in just fine though.

Giuseppe "_joe_" Lavagetto repaired table bugzilla.bugs_fulltext on db1001 as it was marked as crashed

Urgh. Thanks for quickly handling this. :-/

Gerrit Notification Bot changed status in bug 65677 without previously inserting the comment with the link to the Gerrit change, as usual.

Upstream closed as INVALID:

Oh, I now see the outage thread on ops@ (outage 2014-05-26 08:30:25). Alright.

The table being crashed, that prevented the Gerrit bot comment to be submitted though the status (i.e. NEW -> PATCH_TO_REVIEW) would.