PleskMainDBException...help, I'm sooo lost

[scott]

try repairing the tables? REPAIR TABLE TABLENAME;

[wegngis]

All of them? And should I repair them from a bash prompt, or is phpmyadmin sufficient?

[breun]

You could run this to repair all repairable problems in all databases with a single command:

Code: Select all

mysqlcheck --repair --all-databases -uadmin -p`cat /etc/psa/.psa.shadow`

See here for more info on the mysqlcheck command. Using the REPAIR TABLE command from within mysql or using phpMyAdmin should work as well though.

[wegngis]

Running the command as you suggested yielded some interesting results.

psa.BackupTasks
note : The storage engine for the table doesn't support repair

I got that for 90% of the psa tables (about 5 returned 'OK'). If I run the --analyze option, those 5 tables returned the following:

Table is already up to date

The rest say 'OK'

[breun]

Oh yes, the psa db uses the InnoDB storage engine and mysqlcheck doesn't support repairing InnoDB tables apparently. Try using the CHECK TABLE and REPAIR TABLE commands directly.

Have you tried restoring the psa db once more?

[wegngis]

Such as this?

Code: Select all

mysql> check table BackupTasks;
+-----------------+-------+----------+----------+
| Table           | Op    | Msg_type | Msg_text |
+-----------------+-------+----------+----------+
| psa.BackupTasks | check | status   | OK       |
+-----------------+-------+----------+----------+
1 row in set (0.01 sec)

mysql> repair table BackupTasks;
+-----------------+--------+----------+---------------------------------------------------------+
| Table           | Op     | Msg_type | Msg_text                                                |
+-----------------+--------+----------+---------------------------------------------------------+
| psa.BackupTasks | repair | note     | The storage engine for the table doesn't support repair |
+-----------------+--------+----------+---------------------------------------------------------+
1 row in set (0.00 sec)

As for restoring the psa db once more, do you mean taking a different daily dump, restoring the db two times in a row (which, come to think of it, prob won't work) or just trying it on a different occasion? I have restored it twice now since Plesk was hosed upon reboot.

[breun]

Since CHECK TABLE says it's OK, I guess there's nothing to repair. But I to admit I don't know how to repair an InnoDB table then.

Yes, I meant just doing the restore on a different occasion. Restoring the db fixes your problem, but on reboot it is hosed again? Every time?