database errors

Permalink
I am having multiple errors after updating to 5.6.1.2.

I had to update due to the breadcrumb template not set up properly in a previous version of Concrete5 (not displaying > separators properly, the fix was to upgrade to 5.6.1.2).

After the upgrade the site was receiving "unable to connect to database errors when navigating to any page or throughout the dashboard, but upon refresh, the site would come back online. It is as if it is intermittently not connecting to the database.

After examining the database in phpMyAdmin, the following message was displayed after doing a Check Database:

"The indexes PRIMARY and paID_peID seem to be equal and one of them could possibly be removed."

How could this have happened to the database? Is it safe to remove the extra index?. If so, how do you do it?

sherri333
 
VPenkov replied on at Permalink Reply
VPenkov
Those indexes don't cause such errors, they aren't even used by c5 directly, and are for optimization purposes.
Have you tried clearing and/or disabling your cache?
sherri333 replied on at Permalink Reply
sherri333
Do you know what causes them to be in the database?

And yes, I have tried both clearing and disabling the cache. Every time I do anything on the site, either in the dashboard or on the front end (go to a different page, etc), I get an "unable to connect to database error". Even now, during and after clearing cache. After refreshing browser, it reconnects and displays the page.
VPenkov replied on at Permalink Reply
VPenkov
No, I don't know why they are both there, but they really don't matter in this particular case.
Have you noticed any changes in the URL after you refresh the page?
sherri333 replied on at Permalink Reply
sherri333
No, there is no change in the URL when the page is refreshed. It just eventually, slowly, refreshes and the site is displayed again. But it is pretty much every single page.
sherri333 replied on at Permalink Reply
sherri333
Hi again,

I ended up restoring the entire site from a backup, except left the database as is, and it is all working fine again. So, you were right, those items in the database did not affect anything. It appears to be the upgrade to 5.6.1.2. that caused the problems.

Unfortunately, I now need to figure out how to fix the breadcrumbs which are messed up from the current version, which is 5.6.0.2.

Just want to say thanks for the assistance. Will be more careful to only apply upgrades to a beta site from now on. I should have known better.

Thanks!