/mybb_sessions' is marked as crashed and should be repaired
Query:
SELECT * FROM mybb_sessions WHERE sid='fbe27883c89d52578f978790a31101ce' AND ip='171.4.251.14' LIMIT 1
Need rapid help on this. Did not make any changes and just got this...
Goto ACP if you can
Goto Tools & Maintenence in ACP
Click Repear Database Tables...
If you cant accesss ACP, you may be out of luck...
There is no option for 'repair' in acp.
"You may be out of luck." Lol. Man. Stick to your day job, and stay away from any type of medical field work.
Okay. Did repair from cpanel. Now good to go
Can anyone guess as to why this happened?
Hosting had about 20 minutes prior to the error changed something with haproxy. Could this have caused the issue, or any other ideas?
Regards
(2014-07-12, 04:57 PM)DrXotick Wrote: [ -> ]There is no option for 'repair' in acp.
"You may be out of luck." Lol. Man. Stick to your day job, and stay away from any type of medical field work.
Okay. Did repair from cpanel. Now good to go
Can anyone guess as to why this happened?
Hosting had about 20 minutes prior to the error changed something with haproxy. Could this have caused the issue, or any other ideas?
Regards
Glad to hear you fix it, I did make a slight error, so future reference for corrupted tables:
1) Login to ACP
2) Goto Tools & Maintenance
3) Goto Task Manager
4) Manually run the task Table Check
Well could be for many reasons, such as running a faulty query, or disableing a plugin!
Do you use free hosting btw?
No. Not free hosting.
The specific error is mentioned. I made no changes to the site other than what was mentioned above. The host made changes to haproxy because of another issue. Site worked fine for awhile, then this.
(2014-07-13, 02:46 AM)DrXotick Wrote: [ -> ]No. Not free hosting.
The specific error is mentioned. I made no changes to the site other than what was mentioned above. The host made changes to haproxy because of another issue. Site worked fine for awhile, then this.
Thats really odd, because its a session error aka getting a session from your cookies.
It happened because the MySQL server had an 'unclean' shutdown, it may've crashed or the server was rebooted or something to that effect. Usually when you shut down MySQL it'll finish up whatever it is doing then close, but if it crashes or is rebooted before it finishes up then you can end up with tables that aren't written properly (your 'crashed' table). Generally running repair through your control panel will fix it.
Because the sessions table is written to on every page load it has the highest chance of ending up crashed through an unclean shutdown.