Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Sessions.myi Error


raceperformance

Recommended Posts

Almost once a week I get the following error when I check on the store in the morning:

sessions.JPG

 

Does anyone know what causes this, or what the solution is? If I take "mysql" out of the line define('STORE_SESSIONS', ''); in the configuration file, the store works, but with that error at the top saying the the /tmp directory does not exist.

 

Please help.

Link to comment
Share on other sites

I got that once too. I had two computers on and both logged in to admin and using the same password, although I'm not sure that is what caused it.

 

But I fixed it by going to phpMyAdmin, and under the structure tab, clicking on the sessions table box and then at the bottom of that table, where the drop down menu is, selecting "Repair table" from the drop down menu.

 

Hope that helps you...

Link to comment
Share on other sites

  • 11 months later...

I too have been recieving this error a couple times a months for several months now. All I have to do to fix it is do a repair table, but the site is down until I notice it and that makes Mr. Client very unhappy. So, I've got to figure this out soon.

 

Removing mysql from the configure file gives me another error:

Warning: session_start(): open(/tmp\sess_ce087ab0f583fcad91779aeefbb33d8d, O_RDWR) failed: No such file or directory (2) in c:\mysite\includes\functions\sessions.php on line 67

Warning Warning: The sessions directory does not exist: /tmp. Sessions will not work until this directory is created.

 

Also, other users reported upgrading mysql, either the API or to version 4.0.15 solved their problem... any feedback...

 

Also, I think an addition needs to be make to the knowledge base, This Article doesn't say what to do if this is a recurring problem.

Link to comment
Share on other sites

This truly seems to be a recurring problem for a bunch of folks and needs to be addressed with a suggestion for the best fix at the very least.

 

Here's another suggestion from Jim Ekleberry:

If your server is running a verson of mysql > v4.0 then ask your host to add the --myisam-recover = force option to their my.cfg file and that should resolve the problem for you.

 

If your server is running a version of mysql < 4.0 ask your host to upgrade.

 

From this thread

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...