Lates update: DB errors duplicate column

  • Resolved swissspaceboy

    (@swissspaceboy)


    4 years, 1 month ago

    Hello,

    During my auto-update of today of Wordfence plugin, my WP logged me these errors:

    [18-May-2022 06:47:37 UTC] WordPress database error Duplicate column name ‘wordpress_path’ for query ALTER TABLEctn_wfknownfilelist ADD COLUMN wordpress_path TEXT NOT NULL made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/wordfence/wordfence.php’), wordfence::install_actions, wordfence::runInstall
    [18-May-2022 06:47:37 UTC] WordPress database error Duplicate column name ‘wordpress_path’ for query ALTER TABLE ctn_wfknownfilelist ADD COLUMN wordpress_path TEXT NOT NULL made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/wordfence/wordfence.php’), wordfence::install_actions, wordfence::runInstall
    [18-May-2022 06:47:37 UTC] WordPress database error Duplicate column name ‘wordpress_path’ for query ALTER TABLE ctn_wfknownfilelist ADD COLUMN wordpress_path TEXT NOT NULL made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/wordfence/wordfence.php’), wordfence::install_actions, wordfence::runInstall
    [18-May-2022 06:47:37 UTC] WordPress database error Duplicate column name ‘real_path’ for query ALTER TABLE ctn_wffilemods ADD COLUMN real_path TEXT NOT NULL AFTER filename made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/wordfence/wordfence.php’), wordfence::install_actions, wordfence::runInstall
    [18-May-2022 06:47:37 UTC] WordPress database error Duplicate column name ‘real_path’ for query ALTER TABLE ctn_wffilemods ADD COLUMN real_path TEXT NOT NULL AFTER filename made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/wordfence/wordfence.php’), wordfence::install_actions, wordfence::runInstall
    [18-May-2022 06:47:37 UTC] WordPress database error Duplicate column name ‘real_path’ for query ALTER TABLE ctn_wffilemods ADD COLUMN real_path TEXT NOT NULL AFTER filename made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/wordfence/wordfence.php’), wordfence::install_actions, wordfence::runInstall

    My site is running and Wordfence too. Anything to worry about these duplicate SQL errors?

    Didier.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support wfpeter

    (@wfpeter)

    4 years, 1 month ago

    Hi @swissspaceboy, thanks for your message.

    Our update process does run checks for whether columns exist, so this looks more like a number of parallel hits on the database attempting to trigger the updates occurred at the same timestamp.

    The most likely explanation is that the first one succeeded, then these errors indicate that the columns had already been created when the other hits tried almost simultaneously.

    Thanks,

    Peter.

    Thread Starter swissspaceboy

    (@swissspaceboy)

    4 years, 1 month ago

    Hi,

    Thanks for the reply.

    Parallel hits? This is from Wordfence right, cause I only have 1 site per domain (no multi-site). I have multiple sites connected to their own database in the same SQL server however. I saw that the plugin was auto-updated on my 4 sites almost at the same time for all 4 domains. A conflict here maybe?

    So who would be updating in parallel the database structure? My other sites did not report this SQL error.

    Didier.

    Plugin Support wfpeter

    (@wfpeter)

    4 years, 1 month ago

    Hi @swissspaceboy,

    I believe that they would’ve been multiple hits from the Wordfence update process as subsequent queries during the update would’ve been dependent on these tables and columns being present also. I don’t have any reason to believe this site is more or less likely to see these messages in future compared to your other sites, but they can be safely ignored as the processing time to determine the columns were already present will be negligible.

    Thanks again,

    Peter.

    Thread Starter swissspaceboy

    (@swissspaceboy)

    4 years, 1 month ago

    Ok Peter. Thanks for the reply.

    I’ll report back in case these duplicate errors come back.

    The ticket can be closed.

    Bye,

    Didier.

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

The topic ‘Lates update: DB errors duplicate column’ is closed to new replies.