Revo 2.2.11 upgrade - suddenly a massive error log

165 Posts

pdincubus Reply #1, 12 years, 8 months ago

Just upgraded a fairly big site to 2.2.11, upgrade went smoothly but now a lot of the time the frontend and backend are very slow at loading, sometimes give up and the site error log is VERY rapidly filling up. Mostly it's this message:

SELECT `modSnippet`.`id` AS `modSnippet_id`, `modSnippet`.`source` AS `modSnippet_source`, `modSnippet`.`property_preprocess` AS `modSnippet_property_preprocess`, `modSnippet`.`name` AS `modSnippet_name`, `modSnippet`.`description` AS `modSnippet_description`, `modSnippet`.`editor_type` AS `modSnippet_editor_type`, `modSnippet`.`category` AS `modSnippet_category`, `modSnippet`.`cache_type` AS `modSnippet_cache_type`, `modSnippet`.`snippet` AS `modSnippet_snippet`, `modSnippet`.`locked` AS `modSnippet_locked`, `modSnippet`.`properties` AS `modSnippet_properties`, `modSnippet`.`moduleguid` AS `modSnippet_moduleguid`, `modSnippet`.`static` AS `modSnippet_static`, `modSnippet`.`static_file` AS `modSnippet_static_file`, `Source`.`id` AS `Source_id`, `Source`.`name` AS `Source_name`, `Source`.`description` AS `Source_description`, `Source`.`class_key` AS `Source_class_key`, `Source`.`properties` AS `Source_properties`, `Source`.`is_stream` AS `Source_is_stream` FROM `modx_site_snippets` AS `modSnippet` LEFT JOIN `modx_media_sources` `Source` ON `modSnippet`.`source` = `Source`.`id` WHERE `modSnippet`.`name` = ? ORDER BY `modSnippet`.`id` ASC

Any ideas what could be causing this? The site has worked flawlessly for months until this upgrade!

☆ A M B ☆
24,524 Posts

sottwell Reply #2, 12 years, 8 months ago

Looks like an SQL error. That's not the error, it's just a full description of the query causing the error.

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

165 Posts

pdincubus Reply #3, 12 years, 8 months ago

Quote from: sottwell at Jan 23, 2014, 06:05 AM

Looks like an SQL error. That's not the error, it's just a full description of the query causing the error.

There was more to the error but the SQL statement was the most part - seemed to be causing the MySQL server to have "gone away" and PHP errors reporting that scripts were timing out as had exceeded 30 seconds waiting.

Maybe wasn't directly related to the 2.2.11 upgrade but very strange that it happened immediately after the upgrade process - either way seems to have currently calmed down and server load is back down to a sensible level!

24,544 Posts

BobRay Reply #4, 12 years, 8 months ago

Your server may have been overloaded at the time. That will cause it to "go away" and experience timeouts. This would have been aggravated by the upgrade clearing the whole site cache, which puts an extra load on the DB since without the cache, everything has to be retrieved from the DB.

The host may have addressed the issue, or things may have improved now that the cache has been rebuilt (or both).

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

☆ A M B ☆
24,524 Posts

sottwell Reply #5, 12 years, 8 months ago

You also might want to force a full clearing of your browser cache; often javascript files are not refreshed regularly, and since the upgrade updates some of the .js files your browser can be trying to use its cached older versions of the files.

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org