New to the community? Start here

DB errors in log after migrating to DEV hosting

After migrating my site to WPMUDEV hosting, I am receiving errors in my logs like below:

[31-Jan-2019 15:54:54 UTC] WordPress database error Table ‘alcornnelsonllc_wpmudev_host.wp_q5_frmt_form_entry’ doesn’t exist for query SELECT e.entry_id AS entry_idr tttttttFROM wp_q5_frmt_form_entry er tttttttWHERE e.entry_type = ‘poll’r tttttttAND e.date_created < ‘2018-01-31 09:54:54’ made by do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, Forminator_Polls_General_Data_Protection->personal_data_cleanup, Forminator_Polls_General_Data_Protection->anonymize_ip_votes, Forminator_Form_Entry_Model::get_older_entry_ids

[30-Jan-2019 16:59:38 UTC] WordPress database error Table ‘alcornnelsonllc_wpmudev_host.wp_q5_frmt_form_entry’ doesn’t exist for query SHOW FULL COLUMNS FROM wp_q5_frmt_form_entry made by do_action(‘wp_ajax_nopriv_forminator_submit_form_custom-forms’:wink:, WP_Hook->do_action, WP_Hook->apply_filters, Forminator_CForm_Front_Action->save_entry, Forminator_CForm_Front_Action->handle_form, Forminator_Form_Entry_Model->save

We’ve tried flushing the object cache, but the errors still occur, was wondering if you could take a look and see if something went wrong with the migration.

We do have a managed backup from the original site created with snapshot if required.

Initially there was problems accessing the staging site too, but this was solved via LiveChat earlier.

Fri, 1 Feb 2019 6:55:58
  • Adam
    • Support Gorilla

    Hello Nathan

    I hope you’re well today and thank you for contacting us!

    I checked the site and apparently the table was really missing. To be precise: there is a “temp” table of that name in the database which means that while it was imported form backup file it wasn’t, for some reason, fully processed.

    However, not knowing whether it contains valid data or not, I didn’t risk renaming it to the proper name. Instead I have downloaded the backup file, extracted the table from there and manually imported it to your database.

    It’s no longer missing so I believe it should be fine now but please keep an eye on the error log. The last entry of that error I can see was on 01-Feb-2019 12:54:31 UTC. Let me know if it goes back, though I believe it shouldn’t.

    Unfortunately, since it’s already after migration and as far as I’m aware the original site is also no longer available, I’m not quite able to track down what/why happened but I’d like to know how the site was migrated: was it done manually, with our Shipper or some other plugin? I’m asking so we could keep an eye on such migrations.

    Best regards,

    Adam

  • Nathan
    • Getting there

    Okay do that’s strange. I used shipper to migrate but there were issues, especially with a certain plugin. The plugin was deactivated via FTP and the migration continued. You can few past chat history for more details on that.

    Speaking of, I’ve been having issues trying to install that same plugin as well.

  • Adam
    • Support Gorilla

    Hi Nathan

    Thank you for getting back to me and I’m sorry for the delay.

    I have checked the site’s database again and I think that apart from additional restoration of the database this requires also additional investigation, as you have migrated the site with our Shipper. The issue, causing the db errors, seems to be related to the fact that, as I can see now, there’s still some tables that are “temporary migration tables” that, apparently, were not fully cloned to “production” tables.

    For example: there’s a _postmeta table and _postmeta_temp – those are supposed to be the same and in fact the _temp one shouldn’t even be there after migration.

    That being said, I have asked our developers for consultation on this. I’ve provided them with information about the case and the relevant backup (Jan 22nd) so they could check it to make sure that db is fully restored and to avoid such issues in future.

    We’ll update you here as soon as we got more information from them.

    Kind regards,

    Adam

  • Kostas
    • CTO

    Nathan ,

    I’m sorry for the inconvenience with Shipper, it seems that something went wrong during the migration and I’ve forwarded this to Shipper developers for further inspection.

    In the meantime I could help resolve everything by doing a manual restoration of your site if you like from your backup from Jan 22nd to resolve all current issues that you might be facing.

    Would that help out, or is everything ok at the moment as is? Sorry for asking but I was a bit confused from your last reply. The last errors that I see is from a missing table in the database, so that tells me that the database isn’t yet fully recovered.

    Regards,

    Konstantinos

    • Kostas
      • CTO

      Sure Nathan , I’ll be happy to do it.

      Allow me some time to restore the website via the backup and I’ll reply to you here again when everything is finished. Please don’t make any changes during this time as they will be lost and to avoid any interference with the restoration.

      Regards,

      Konstantinos

  • Kostas
    • CTO

    Nathan ,

    The restoration is complete. Could you please login to your Admin and check your Plugins settings? Since the backup was from a different server some might need re-configuration. For example I see that the ‘WP_Estimation_Form’ is looking at the old Uploads directory and throws some errors as it tries to create folders/files into a non-existing directory etc. Those kinds of errors are expected since the file paths are not the same and they might as well be updated on their own even when you log in to your admin and transients/cache refreshes.

    Other than that particular error everything else seems fine and as it should but a confirmation from you would mark this as complete.

    Tell me if I can help in any other way!

    Regards,

    Konstantinos