jos_session is marked as crashed and should be repaired

[Tintu_89]

why this error happens? how can i solve this permanently?..

plzz help me..

Thanks..

[micheas]

The problem: mysql crashed, had the power pulled, etc, while it was writing a cookies session data to jos_session.

The immediate solution: go to your mysql admin program (phpmyadmin, or open mysql on the command line) and run the following command:

Code: Select all

repair table jos_session;

Possible permanent solutions:
move the database to a server that won't go down unexpectedly (the best and most expensive solution)

write a script that checks if the tables are crashed and try and auto repair them if so.

move the session cookies from the database to the file system. (less secure, does not scale as well, gives better performance for small sites however.)

[seoras]

This has started happening to my web site.
It's not a power outage that causing it.

This I'm sure of because I left 3 ssh sessions connected to the server from my Mac and the problem happened again last night.
All 3 sessions are still running so safe to assume no restart/reboot

It's happened twice now in 2 weeks and the first time it happened was when my site got a (brief) jump in Google ranking and doubled it's normal traffic load.

Any suggestions?

Is this a joomla bug or an SQL bug?

Joomla 1.5.15
PHP 5.2.6-1+lenny16
MySQL 5.0.51a-24+lenny5

[Codeless]

Having the same problem here with one of the sites, whenever my server crashes or needs to restart it throws up this error. Repairing the table works great. But I need to find a way to prevent this from happening. Of course not having the server crash is step number 1, which I've upgraded it's hardware in hopes that won't happen anymore. But its strange that only one of my sites gives this error (the one with the highest traffic) when the sever restarts. Other Joomla 2.5 and 3.0 sites on the same server don't give this error upon restart.

I have checked configuration.php and it does have my table's prefix in it.

My hosting company says I have to upgrade my PHP/SQL. But whenever I do that with Joomla always some extension stops working, so I'm trying to remain on my current PHP version (PHP 5.3.28). And I don't think upgrading will really fix anything.

I've done a lot of research and it's quite the popular Joomla error without any definitive solution. Hopefully a few of us can put our heads together and solve this problem once and for all.

Cheers!

PS - does anyone know a way to set a cron task or something to automatically repair the table so if it does go down again it'll be automatically fixed? Or is that also dangerous behavior?

[micheas]

The way to prevent this is to configure Joomla to store sessions in the file system instead of the database.

[Codeless]

Thanks for your help micheas. How would one accomplish this? And as you said before, it's less secure, does not scale as well, gives better performance for small sites however... my site is very large, so not sure about this as a solution...