Support Forum

SPF filling the error_log

BM Bill Murray
Bill Murray
Member
Member since Apr 2010
129 posts
Oct 4, 2011 · 8:33 am · Edited

I had to deactivate SPF due to a rapidly growing error log. On both the front end and back end, everything seems fine.  However, the site started to get very slow, and I noticed that the error_log was filling up with contents similar to what I pasted below.  In a 6 hour span, the error_log got to 48 Mb with similar content.  Before I observed it the first time, the log was approaching 100 Mb.  Before deactivating, my apache status panel was full of cron entries; after deactivating, they are all gone.

One other oddity:

When clicking to the plugins menu choice, I got this (I shortened URL):

Fatal error: Cannot run code from this file in conjunction with non encoded files in ../wp-includes/version.php on line 201

I have no info to connect the 2, but other than SPF, the site config hasn’t really changed.

I am running WP 3.2.1 multi-site with W3 Total Cache, which hasn’t changed since I first installed SPF 5.0.  The error_log situation only started happening with my SVN update from Sunday, but it might have been going on from my just prior update and I didn’t notice.

Any thoughts?

 

Portion of error_log below:

[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query UPDATE `wp_options` SET `option_value` = ‘a:29:{i:1317704780;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317705288;a:1:{s:25:”w3_cdn_cron_queue_process”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:25:”w3_cdn_cron_queue_process”;s:4:”args”;a:0:{}s:8:”interval”;i:900;}}}i:1317705527;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317705604;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317706704;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317707185;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317707815;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317708125;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317708202;a:3:{s:18:”w3_dbcache_cleanup”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:18:”w3_dbcache_cleanup”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}s:22:”w3_objectcache_cleanup”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:22:”w3_objectcache_cleanup”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}s:18:”w3_pgcache_cleanup”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:18:”w3_pgcache_cleanup”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317708359;a:1:{s:18:”w3_cdn_cron_upload”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:18:”w3_cdn_cron_upload”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317708380;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317721263;a:1:{s:16:”wp_update_themes”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:10:”twicedaily”;s:4:”args”;a:0:{}s:8:”interval”;i:43200;}}}i:1317736525;a:1:{s:21:”dbmanager_cron_backup”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:16:”dbmanager_backup”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317738290;a:1:{s:21:”update_network_counts”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:10:”twicedaily”;s:4:”args”;a:0:{}s:8:”interval”;i:43200;}}}i:1317738459;a:1:{s:10:”polls_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:10:”twicedaily”;s:4:”args”;a:0:{}s:8:”interval”;i:43200;}}}i:1317740066;a:1:{s:16:”wp_version_check”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:10:”twicedaily”;s:4:”args”;a:0:{}s:8:”interval”;i:43200;}}}i:1317740780;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317743884;a:1:{s:24:”akismet_scheduled_delete”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317744927;a:1:{s:17:”wp_update_plugins”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:10:”twicedaily”;s:4:”args”;a:0:{}s:8:”interval”;i:43200;}}}i:1317745127;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317749904;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317751402;a:1:{s:17:”w3_minify_cleanup”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:17:”w3_minify_cleanup”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317752404;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317761815;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317772925;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317776389;a:1:{s:19:”wp_scheduled_delete”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317779185;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317822925;a:1:{s:23:”dbmanager_cron_optimize”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:18:”dbmanager_optimize”;s:4:”args”;a:0:{}s:8:”interval”;i:259200;}}}s:7:”version”;i:2;}’ WHERE `option_name` = ‘cron’ made by call_user_func_array, wp_reschedule_event, wp_schedule_event, _set_cron_array, update_option, W3_Db->update, W3_Db_Nocache->query, W3_Db->query_nocache
[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query UPDATE `wp_options` SET `option_value` = ‘a:28:{i:1317705288;a:1:{s:25:”w3_cdn_cron_queue_process”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:25:”w3_cdn_cron_queue_process”;s:4:”args”;a:0:{}s:8:”interval”;i:900;}}}i:1317705527;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317705604;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317706704;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317707185;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317707815;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317708125;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317708202;a:3:{s:18:”w3_dbcache_cleanup”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:18:”w3_dbcache_cleanup”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}s:22:”w3_objectcache_cleanup”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:22:”w3_objectcache_cleanup”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}s:18:”w3_pgcache_cleanup”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:18:”w3_pgcache_cleanup”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317708359;a:1:{s:18:”w3_cdn_cron_upload”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:18:”w3_cdn_cron_upload”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317708380;a:1:{s:14:”sph_stats_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:6:”hourly”;s:4:”args”;a:0:{}s:8:”interval”;i:3600;}}}i:1317721263;a:1:{s:16:”wp_update_themes”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:10:”twicedaily”;s:4:”args”;a:0:{}s:8:”interval”;i:43200;}}}i:1317736525;a:1:{s:21:”dbmanager_cron_backup”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:16:”dbmanager_backup”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317738290;a:1:{s:21:”update_network_counts”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:10:”twicedaily”;s:4:”args”;a:0:{}s:8:”interval”;i:43200;}}}i:1317738459;a:1:{s:10:”polls_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:10:”twicedaily”;s:4:”args”;a:0:{}s:8:”interval”;i:43200;}}}i:1317740066;a:1:{s:16:”wp_version_check”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:10:”twicedaily”;s:4:”args”;a:0:{}s:8:”interval”;i:43200;}}}i:1317740780;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317743884;a:1:{s:24:”akismet_scheduled_delete”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317744927;a:1:{s:17:”wp_update_plugins”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:10:”twicedaily”;s:4:”args”;a:0:{}s:8:”interval”;i:43200;}}}i:1317745127;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317749904;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317751402;a:1:{s:17:”w3_minify_cleanup”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:17:”w3_minify_cleanup”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317752404;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317761815;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317772925;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317776389;a:1:{s:19:”wp_scheduled_delete”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317779185;a:1:{s:26:”sph_transient_cleanup_cron”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:5:”daily”;s:4:”args”;a:0:{}s:8:”interval”;i:86400;}}}i:1317822925;a:1:{s:23:”dbmanager_cron_optimize”;a:1:{s:32:”40cd750bba9870f18aada2478b24840a”;a:3:{s:8:”schedule”;s:18:”dbmanager_optimize”;s:4:”args”;a:0:{}s:8:”interval”;i:259200;}}}s:7:”version”;i:2;}’ WHERE `option_name` = ‘cron’ made by wp_unschedule_event, _set_cron_array, update_option, W3_Db->update, W3_Db_Nocache->query, W3_Db->query_nocache
[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query SELECT  * FROM wp_sfforums ORDER BY group_id made by do_action_ref_array, call_user_func_array, sp_cron_generate_stats, sp_get_stats_counts, spdb_table, spdb_select, W3_Db->query
[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query SHOW TABLES LIKE ‘wp_sferrorlog’ made by do_action_ref_array, call_user_func_array, sp_cron_generate_stats, sp_get_stats_counts, spdb_table, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, W3_Db->query
[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query SHOW TABLES LIKE ‘wp_sferrorlog’ made by do_action_ref_array, call_user_func_array, sp_cron_generate_stats, sp_get_stats_counts, spdb_table, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, W3_Db->query
[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query SHOW TABLES LIKE ‘wp_sferrorlog’ made by do_action_ref_array, call_user_func_array, sp_cron_generate_stats, sp_get_stats_counts, spdb_table, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, W3_Db->query
[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query SHOW TABLES LIKE ‘wp_sferrorlog’ made by do_action_ref_array, call_user_func_array, sp_cron_generate_stats, sp_get_stats_counts, spdb_table, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, W3_Db->query
[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query SHOW TABLES LIKE ‘wp_sferrorlog’ made by do_action_ref_array, call_user_func_array, sp_cron_generate_stats, sp_get_stats_counts, spdb_table, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, W3_Db->query
[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query SHOW TABLES LIKE ‘wp_sferrorlog’ made by do_action_ref_array, call_user_func_array, sp_cron_generate_stats, sp_get_stats_counts, spdb_table, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, W3_Db->query
[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query SHOW TABLES LIKE ‘wp_sferrorlog’ made by do_action_ref_array, call_user_func_array, sp_cron_generate_stats, sp_get_stats_counts, spdb_table, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, W3_Db->query
[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query SHOW TABLES LIKE ‘wp_sferrorlog’ made by do_action_ref_array, call_user_func_array, sp_cron_generate_stats, sp_get_stats_counts, spdb_table, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, W3_Db->query
[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query SHOW TABLES LIKE ‘wp_sferrorlog’ made by do_action_ref_array, call_user_func_array, sp_cron_generate_stats, sp_get_stats_counts, spdb_table, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, W3_Db->query

16 Answers

New Answer
BM Bill Murray
Bill Murray
Member
Member since Apr 2010
129 posts
Oct 4, 2011 · 12:38 pm

You can ignore the part about:

Fatal error: Cannot run code from this file in conjunction with non encoded files in ../wp-includes/version.php on line 201

I had installed APC but had forgotten to disable Zend, and that was triggering that error on many backend pages.  Too many late night kills my RAM.

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Oct 5, 2011 · 12:02 am

error code 28 means the mysql server has gone away…  once the mysql server is not reachable, you will get tons of errors…

BM Bill Murray
Bill Murray
Member
Member since Apr 2010
129 posts
Oct 9, 2011 · 9:52 am

I’m back!  I get the point about the mySQL server going away.  I come at least that far 🙂 

I deactivated SPF and saw no problems.  So I reactivated, and here is a sample of what I see.  Note that the end was manually cut off my me.  On the query, the string is huge and it repeats.  See the pattern of spdb_select, sp_construct_database_error, sp_write_error.  Once that starts, it just repeats and repeats.  If that is the actual query, it is no wonder the mySQL went away.  So, my questions are: is that the actual query and if not, what is causing it to go haywire?

 

[09-Oct-2011 14:30:48] WordPress database error MySQL server has gone away for query SHOW TABLES LIKE ‘wp_sferrorlog’ made by do_action_ref_array, call_user_func_array, sp_cron_generate_stats, sp_get_stats_counts, spdb_table, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error, spdb_select, sp_construct_database_error, sp_write_error …

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Oct 9, 2011 · 11:14 am

I dont know… obviously some queries require more db cpu/time than others… if the mysql server is hanging by a thread, its possible a query can put it over the edge… but still points back to a weak mysql server…

I think there is a way to monitor the mysql server and report back on long queries and see if any trend… I would google for how to do that…

BM Bill Murray
Bill Murray
Member
Member since Apr 2010
129 posts
Oct 9, 2011 · 6:49 pm

Before I get into checking the mySQL server, which I think is fine, can you confirm that the query is right? 

Can you explain why the query appears to repeat endlessly 3 items?  I’ve seen a lot of queries, and I have never seen one that repeats to the degree this query does. 

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Oct 9, 2011 · 7:01 pm

Depends on what you mean by correct… wink

yes, that is one of our queries…  I dont know what you mean by endlessly… that is a query as part of trying to write out an error to the error log…  I assume you do have an sferrorlog table?

so without knowing more information, only way I could see some sort of repetitive loop is if the trying to generate the error itself was causing an error generation…

do you know what the original error it was trying to generate was?

BM Bill Murray
Bill Murray
Member
Member since Apr 2010
129 posts
Oct 9, 2011 · 7:15 pm

Yes, I do have an sferrorlog table.  However, there are no errors in the log.

You say that is one of your queriers – you have the query repeating those 3 elements?  That seems odd.

I just have a couple of posts in my forum, and I didn’t get any new posts today.  So the error, whatever it was, could have only occurred with someone just viewing the forum. 

Could it have occurred updating stats?

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Oct 9, 2011 · 7:27 pm

No, thats not what quite what I said…. about repeating…

there is not builit in repeating…  the query:

    $success = spdb_select(‘var’, “SHOW TABLES LIKE ‘”.SFERRORLOG.”‘”);

happens once when generating an error message for the log…  I did hypothesize that perhaps the act of trying to write to the error log is itself generating an error…  and so its possible it could do the query again…

BM Bill Murray
Bill Murray
Member
Member since Apr 2010
129 posts
Oct 9, 2011 · 7:48 pm

Your hypothesis that the act of trying to write to the error log is generating an error could be correct, since there are no errors in the log.

But let’s imagine it does the query again.  It is as if the query is not duplicated exactly, but for each successive duplication of the query, the components in the array are duplicated, so that the query grows and grows, almost like the federal debt.

Btw, my sferrorlog has 4 fields: id, error_date, error_type, error_text.  I am assuming the structure did not change.

Are the stats updated automatically?  Given my forum has virtually no activity, could updating the stats be the source of the problem?

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Oct 9, 2011 · 8:59 pm

the size of the query wont grow… the query is fixed… if there was some sort of loop, it would be the query, then the query, then the query, etc… so the query X times in a row… but the query itself would be small and simple…

yes, the stats run via cron job every hour and update… but the level of activity wouldn’t affect the stats… and cron jobs on wp cant run with no activity… so the stats cron, for example would not run every hour if someone didnt visit the site… but if an hour (or 20 with no visits), wp would fire the crons on the next visit…

Andy should be back tomorrow (while I step away for a couple days) and may shed more light.

BM Bill Murray
Bill Murray
Member
Member since Apr 2010
129 posts
Oct 9, 2011 · 9:19 pm

Ok. 

The query as reported in the error_log is growing.

If the cron is running on a visit, then maybe someone is visiting the forum page, and the error takes place when generating stats.

If the stats code was updated, maybe I can try updating my SVN.  I am at least 1 week and maybe 2 weeks old.

YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Oct 14, 2011 · 4:09 am

Not sure I can be much help on the cron job issues as I have about zero expertise in that area but I can discuss the sql error entry.

However I am not sure at all what you mean by the ‘query is growing’? It’s the same query being run every time that is failing.

You clearly have a single sql error (to be determined) which will then attempt to put an entry in the Sp error log. Because the server has gone away this too generates an error and a further attempt to write to the SP error log.

The questions here are

  1. What was the original sql error that prompted an error log entry? The log is on the previous page but I will go back to see if I can find it.
  2. Why does the sql engine ‘go away’? All it is doing at that point is asking the mysql server if it actually has the error log table….!

It would clearly be useful for us to clean the code so that if the error entry fails to write we don’t spin intio a loop and I will open a ticket for that. But knowing the answers to the above questions would be a great help.

[UPDATE] There you go. Looks like the first error that then caused the looping error log attempt was this:

[04-Oct-2011 05:13:08] WordPress database error MySQL server has gone away for query SELECT  * FROM wp_sfforums ORDER BY group_id

So it started off with a loss of the mysql server engine – something which perhaps is berst asked of your host.

BM Bill Murray
Bill Murray
Member
Member since Apr 2010
129 posts
Oct 14, 2011 · 10:58 pm

Thanks for the update.

I can only add this info:

1) Without SPF activated, I don’t really see errors of mySQL going away.  Prior to a recent update, I didn’t see them even with SPF; it was just something that happened recently.

2) Perhaps you have landed on what I meant by the query growing by your discussion of the looping error log.  In a normal setting, if mySQL had gone away, it would trigger an error, and that would be that.  But here, that wasn’t the case.

3) There were no entries in the SPF error log, whereas before SPF was writing successfully to the log.  Maybe something broke that?

4) I’ll update my SVN now and reload SPF.  Hopefully, it will work smoothly.  I’ll report back.

YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Oct 15, 2011 · 2:49 am

Well 3 was the error you were seeing… trying to create an error log entry.
There is some good info on this out there if you google ‘server gone away’. Might just be the wait_timeout setting or just a simple tcp/ip glitch of some sort.