SamyT Posted October 23, 2007 Share Posted October 23, 2007 G'day - I simply navigated to a page on my website the other day and up came a big white screen with a database error - to do with sessions and sesskey. To fix I had to repair the sessions table. That fixed it for about two minutes and I had to contact my host. He suggested just restarting the system after repairing the table and that seemed to do the trick. A week later I am in one of my orders status pages and I get the error again! I've repaired the sessions table and rebooted the VPS, so it's fixed for the moment, but is there any better way? There may not always be someone in the business who knows how to do this kind of thing, I'm worried how they will deal with this sort of stuff so would like to minimize this sort of problems. Does anyone have a solution? Link to comment Share on other sites More sharing options...
Guest Posted October 23, 2007 Share Posted October 23, 2007 Most likely your host it is "messing up" with too many connections to your dbase.Make shure to back-up the dbase and drop the table.Then import back and that should cure.Back -up in proper format.I would recommend to back-up trough the admin in osc and again trough the cpanel at your host( admin myphp).When you exporting thosugh your host admin make shure that proper format is selected( not default) for mysql version.I had to disable the "whos online" because the host could not handle the dbase connection and was shutting down my web site.The radical option is to change to dedicated server. Link to comment Share on other sites More sharing options...
Guest Posted October 23, 2007 Share Posted October 23, 2007 Most likely your host it is "messing up" with too many connections to your dbase.Make shure to back-up the dbase and drop the table.Then import back and that should cure.Back -up in proper format.I would recommend to back-up trough the admin in osc and again trough the cpanel at your host( admin myphp).When you exporting thosugh your host admin make shure that proper format is selected( not default) for mysql version.I had to disable the "whos online" because the host could not handle the dbase connection and was shutting down my web site.The radical option is to change to dedicated server. Check that persitent connections (pconnect) in the configure.php files is set to false. Link to comment Share on other sites More sharing options...
SamyT Posted October 23, 2007 Author Share Posted October 23, 2007 Hi, I checked the persistent connections thing and it was set to true - I changed it to false, now I find I am getting this error when working with products in my database: 1030 - Got error 127 from table handler delete from sessions where expiry < '1193178096' [TEP STOP] Link to comment Share on other sites More sharing options...
SamyT Posted October 23, 2007 Author Share Posted October 23, 2007 By the way, I didn't mean to ignore you jesphoto, it's just that my entire database is over 30mb and the system has frozen and crashed when trying to restore in the past - I'd really prefer not to have to do that as it would take hours to fully get it all back into the database. Link to comment Share on other sites More sharing options...
Nullachtfuffzehn Posted October 24, 2007 Share Posted October 24, 2007 The most common method to fix the error mentioned above is to repair the table. Should work again then. Link to comment Share on other sites More sharing options...
SamyT Posted October 24, 2007 Author Share Posted October 24, 2007 Repairing the table works for a short time only - I've seen the same thing said by other people having this problem. Immediately the error is gone.. then after a short while, it's back. Link to comment Share on other sites More sharing options...
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.