Arthur Guy wrote: This is a problem with one or more of: * MySQL * operating system * hardware MediaWiki has no direct access to the database files, so any such file corruption problem must necessarily be on the other end. If a one-time event corrupted the files it's possible a REPAIR TABLE isn't quite doing enough. Try dumping and reloading the tables. -- brion vibber (brion @ pobox.com)

-- brion vibber (brion @ pobox.com) I am going to try a better repair this evening when I can shut down the server. I just wanted to make sure the website couldn't be causing the problem; when I repaired the database it seemed fine until I used the website. Chris McIntosh do null edits on the pages to have the indexes rebuilt. How do these maintenance files work, do I just run the "rebuildtextindex.php" in a browser, do I delete/drop the entire table first. Thanks Arthur arthur(a)astarsolutions.co.uk 'a star solutions' disclaimer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this communication

Last night I dropped the search index table and re-created it but then when I attempted to run the rebuild script (from the CLI) it returned the following errors. Warning: Invalid argument supplied for foreach() in ...commandline.inc on line 156 Fatal Error: Call to member function tableName() on a non-object in includes\objectcache.php on line 409 Both of these errors seem to be related to the database name I have looked through the code but I am not really sure what it is doing at these stages. Does anyone know what could be wrong? If I do a null edit on a page the search entry is recreated so the database is working again, I would just like to be able to run the script to rebuild it all. Thanks Arthur arthur(a)astarsolutions.co.uk -----Original Message----- From: mediawiki-l-bounces(a)Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Jamie Bliss Sent: 29 June 2005 04:43 To: MediaWiki announcements and site admin list Subject: Re: [Mediawiki-l] Database Corruption On 6/28/05, Arthur Guy <arthur(a)astarsolutions.co.uk> wrote: nope; it's CLI. For obvious reasons, it can't be ran from the browser (though I have hacked a script to circumvent that for my personal test server, due to PHP CLI issues). -- Jamie ------------------------------------------------------------------- http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB. _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l 'a star solutions' disclaimer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this communication

Thanks for replying, I hadn't filled out the details in adminsettings.php. I created a new database user and put the account details in that file and re-ran the rebuild script, it came back with a message saying the user I had created didn't have permission. I gave the user the following privileges SELECT INSERT UPDATE DELETE INDEX ALTER Are there any other privileges it needs? Thanks Arthur arthur(a)astarsolutions.co.uk -----Original Message----- Make sure AdminSettings.php is present and contains correct username and password settings as per AdminSettings.sample. Note that rebuildIndex.php requires ALTER TABLE permission (iirc) to drop and re-add the fulltext index. -- brion vibber (brion @ pobox.com) 'a star solutions' disclaimer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this communication