Security problem?
-
In error.log of a WP site I’ve inherited I get several errors like this:
[Wed Dec 04 01:11:52 2013] [error] [client 198.27.80.33] WordPress errore sul database MySQL server has gone away per la query UPDATE
hcvwp_optionsSET
option_value= 'a:6:{i:1386115794;a:2:{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;}}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:1386115892;a:1:{s:11:\\"wp_cache_gc\\";a:1:{s:32:\\"40cd750bba9870f18aada2478b24840a\\";a:2:{s:8:\\"schedule\\";b:0;s:4:\\"args\\";a:0:{}}}}i:1386136800;a:1:{s:20:\\"wp_maybe_auto_update\\";a:1:{s:32:\\"40cd750bba9870f18aada2478b24840a\\";a:3:{s:8:\\"schedule\\";s:10:\\"twicedaily\\";s:4:\\"args\\";a:0:{}s:8:\\"interval\\";i:43200;}}}i:1386161328;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:1386164926;a:1:{s:30:\\"wp_scheduled_auto_draft_delete\\";a:1:{s:32:\\"40cd750bba9870f18aada2478b24840a\\";a:3:{s:8:\\"schedule\\";s:5:\\"daily\\";s:4:\\"args\\";a:0:{}s:8:\\"interval\\";i:86400;}}}s:7:\\"version\\";i:2;}' WHERE
option_name= 'cron' fatta da require('wp-blog-header.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('plugins_loaded'), call_user_func_array, bwps_secure->themeupdates, wp_clear_scheduled_hook, wp_unschedule_event, _set_cron_array, update_option
in rapid succession, e.g. hundreds in a few minutes. After those, I get
[Wed Dec 04 01:11:52 2013] [error] [client 198.27.80.33] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 52 bytes) in /home/.../wp-includes/functions.php on line 3950
Line 3950 is inside the
wp_debug_backtrace_summary
function, so I believe that means the exception was an outofmemory that pervented even the debug function to work. Now I guess the outofmemory could be caused by previous a loop of thoseMySQL server has gone away
events.That being said (er… guessed) I still wonder where the problem hides in my site. How can I spot it?
Just for the record, I’m running WP updated at its most recent release and a five plugins, all updated (Better WP Security, Custom sidebars, Google Picasa Viewer, PicasaView, WP Super Cache). A number of other plugins are installed but disabled.
- The topic ‘Security problem?’ is closed to new replies.