View Single Post
Career Officer
Join Date: Jun 2012
Posts: 1,474
# 1964
11-10-2012, 05:49 AM
Quote:
Originally Posted by senshibat01 View Post
when i hit social tabs this

MyBB has experienced an internal SQL error and cannot continue.

SQL Error:
145 - Table './itescom_mybb/mybb_posts' is marked as crashed and should be repaired
Query:
SELECT tid,uid FROM mybb_posts WHERE uid='10' AND tid IN (261,223,478,179,594,595,363,67,571,251,44,579,507 ,43,492,576,593,50,146,133) AND visible='1'

when i hit thread of approval

MyBB has experienced an internal SQL error and cannot continue.

SQL Error:
145 - Table './itescom_mybb/mybb_posts' is marked as crashed and should be repaired
Query:
SELECT pid FROM mybb_posts WHERE tid=478 AND visible='1' ORDER BY dateline DESC LIMIT 0, 1

when i hit my silly thread this

MyBB has experienced an internal SQL error and cannot continue.

SQL Error:
145 - Table './itescom_mybb/mybb_posts' is marked as crashed and should be repaired
Query:
SELECT pid FROM mybb_posts WHERE tid=260 AND visible='1' ORDER BY dateline DESC LIMIT 0, 1


COMM NEWS

MyBB has experienced an internal SQL error and cannot continue.

SQL Error:
145 - Table './itescom_mybb/mybb_posts' is marked as crashed and should be repaired
Query:
SELECT tid,uid FROM mybb_posts WHERE uid='10' AND tid IN (105,46,495,587,385,572,543,527,522,509,485,383,44 3,427,370,358,168,351,328,288) AND visible='1'


so basicaly cant get into anything and by the post dates time it looks like it locked up about in around prior to 1051 board time so noones posted there since

When i hit view todays post search this crash error shows
MyBB has experienced an internal SQL error and cannot continue.

SQL Error:
145 - Table './itescom_mybb/mybb_posts' is marked as crashed and should be repaired
Query:
SELECT DISTINCT tid,uid FROM mybb_posts WHERE uid='10' AND tid IN(478,260,179,105,594,595,363,67)
It appears the whole database has crashed. Just like in Cappy's thread. Momo said she was going to look into it. I have no clue where these repair commands are but I did look for them. The only thing I could find was a check tool and that stated that there were no currupt files. If it's correct, I'm guessing I'm looking in the wrong place. Hopefully it will be back up and running by the end of the day.