"ezsession is marked as crashed and should be repaired"

Monday 18 September 2006 11:13:54 am

Hi,
while toggling my harddrive with the szpublish installation between several computers, I must have made something wrong. Now I get the following MYSQL-error while trying to login in the admin interface. Logging in turns out to be impossible, the system always shows the same login page (admin siteaccess). The other siteaccesses aren't accessible as well.

Is there a way to reset the session manually without a browser?

060918 18:45:15 [ERROR] mysql\bin\mysqld: Table '.\myezp\ezsession' is marked as crashed and should be repaired
...
060918 18:45:16 [ERROR] mysql\bin\mysqld: Table 'ezcontentobject_version' is marked as crashed and should be repaired
060918 18:45:16 [ERROR] mysql\bin\mysqld: Sort aborted
060918 18:45:16 [ERROR] mysql\bin\mysqld: Table '.\myezp\ezsession' is marked as crashed and should be repaired
...

Monday 18 September 2006 1:04:18 pm

Thanks, Claudia.
I made a copy of the mysql database.
I dropped ezsession and had still an error concerning ezcontentobject_version.
I dropped ezcontentobject_version.

Now I don't get any errormessages from MYSQL, but I still get no access to my site anymore...

Is it lost forever...?

Monday 18 September 2006 2:30:28 pm

Hi Ulrich,

As Claudia said, dropping ezsession is not much of a problem but dropping ezcontentobject_version was probaly not a good idea so I think your backup might come in handy :)

One easy way to repair your tables, is to use the tools shipped with mysql:

~ # mysqlrepair -A -e -v --auto-repair -p

Issuing this as root will prompt for the root password (-p) of your database instance and then do an extended (-e) check and automagically repair (--auto-repair) of all (-A) tables in the database, verbosley (-v) showing what is happening.

If you don't want to do it from the commandline but have access to phpMyAdmin then you can mark all tables in the database you have trouble with and select 'repair'. This will then do almost the same as above.

...and as always. Don't forget to take backups of all your databases before you do anything of this. :)