Sync failing due to database corruption

  • mikebreeze

    (@mikebreeze)


    4 years ago

    Production site = spookybeavers.net; Staging site = j9j.6e5.myftpupload.com
    WordPress version = 5.5.3; PHP Version = 7.3
    Wordpress shared hosting by godaddy.com
    Site turned 2 years old on 11/15/2020

    I’ve had no issues syncing staging to production until 11/13/2020. I initially got a “Building Staging Site at 80%” which stayed that way for over 24 hours. After a week of back and forth with godaddy.com I received the following email:

    …We have determined the issue preventing your hosting sync from completing was due to some corrupt content in your staging database. Two tables in your staging database, wp_fn08dt591m_actionscheduler_actions and wp_fn08dt591m_wpgmza – have null values that are causing the sync to error. We have manually synced the remainder of your database to your production site. The site is up and running without these two tables, but please note that future syncs will stall until the errors with these tables in the staging database are addressed. …

    GoDaddy feels that a plugin caused this database corruption and says that it is my responsibility to fix. So my questions are:

    1) Did a plugin cause this error?
    2) What do these two tables do?
    3) Can I possibly repair or clear the corrupted data from the database?
    3) If all else fails should I create a new site, transfer all content and then nuke the current site?

    Thanks in advance.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    1. We have no way of knowing.
    2. The tables belong to specific plugins, so maybe… ???
    3. Give it a try. Repair the tables using PHPMYADMIN.
    4. It’s a staging site, so it should be OK to blow it away and recreate it.

    Thread Starter mikebreeze

    (@mikebreeze)

    Is PHPMYADMIN the plugin by Puvox Software? Can one access the database tables within WordPress via command line using mysql -u username -p ? I’m debating whether to go the plugin route or just have godaddy.com blow away my present staging server, reinstall it and just copy everything over from production. I’ve read that the repair command only works about 50% of the time for corrupted tables. Your thoughts?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    PHPMYADMIN should be in the GoDaddy control panel; it’s not part of WordPress.

    If you’re comfortable with a command line, you could use the mysqlcheck command to check and repair the table.

    Thread Starter mikebreeze

    (@mikebreeze)

    Now I’m really in trouble. I had planned on deleting my staging server tomorrow and recreate/sync my production server to staging next week. However, today I logged into my production dashboard and saw that the wp Google Maps plugin needed to be updated. I did and it broke my production server. I’ll notify the authors of this plugin. I will also call GoDaddy tomorrow to see if they can’t help me fix production. Happy Thanksgiving.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Sync failing due to database corruption’ is closed to new replies.