Warning: Empty row packet body

Hi!

I am having all kinds of strange issues after a site has been migrated to a new temporary domain, on a different hosting. I have done X and Pro migrations numerous times, and I have never seen such issue.

The links are in the Secure note. I am running in circles with the Hosting support.

The original site is still hosted in a subfolder with Blacksun hosting. It woks normally.

The client has asked Siteground to migrate the site to their server, on a different domain.

The migrated site was upgraded from X to Pro. No issues there.

However, the first issue was that for some reason, the TTBF from my own location was 17 seconds, while everybody else doesn’t have problems. I have cleared all possible caches.

The second problem that arised was that I cannot perform Search and Replace in the Database, using Search Replace plugins. They don’t do anything.

The third problem happened when I have created the Pro header.

Since then, when logged out, I am getting this warning on the Homepage:

Warning: Empty row packet body in /home/customer/www/***/public_html/wp-includes/wp-db.php on line 2030

Warning: mysqli_query(): (00000/0): in /home/customer/***/public_html/wp-includes/wp-db.php on line 2030

Warning: Error while sending QUERY packet. PID=26089 in /home/customer/www/***/public_html/wp-includes/wp-db.php on line 2030

Another problem is that I cannot create a site backup with any plugin. The process takes ages. It seems like it will never end.

Does all this sound like some known pattern to you?

I’d appreciate any thoughts on this.

Thank you!

Hey @Misho,

It’s unlikely that Pro caused this issue. Based on the details you provided, below are the factors I suspect caused the issue. Beyond these points, I could not help further and we’ll need that you set up a test site in the original server and do a fresh WordPress install, then install Pro and then perform migration to a test server in Siteground. This will tell us if there’s a specific conflict with Blacksun host, Pro and Siteground. In this case, we’ll post this issue in our issue tracker for further investigation.

  • The original site is using WP-Optimize and that could have done something in the database before migration or what it did is not compatible with Siteground
  • Settings of the original server might have been carried over to Siteground. Try setting up a fresh WP install in Siteground and only import the WP Content files and the database.
  • Regarding the warning, error display in the Siteground site might have been enabled while enabled in the oringinal site. Disable the error display. If you’re not sure, please check this: https://wordpress.org/support/article/debugging-in-wordpress/

Hope that helps.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.