Same here. I have a few sites where this is happening now. On one, the error file reached about 700MB. I found one instance where the file was of manageable size, so that it could be opened and it’s a single line of text listing, seemingly, every file in the site. It opens…
[01-May-2013 20:08:09] WordPress database error Got a packet bigger than 'max_allowed_packet' bytes for query INSERT INTOlcdji_options(option_name,option_value,autoload) VALUES ('bwps_file_log', 's:1390763:\"a:9079:{s:11:\"readme.html\";a:2:{s:8:\"mod_date\";d:1359142945;s:4:\"hash\";s:32:\"05d50a04ef19bd4b0a280362469bf22f\";}s:22:\"wp-includes/update.php\";a:2:{s:8:\"mod_date\";d:1355667197;s:4:\"hash\";s:32:\"2f3b9e14fcc05ad89d1bcc6b32339f33\";}
and it ends…
made by 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->filecheck, bwps_filecheck->__construct, bwps_filecheck->execute_filecheck
All I can think to do is to make the error_log file un-writeable. Is there a more elegant solution?
