max_allowed_packet error filling error log

  • Resolved webtent

    (@webtent)


    8 years, 2 months ago

    I’ve found our error_log file is growing too big and see tons of entries constantly being added to the file related to UPDATE on the wp_options table. The updates are being done where option_name is wordpress-https_path_cache and the update is attempting to post values over 3 million characters in length. Below is example with the majority snipped out due to length…

    [16-Jan-2018 17:05:33 UTC] WordPress database error Got a packet bigger than 'max_allowed_packet' bytes for query UPDATEwp_optionsSEToption_value` = ‘a:18722:{s:13:\”/programming/\”;
    <snip>
    i:0;s:27:\”/tag/alternative-rock/feed/\”;i:0;s:25:\”/tag/charleston-shooting/\”;i:0;s:11:\”/tag/meals/\”;i:0;s:24:\”/music-inspired-dr-king/\”;i:0;}’ WHERE option_name = ‘wordpress-https_path_cache’ made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, wp_ob_end_flush_all, ob_end_flush, WordPressHTTPS_Module_Parser->parseHtml, WordPressHTTPS_Module_Parser->fixLinksAndForms, Mvied_Base->setSetting, update_option`

    How can I stop these updates from filling the log? Right now, I have error_log disabled.

Viewing 2 replies - 1 through 2 (of 2 total)
  • OptimizerWP

    (@layerthemes)

    8 years, 1 month ago

    Yeah, Same thing happened here. the error logs were 15gb in 3 days and our site crashed several times, I am not sure why the dev though it would be a good idea to write cache like this in the db… 😐

    Thread Starter webtent

    (@webtent)

    8 years, 1 month ago

    I set the max_allowed_packet in the my.cnf file for MariaDB to resolve. The default is very low and by changing to ‘max_allowed_packet=100M’, the issue went away. Good luck!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘max_allowed_packet error filling error log’ is closed to new replies.