[axxs-sysadmin] severe database corruption problems on indymedia.org.nz

[aketus]

Hey,

I've been helping run the REPAIR TABLE and yes I agree, it's weird  
that it keeps getting corrupted. Unfortunately I don't know why, I  
wondered if it was the way dada handles php to mysql activity, but  
then why would it start playing up now if it didn't in the past.

My other theory: I actually just thought of it then: We recently did a  
MySQL upgrade on axxs. I'm wondering if dada is having trouble  
handling MySQL 4.1. The more I'm thinking about it, the more I think  
this may have something to do with it. I don't recall any of these  
errors occuring prior to MySQL being upgraded.

Good idea with the cron. I was going to write a script that repaired  
all databases when manually run outside of phpmyadmin or terminal, but  
a cron is probably more reliable for the time being.

aketus

Quoting Sebastian <aotearoa at kodeaffe.de>:

> kia ora koutou..
>
> for 1 week or 2, we have a recurrent problem of database corruption.
> we did not change any code that touches database stuff (actually none at
> all until today). we see error messages like:
>
> file not found: articles.MYI
>
>
> or when running mysqlcheck:
>
> nzdada.articles
> warning  : Table is marked as crashed
> error    : Key in wrong position at page 339968
> error    : Corrupt
>
>
> or just now:
>
> Unknown ID Error
>
> Database failed to return a unique record for this query, or you are not
> authorized to access that record.
>
>
> a simple SQL command 'repair table <table name>' or 'mysqlcheck
> --auto-repair' seems to fix it, but only temporarily. i installed a cron
> script today which runs mysqlcheck every 5 minutes.
>
> i am crawling the internet at the moment for possible answers, but
> perhaps any one of you has an idea?
>
> ta,
>  Sebastian
> --
>  _   ascii ribbon campaign     .oOo.   GCSd-s:+aC++ULB+++W++M+PS+++Y+
> ( )
>  X   Jeden Tag eine Erisische Tat!
> / \
>



-- 
aketus