MySql Error log flooded with errors from WordPress

  • Hi,
    I noticed today that my mysql error log is flooded with warnings fired by WordPress’ options table.
    Here are few lines of the log:

    2017-02-14 16:21:57 1338 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO so_options (option_name, option_value, autoload) VALUES (‘_transient_timeout_jetpack_sync_callables_await’, ‘1487085777’, ‘no’) ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)
    2017-02-14 16:21:57 1338 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO so_options (option_name, option_value, autoload) VALUES (‘_transient_jetpack_sync_callables_await’, ‘1487085717.7727’, ‘no’) ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)
    2017-02-14 16:24:08 1338 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO so_options (option_name, option_value, autoload) VALUES (‘_transient_timeout_jetpack_sync_callables_await’, ‘1487085908’, ‘no’) ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)
    2017-02-14 16:24:08 1338 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO so_options (option_name, option_value, autoload) VALUES (‘_transient_jetpack_sync_callables_await’, ‘1487085848.2307’, ‘no’) ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)

    There is any way to fix the problem? Is it a WordPress bug or there is some problem with my installation?

    Thanks in advance,
    S.

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

  • Deactivate and then delete JetPack.

    Thread Starter leeppolis

    (@leeppolis)

    Yeah, thanks, this means that Jetpack (an official plugin coded by Auttomatic) is bugged?
    That doesn’t really make sense to me. Either it looks impossible that no one noticed the problem before me…

    Doesn’t mean anything yet. Just ruling out things. Try deactivating all plugins. If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue (theme functions can interfere like plugins).

    Thread Starter leeppolis

    (@leeppolis)

    You’re right, sorry for the reply.
    So, deactivating Jetpack the logging stopped.
    Activating the twetysixteen theme instead of my default theme, a lot of new warnings started being logged:

    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#VenezuelaConTareck’, ‘%23VenezuelaConTareck’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#IBMGoT’, ‘%23IBMGoT’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#FelizMiercoles’, ‘%23FelizMiercoles’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#bfc530’, ‘%23bfc530’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#AtlantaAlive’, ‘%23AtlantaAlive’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#SecDef’, ‘%23SecDef’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#njmorningshow’, ‘%23njmorningshow’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#FoxKatZ1035’, ‘%23FoxKatZ1035’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#BlownOff’, ‘%23BlownOff’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#Malden’, ‘%23Malden’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#POWERGetUpCrew’, ‘%23POWERGetUpCrew’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#FOX13GMM’, ‘%23FOX13GMM’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
    2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#BurnASongOrBand’, ‘%23BurnASongOrBand’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’

    (This are just few of them)

    Thread Starter leeppolis

    (@leeppolis)

    Yes, you’re right, sorry for my answer.
    So, deactivating Jetpack it stopped logging warnings…
    Replacing my custom theme with twenty sixteen, the log started being flooded again, but with different warning messages (these are just a sample)

    2017-02-15 14:24:42 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO so_options (option_name, option_value, autoload) VALUES (‘theme_mods_twentysixteen’, ‘a:1:{i:0;b:0;}’, ‘yes’) ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)
    2017-02-15 14:25:04 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO so_options (option_name, option_value, autoload) VALUES (‘_transient_is_multi_author’, ‘1’, ‘yes’) ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)
    2017-02-15 14:25:04 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO so_options (option_name, option_value, autoload) VALUES (‘_transient_twentysixteen_categories’, ‘2’, ‘yes’) ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘MySql Error log flooded with errors from WordPress’ is closed to new replies.

Tags