WARNING: Error while sending QUERY packet. PID=82827

Hi, I have two websites on the same host both running BackWPup and Wordfence. Since about mid-May I have been getting the same “Query Packet” warnings on my log file for one site, but not the other. BackWPup on that site operates just fine with no warnings, as it has previously always done on both sites.

If it would help I can run and send debug log files on each site.

Also, on the latest backup I am also now getting an error message regarding “… wp-content/db.php” not following. Do I need to start a new post for this?

Please advise.

Hi not sure if this will help any of you, but my problem is now resolved, and not only have the various Query Packet WARNING messages disappeared, and the other warning I got re db.php, but the backup job is completing in 60-63 seconds when previously it was taking up to 500 seconds and sometimes more.

In terms of the plugin settings all I did was change to “.tar.gz” compression. But, I also cleaned out some other plugins file “remnants” from wp-content/plugins that had been left behind by previously deleted plugins.

That’s it, and, luckily for me, voila! BackWPup and Wordfence both still functioning fine together.

Cheers Paul

How did you enable .tar.gz? I only have Gzip and Bzip2

When I edit my backup job, under the General tab-> Archive Format I have radio buttons for:
Zip
Tar
Tar GZip and
Tar BZip2

Tar Gzip gives me a file named “…Backwpup-date-time.tar.gz”

Hope this helps

This fixed it for me too. Thanks @choicesnz for posting that.

Who would have thought!

After changing to Tar GZip the problems still exist.

Frank

I have the same problem since June 18. I do however use tar.gz and have since the beginning. Seems however like the backup is done anyway, but have no idea if it is saved correctly or what happens if I should try to restore…

[02-Jul-2016 10:15:28] WARNING: Error while sending QUERY packet. PID=24797
[02-Jul-2016 10:15:28] One file deleted on FTP server
[02-Jul-2016 10:15:28] One old log deleted
[02-Jul-2016 10:15:28] WARNING: Job finished with warnings in 540 seconds. Please resolve them for correct execution.

The same problem like me.
How important are the errormessages regarding a restore?

I hope they are found a solution fast.

Frank

I’ve remembered that one other thing I did was to de-activate Backwpup, then later re-activated it. I guess it’s unlikely that made any difference but can’t hurt to try.

I was considering deleting then re-installing to see if that helped, but luckily didn’t need to. But that may be worth trying also. Of course you’d have to set your backup jobs up again, but that’s not too onerous.

Cheers
Paul

I don’t think it’s a problem, truth be told. In all instances, the backups appear to be successful and complete. A warning vs an error.

Sorry for my terrible english.

All my Problems are solved.

First I deleted all Backup-Jobs and installed the Backup-Jobs new.
– The problems still exist on both different Homepages on both different Hosters.

Than I deleted (deinstalled) BackWPup komplete and installed it again.
I also created the Bachup-Jobs new.

After this, all errormessages are gone.
All my Backups are now running without any errors.

Greetings Frank

@frank9652: now where a difference between the settings interesting.

I will sent you a Logfile from the new installation.

Frank

Actually what makes more sense as the root cause of the problem is this: https://stackoverflow.com/questions/30753674/error-while-sending-query-packet

You guessed right MySQL have limitation for size of data, you need to break your query in small group of records or you can Change your max_allowed_packet by using SET GLOBAL max_allowed_packet=524288000;

So here is the hypothetical scenario that appeared that uninstalling/reinstalling the plugin worked to fix the problem. The root cause of the issue/problem is the Data Type or the Data itself in a particular DB Table. For whatever odd reason or maybe just a coincidence or maybe an old problem with a particular DB table no longer exists after uninstalling/reinstalling the plugin. For that to be true the plugin would have to reusing or storing something that was previously part of the root problem, which actually has something to do with the Data Type or Data itself. So let’s say whatever the problem was that previously existed for a particular DB Table no longer exists and then you uninstall/reinstall the plugin and whatever old stored data (setting) no longer exists in that plugin. Then when you reinstall the plugin and root problem Data Type or Data in a particular DB no longer exists then the root problem is gone and the plugin settings do not store that problem.

If nothing has changed in how the plugin does what is does then the error should still be occurring. So logically the root cause has to do with the DB itself or a particular DB Table/Type/Data or of course a DB config setting.

Another possible clue that I was looking at was maybe this has to do with SSL? I would be curious to know how many people have SSL websites that are experiencing this particular issue/problem/error.