I would suggest a server optimization.

You could raise your timeout's in my.cnf & restart sql.

It doesn't help with you obliterating the table and column calls in that sql, so we cant help you with that. You have probably got a poorly configured server, if you have eAccelerator enabled and you are running SuPHP you will find this simply doesn't work as intended. You'll certainly not see any performance benefits and depending how it's configured, you may find that it actually decreases performance and fills up your "/tmp/eaccelerator" folder with thousands of files. Opcode caching tools only work when running PHP scripts under DSO or similar. So that could be a reason for your server being full.

i rebuild server with out e Accelerator ... i wait to see result ...

As df shows on 12% usage on /tmp, this is not a tmp w/eac issue, the sql error is the problem at this point if it keeps sending out cant connect emails.

Invalid SQL:
SHOW CREATE TABLE postindex;

MySQL Error : Table './iecloob_db/postindex' is marked as crashed and last (automatic?) repair failed
Error Number : 144
Request Date : Thursday, May 10th 2012 @ 07:10:30 PM
Error Date : Thursday, May 10th 2012 @ 07:10:31 PM

--------------- Added [DATE]1336670142[/DATE] at [TIME]1336670142[/TIME] ---------------

Deprecated: Assigning the return value of new by reference is deprecated i

i upgrade php to new version but ... Deprecated ...

Repair the table.

I would suggest you let/hire some one to fix the server correctly.

--------------- Added [DATE]1336670541[/DATE] at [TIME]1336670541[/TIME] ---------------

tables cannot fix .... broweser just send request but no action show !

--------------- Added [DATE]1336670597[/DATE] at [TIME]1336670597[/TIME] ---------------

postindex 0 0 0 !!!! is it clear ?

I would suggest that your stop at this point, do NOT restart mysql at this point.

Repair that table from the cmd line via a shell.

If you cant repair it you'll need to use ssh to find the postindex.TMD file and delete it, when i file is attempting to repair they make another temporary file, if the databse crashes for some reason when this is taking place it leaves that file unfinished, trying to repair again does nothing as that file still exists, i suggest you backup your postindex table as it is then via ssh find that file, delete it, and repair again, you could run the Check table or analyse table first, when you see the full text it will give you the name of the file that already exists.

i can not see tables via php my admin i click it .. it not open just send request

--------------- Added [DATE]1336671252[/DATE] at [TIME]1336671252[/TIME] ---------------

send my commant to do it ... plz