8.0.27 crashed Staging; 8.0.28 crashed Production

  • Resolved mikebreeze

    (@mikebreeze)


    3 years, 12 months ago

    2 weeks ago I encountered an issue on my staging server. It crashed while updating a number of plugins including wp Google Maps version 8.0.27 . I had GoDaddy troubleshoot the issue and they came back and said that:

    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.

    They bypassed the 2 affected tables and synced staging with prod minus those 2 tables. I was planning on deleting sync tomorrow and then copying production back to staging.

    So today I logged onto production and saw that there was an update to production for wp Google Maps. Version 8.0.28 . So I tried to update it and it crashed my production server. I’m not going to do anything today because it is Thanksgiving. However, tomorrow I will call GoDaddy and see what they can do. If you can offer any assistance I would appreciate it. At this point I just want to back this plugin out of production and then staging. Thanks

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author DylanAuty

    (@dylanauty)

    Hi @mikebreeze,

    Thank you for getting in touch and my sincerest apologies for the trouble experienced.

    Could I ask you to get in touch with us directly at the following link: https://www.wpgmaps.com/contact-us/ – This will allow us to discuss possible debugging steps with you, to ensure this issue is resolved as soon as possible.

    I have had a look at your site, however, I was unable to locate any further information regarding the error from the front-end of the website. I would like to get this resolved as soon as possible from my side and restore your site functionality.

    With regards to the migration issues you are experiencing, this is most likely due to the spatial location data we store in the database. This may cause issues with automated migration tools. With that said, I do believe this issue is separate from the crash you are experiencing on the production site presently.

    Once we have debugged this a bit further, I would be more than happy to assist you with the migration issue as well.

    I look forward to hearing from you and resolving this issue as soon as possible.

    I have had the same issue and reverted back to 8.0.26. Is it possible to get a general update on that, as it seems it does concern other users (including me) as well?

    Thread Starter mikebreeze

    (@mikebreeze)

    I could not get access to the WP database via command line. I was able to ssh to the server, I found the login/pwd in the php-config file. However, when I tried to access the database I got a socket error. So it looks like one can only access the WP database from the WP dashboard. And I was told by GoDaddy that you can’t rename tables in WP. I worked with GoDaddy half of Monday trying to delete staging and sync production back to staging. But it would not sync because of the corrupted tables. So I ended up “resetting” the production server (essentially blowing it away) and started from scratch. Thank goodness this is a very simple site so I think that I can get it back up quickly. The last few weeks have not been fun..

    Plugin Author DylanAuty

    (@dylanauty)

    Hi @mikebreeze and @katjavolker,

    Thank you for your continued time, we do appreciate it.

    As mentioned in my previous response, in most cases automated sync-systems or systems which periodically migrate data from one database to another may fail if they do not fully support spatial data.

    Our marker locations are stored as spatial data to improve performance of maps on-site, allowing for more accurate search results and quicker query times due to the fact that we can leverage position based queries. This is used, as an example, when performing a search with the store locator module.

    Unfortunately, if the system which migrates data between two servers does not support spatial data in it’s the raw format, this data needs to be handled in one of two ways commonly:
    1. Spatial data is encoded when being exported and decoded when imported
    2. Spatial data is ignored, or more specifically, the latlng column in your wp_wpgmza table is ignored and not included in the migration

    We have developed tools to assist with migrating data between servers from within the plugin and also integrated with a migration plugin to assist with this. However, we do not directly integrate with host tools at this stage as our plugin runs within the WordPress environment and as a result we do not have access to those actions.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘8.0.27 crashed Staging; 8.0.28 crashed Production’ is closed to new replies.

Tags