Database migration issue caused by wfConfig table entries

  • Resolved mengsel

    (@mengsel)


    8 years, 6 months ago

    I’ve encountered an issue whilst migrating a website using WordFence from one server to another. During database migration, whilst importing an SQL backup of the wordpress database, I’ve encountered a max_allowed_packet error that occurs when server tries to execute:

    INSERT INTO wp_wfConfig (name, val) VALUES
    (‘wfsd_engine’, 0x4f3a3132 […];

    The value in this entry exceeds the default 16M max_allowed_packet value. As a result the import operation is halted. I’ve managed to migrate the database by dropping all WordFence-related tables, effectively forcing WF into a blank re-activation.

    Perhaps it would interest the developers of the plugin to find a workaround for setting up a table row with such a massive amount of data that it effectively makes any database export unusable, for example by fragmenting the data stored. I’m not really an SQL expert so I’m just gonna drop this issue here and hope you can do something with it.

    If you need any additional information I’ll be happy to provide it ??

    https://www.ads-software.com/plugins/wordfence/

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

  • Hi mengsel,

    I will pass this on to the development team.

    Thanks for the info!

    I am going to go ahead and mark this resolved. If I have feedback or questions from the dev team, I will update the post.

    Thanks again.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Database migration issue caused by wfConfig table entries’ is closed to new replies.