Nekochan Net

wiki database error

sybrfreq
Old Salt
Who joined Aug. 21, 2007, 10:12 p.m.
and authored 1647 notes

Wrote the following at Jan. 16, 2010, 11:20 p.m...

wanted to do some reading on this old sgi, but I think I broke the wiki. :oops:

http://www.nekochan.net/wiki/index.php? ... is+old+sgi

in my infinite wisdom I thought maybe "this" is some keyword so tried:
http://www.nekochan.net/wiki/index.php? ... +sgi&go=Go

which results in the same thing, tried in srware iron and internet explorer 8 and even deleted all the settings in ie8 and tried again. each time I get this error:

Code:

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 "". MySQL returned error "145: Table './wikidb/searchindex' is marked as crashed and should be repaired (localhost)".

although searching "onyx" for example does take me to the onyx page.

maybe growing pains with the new server? or is neko already fixing it...

_________________

(Aldebaran)

(Chaos)

(Machop)
:hp xw9300: (Aggrocrag) :hp dv8000: (Attack)

recondas
Moderator
Who joined June 6, 2004, 5:55 p.m.
and authored 3378 notes

Wrote the following at Jan. 17, 2010, 5:21 a.m...

Until neko's had the opportunity to look into this, would *everyone* please avoid the wiki search tool.

sybrfreq -for now here's a direct link to the "This Old House" wiki - http://www.nekochan.net/wiki/index.php/This_Old_SGI

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

nekonoko
Site Admin
Who joined Jan. 23, 2003, 2:31 a.m.
and authored 7591 notes

Wrote the following at Jan. 17, 2010, 6:47 a.m...

Fixed

_________________
私のホバークラフトは鰻が一杯です。
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.

squeen
Moderator
Who joined May 9, 2003, 6:10 a.m.
and authored 2895 notes

Wrote the following at Jan. 18, 2010, 6:42 a.m...

What was the fix?

nekonoko
Site Admin
Who joined Jan. 23, 2003, 2:31 a.m.
and authored 7591 notes

Wrote the following at Jan. 18, 2010, 10:41 a.m...

squeen wrote:

What was the fix?

Code:

# myisamchk --silent --force --fast --update-state searchindex.MYI

myisamchk: MyISAM file searchindex.MYI

myisamchk: warning: Table is marked as crashed

myisamchk: warning: 2 clients are using or haven't closed the table properly

# php rebuildall.php

** Rebuilding fulltext search index (if you abort this will break searching; run this script again to fix):

Dropping index...

Rebuilding index fields for 1992 pages...

1500

Rebuild the index...

** Rebuilding recentchanges table:

Loading from page and revision tables...

$wgRCMaxAge=604800 (7 days)

Updating links and size differences...

Loading from user, page, and logging tables...

Flagging bot account edits...

Flagging auto-patrolled edits...

** Rebuilding links tables -- this can take a long time. It should be safe to abort via ctrl+C if you get bored.

Refreshing links table.

Starting from page_id 1 of 1992.

100

200

300

400

500

600

700

800

900

1000

1100

1200

1300

1400

1500

1600

1700

1800

1900

Done.

It's the only MyISAM table I'm still using; I moved nearly everything to InnoDB years ago to prevent splats like that.

That table may have been marked as crashed before the server move - there was a power outage a couple weeks ago that dropped the O350 on its butt (another advantage of a smaller system is I can keep it up on a UPS nearly indefinitely). If it happens again for some reason I'll see about moving that table to InnoDB as well.

Edit: Bummer. According to the MediaWiki docs, the searchindex has to be MyISAM. Guess that's why I left it that way

Interestingly, I found this via Google:

Quote:

TODO: MediaWiki’s MySQL search backend
Some problems and solutions…

...

Problem 2: The table crashes sometimes

People often get mystified when the searchindex table is marked crashed.

Catch the error: try a REPAIR TABLE transparently, and display a friendlier error if that fails.

...

... this is apparently a known issue.

squeen
Moderator
Who joined May 9, 2003, 6:10 a.m.
and authored 2895 notes

Wrote the following at Jan. 19, 2010, 4:14 a.m...

Hmm. I'll have to keep on eye on ours.
Thanks for sharing that.

nekonoko
Site Admin
Who joined Jan. 23, 2003, 2:31 a.m.
and authored 7591 notes

Wrote the following at Jan. 19, 2010, 11:28 a.m...

Not a problem! I wouldn't worry about it too much - the searchindex is a throw-away table in that it can be regenerated from scratch in just a few seconds using the 'rebuildall' script. It's not critical by any means.