Repairing the DB after upgrade to 7.64 returns a blank page

📦 Install & Upgrade Help
1

Hi,

I have just upgraded from v.7.5.3 to v.7.6.4. Having completed the ugrade successfully I tried to perform a ‘quick repair and rebuild’.

The results returned differences found between database and vardefs so I executed the changes as requested. This action returns a blank page.

Running the quick repair again shows that the DB and vardefs have not been synced.

Sugarlog shows the following:

AND jt1.deleted=0 where (schedulers.status=‘Active’ AND NOT EXISTS(SELECT id FROM job_queue WHERE scheduler_id=schedulers.id AND status!=‘done’)) AND schedulers.deleted=0: MySQL error 145: Table ‘./db_name/job_queue’ is marked as crashed and should be repaired
Sun Jun 12 13:13:02 2016 [4910][1][FATAL] Query Failed: SELECT id FROM job_queue WHERE execute_time <= ‘2016-06-12 12:13:02’ AND status = ‘queued’ ORDER BY date_entered ASC LIMIT 0,1: MySQL error 145: Table ‘./db_name/job_queue’ is marked as crashed and should be repaired
Sun Jun 12 13:13:02 2016 [4910][1][FATAL] Get One Failed:SELECT id FROM job_queue WHERE execute_time <= ‘2016-06-12 12:13:02’ AND status = ‘queued’ ORDER BY date_entered ASC: MySQL error 145: Table ‘./db_name/job_queue’ is marked as crashed and should be repaired

Can anyone please advise as to what the problem might be and possible solution?

Many thanks,

2

Maybe you should consider going back to a previous point in time by using a backup or a Virtual machine snapshot, if you have them (I always snapshot before upgrades, just in case).

It seems something got corrupted in your database. I googled and found a few things to try:
http://stackoverflow.com/questions/4357270/table-is-marked-as-crashed-and-should-be-repaired

Be careful with what you try…

3

Many thanks for your advice. I’ll look in to this.

4

Sounds like a issue with you db, if you can directly access the db table, you can run a command to repair the table

but if you need to clear out the job_queue table this should be an issue as primarily it will just store the history of scheduler jobs that have run and any that are pending/running, but if you clear it out the scheduler will just run again anyway and refill new jobs in the table.