"ezsession is marked as crashed and should be repaired"

Next topic

Author	Message
Ulrich L.	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 ...
Claudia Kosny	Monday 18 September 2006 12:08:45 pm Hi Ulrich Did you by any chance remove your usb device without logging it off from the system? The some data might still have been in the cache and not written to the table which might have caused this error. Anyhow - to access the database I would install PHPMyAdmin on the sever - if you use xampp you most likely have it anyway. If repairing does not help, just drop this table and create it new - I don't think that the ezsession table holds any relevant information. Greetings from Luxembourg Claudia
Ulrich L.	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...?
Claudia Kosny	Monday 18 September 2006 1:21:03 pm Hi Ulrich I think dropping ezcontentobject_version was a bad idea. The table ezsession holds afaik only session data, thus is is not incredibly important whereas ezcontentobject_version holds permanent data which is important for maintaining the objects. Hopefully I am wrong but I don't think you can recreate this data if the table is so corrupted that it cannot be repaired. What happened when you tried to repair the table? Do you get any error messages at all now? Claudia
David Boman	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. :)
Ulrich L.	Tuesday 19 September 2006 12:35:53 am Thanks, David. I tried to repair the two tables, using phpadmin. Having that done, I could access my siteaccess again (admin). However, I could only see the root node of the content tree, all the other content was gone...Behaviour was strange (couldn't access class management). Perhaps it's better to downgrade to an older backup... Hmmm.... Or still any other ideas?