Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted February 7, 20241 yr Hey All-- Our CreditInfoCenter.com community forum started to experience what appears to be a corrupted DB where users with accounts and admins cannot login. As the admin, this doesn't give me the ability to diagnose the issue because I have no access to the backend. Normal anonymous visitors can view the site one or two pages deep, but after that, they see this error. Users with accounts see a mess and have no way of logging out. They can only see the forum while in a logged out browser such as incognito mode. And this is what I see as Admin. Nor can anyone create a new account. The error code is EX12666 Something went wrong. Please try again. The only thing that has changed in the last 24 hours is that we expanded the core_search_index so users could search all of the topics/posts. I've engaged with the hosting company (SiteGround), but this is an Invision issue and they can't provide support for the problem. Your input is appreciated. Edited February 7, 20241 yr by Kevin Marcum
February 7, 20241 yr Community Expert The error code there is not one which we utilize currently so may be from a third party or has been decommissioned. Would recommend trying recovery mode as outlined below in the guide: If recovery mode does not work, you will need to post the system log error. This can be found in /uploads/logs. It will be dated today.
February 7, 20241 yr Author Thanks, but unfortunately, I can't even log in to the admin section to trigger recovery mode. The logs are php files and an index file. Should I post them directly to this thread?
February 7, 20241 yr Community Expert 4 minutes ago, Kevin Marcum said: Thanks, but unfortunately, I can't even log in to the admin section to trigger recovery mode. You would not need to. This would be something done on the file level. 4 minutes ago, Kevin Marcum said: The logs are php files and an index file. Should I post them directly to this thread? You can indeed. Remove any information that should be private, like your directory paths prior to /uploads
February 7, 20241 yr Author Looking at the logs, it appears SiteGround has a limit on the database. I have a ticket into them and have attached one of the system error logs. They put that on when I moved the site to one of their managed plans. I have since moved it to an "unlimited" DB plan, but their automation may have still placed a limit on the URL. I'll try the manual recovery if the limit on the database is not the issue. 2024_02_04_uncaught_exception.php
February 7, 20241 yr Author SiteGround did lift the DB limit and all is well with the world. Site is fully functional again. Thanks for your help.
