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
Warning: Invalid argument supplied for foreach() in ...commandline.inc on
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
[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:
How do these maintenance files work, do I just run
"rebuildtextindex.php" in a browser, do I delete/drop the entire table
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).
Thank you to JosephM for inviting me to Gmail!
Have lots of invites. Gmail now has 2GB.
MediaWiki-l mailing list
'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
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