Error while sending query packet mysql

BloggingLove

How to Fix a “Warning: Error While Sending QUERY Packet”

July 2nd, 2017 | by Ravi Chahar || Leave a comment |

Just a few days ago, I noticed an unusual error. It was a warning regarding the packet which wasn’t sent properly. The notice was “Warning Error while sending QUERY packet”.

There were also mentioned some parameters to let me know about the file and the line number.

If you’re using WordPress, you should know about the common WordPress errors and their solutions. You can’t expect to run it perfectly all the time.

Sometimes, you need to take some actions to maintain it properly.

In this post, you will learn the reasons and the solutions of “Warning error while sending QUERY packet”.

How does the Error Message Look Like

As mentioned earlier, the notice will have the warning message with a proper packet number.

Let me tell you that error is related to the database of your WordPress website. You will see a related file and the line number too.

Let me show you an example.

As you can see, it also mismatches the design of the website. It has shifted the excerpt of the article downward. It’s not the only case, you can get a different error.

It’s because the packet and the line numbers would be different.

What’re the Reasons to Get Such Warning

This error is appearing because of the maximum number of database connection requests have made. No further requests are allowed.

It happens on the shared server. The worst part is that your web hosting can’t allow you to increase the number of requests to the database.

It will directly impact other users.

The reason of these requests may be anything. It maybe the size of your website or any plugin you use which is making so many database requests while updating it.

Let me mention that error isn’t bad for anything. It’s just a warning to let you know that your website’s database connection is dealing with some high time.

Removing “Warning Error While Sending QUERY Packet” Message

As mentioned above, if you’re having a shared hosting then it can be the problem. To fix this, you can shift to a managed web hosting.

#1. Managed Web Hosting

To fix this, you can shift to a managed web hosting. It’s only recommended if you have a bigger website otherwise, no need to spend that much of money.

You can get a new managed hosting from WPEngine. It’s because the maximum number of requests allowed are more on a managed server and it can be increased accordingly.

But if you don’t want to change your server then go to the next step.

#2. Optimize the Database

As per the line number and the path, you can easily guess that everything is happening somewhere in the database.

You should always clean up your WordPress database using a plugin. You can use the plugin like WP-Sweep and WP-Optimize.

Such plugins clean the unwanted database tables which are created when you update any post, publish a post, add new media files and delete those.

You should always know the way to uninstall a WordPress plugin completely so that no extra tables remain in the database.

The point is keeping the size of the database as minimum as possible.

As you know, having a bigger WordPress website can be brainstorming for the browser. It can take so much time to get loaded.

And there are many static pages and images are present on your WordPress website which should be cached by a CDN to improve its speed.

A CDN also acts like a security firewall.

Overall, it improves the user experience and helps you to make fewer database requests. You can set up CloudFlare for WordPress for free.

If you have enough budget then a paid CDN is always a better option.

I Hope You Got a Solution to Your Problem

As I have said earlier, such type of error is unique and different for all.

I have gotten a different packet, you can get something else. But the reasons are the same. The database gets exhausted due to more number of requests than its capacity.

That’s the reasons it’s always recommended to keep your database optimized. I am sure, you can fix this “Warning Error While Sending QUERY Packet”. If you still have any doubt, feel free to drop a comment.

You can also connect with us on Twitter, LinkedIn, and Facebook.

Источник

Backup and restore

Backup Fails — Warning: Error while sending QUERY packet.

Backup Fails — Warning: Error while sending QUERY packet.

I updated to the latest code last week and over the weekend I started getting errors in the backups of two of my course. The regular emails detailing the backup status reported the following

Some of your courses weren’t saved!!

I received this email continually, every 30 minutes, over the weekend like it was stuck in a loop. (Note that the cron job runs every 10 minutes)

Looking at the backup logs reports at http://My.site/report/backups/index.php it shows a couple of courses with a status of “Unfinished”. When I go into the courses all seems fine but if I try and run a backup of the course or if I try and restore a copy of this course from a backup I get an error page showing 2 lines:

Error writing to database

Error reading from database

Sometimes I also get the added information

Warning: Error while sending QUERY packet. PID=3832 in C:moodlelibdmlmysqli_native_moodle_database.php on line 902

Front server is Windows 2008 R2 x64, IIS 7.5, PHP 5.3.8, Moodle 2.3.3+ (Build: 20121123)

Back server is Windows 2008 R2 x64, MySQL 5.1.33,

Server check reports that all is OK

Re: Backup Fails — Warning: Error while sending QUERY packet.

Qualification for this response . don’t run Windows so have not seen that exact error + you asked for ‘ideas’ . soooooooo .

There’s something in those 2 specific courses (obviously), but what?

Check moodledata/temp/backup/ folder for ‘hashnamed’.log files. 0 byte .log files are successful backups and any .log file with more than 0 bytes indicates issues with associated course. Open .log files with NotePad and see what they say. They will provide hints as to module/activity/etc.
IF you see any ‘hashnamed’ folders by the same name as the .log files those are the temporary folders Moodle uses to build the backup .mbz files. Inspection of those folders probably wouldn’t hurt.
BTW, they can be safely removed from the operating system level.

Also, as your 2 has grown, data has grown so one might need to tweak mysql settings for max_allowed_packets.

If that is the problem one might see references in mysql logs or web error logs
MySQL server’s default max_allowed_packet value is 1MB.
See: https://dev.mysql.com/doc/refman/5.1/en/packet-too-large.html

‘spirit of sharing’, Ken

Re: Backup Fails — Warning: Error while sending QUERY packet.

Thanks for that. I will start going through that now

Re: Backup Fails — Warning: Error while sending QUERY packet.

Now using Moodle 2.4 but no luck with identifying the cause of the errors. I tried to attach a copy of the log file but as it’s over 6 meg, it would not let me upload. I could not find anything in it as it look s like :-

K §wA activities/ PK §wA activities/assign_15841/ PK —wA™ ¯žô â » activities/assign_15841/assign.xmlÅUÛnœ0>ÏWX¼§²ŽÄ:ZEªÔ·JMž+/6V°ÙK¿¾Æ†…½¥R£Mßð9sfÎcÈŸv•@h4WrÄ_¢ ,ãr½^_¾Þãà‰Üå´0|ÃÍq¶æI€*ÅZÝ1Îp€¤,ª5_Ë JØ™.*É0ƹC(÷ì!U‡Y´S’eQ¨V[½JnÐýX>£xy£oÏ/(‰â8]¤qiE¾ P[EÙ¨xƒòЇLÂKÕTÔ¨§ú£ bK÷Z¿©-]4¼6v.ÄÖ¼LxQÝÀ¤Ô€nW×Ý0uWà
ãe#ÂZ’8ÃúPL*ÃK^PãRXKçàÜU¼(8’¼ˆµÀ,EâYÍpŠ#kfÀ†ÑµtQ6ªò’äñqnäjϱn(‚çyèŸ 3|Œ¡

¼Ž…Pš’Ðùœ)>(æ°5I‰TäxêãNñP–`e·ì“…ÿä¥5#5-Öˆf±85`¯–µD%fpÜ´kfÑVSuØ€‹¹F)Bí Ü ;ÓÓ2R‰±N
6Hs±D‹kššñиÓÂ^ó^Mù»í_‚hi;Åξñq8[ÀeË”MŽ`–»ó&… í³Ã(ÊðwÞ£Ôpÿô`ãhj a‡Nàuò

FÄó¼”ðîmî¢üYÕyª§,^ y’ßÀ³±êæô.,Ì¿ªQóW`| ³PK —wAÌÂbˆ3 7 # activities/assign_15842/grading.xml³±¯ÈÍQ(K-*ÎÌϳU2Ô3PRHÍKÎOÉÌK·U
qÓµP²·ã²I,JM,Òú PK —wAãÈOOX # activities/assign_15842/inforef.xml³±¯ÈÍQ(K-*ÎÌϳU2Ô3PRHÍKÎOÉÌK·U
qÓµP²·ã²ÉÌKË/JM³ãRP°)-N-‚²¡ ³PK •wARyRq ˆ # activities/folder_13102/inforef.xml³±¯ÈÍQ(K-*ÎÌϳU2Ô3PRHÍKÎOÉÌK·U
qÓµP²·ã²ÉÌKË/JM³ãRP°IËÌI…²¡ ߟ6ñž-²RñV@„ÜxV”¤ñ“š’5>#$f‹(¬2/]”à ³ÄCÖQCјRä,]Ó×,™sO•myÍÖ“ $Y2…–çœgt•nW/[º!YÒ׶P˜A>àÚH²±lˆ,ì°Æ³ F³d=lò›YñªU[™!]ÿ9™$³L3ܨõÙöûk%ÅÏî1k,TY °[°/Å«Î9`å°“åáãt ³PK •wA¿¡Œñn # activities/folder_13198/inforef.xml³±¯ÈÍQ(K-*ÎÌϳU2Ô3PRHÍKÎOÉÌK·U
qÓµP²·ã²ÉÌKË/JM³ãRP°IËÌI…²¡ Средняя оценка: —

Re: Backup Fails — Warning: Error while sending QUERY packet.

Strange . on a Linux box, the data/temp/backup/ directory on a 2.4 not having issues shows log files like:

[root@sos backup]# ls -l
total 0
-rw-rw-rw- 1 apache apache 0 Dec 4 17:41 699f1b0851f0dff3f7701e7a6fe6f52b.log

And that contains 0 bytes . ie, nothing in it . indicating a successful backup.

If you find a log file in that location, in previous versions of Moodle, they would be text (NOT zipped) and opening one in a text editor was all that was needed to inspect. So open NotePad first, then have it look for .log files in the appropriate directory.

Let’s have a look see at your DB:

select * from mdl_files where component=»backup»;

From the looks of what was copied and pasted, was a file with a hashname like 699f1b0851f0dff3f7701e7a6fe6f52b opened? or attempted to open it? That really might be a hash named *zip* file.

Copy that hash named file out into a temp directory. Rename it:

699f1b0851f0dff3f7701e7a6fe6f52b to 699f1b0851f0dff3f7701e7a6fe6f52b.zip

It is the failed backup, BTW. Inspection of it can sometimes help find a clue as to what is NOT being backed up.

Also suggest turning on debugging and run a backup to see what it says.

‘spirit of sharing’, Ken

NOTE: can’t believe no Windows users bother to respond! Shame on them!

Re: Backup Fails — Warning: Error while sending QUERY packet.

Thanks for the info. I managed to spend a bit of time on it today, but not enough. It looks like what I thought was a backup log was not and adding the .zip helped there. I have dumped the data from MySQL but not had the time to go through it as yet.

Debug was set to all and this showed only two lines when I tried the backup, «Error writing to database» and «Error reading from database». Changing debug to Developer gave the following when I tried to do a manual backup of one of the course:-

Error writing to database Debug info: MySQL server has gone away INSERT INTO mdl_backup_controllers (backupid,operation,type,itemid,format,interactive,purpose,userid,status,execution,executiontime,checksum,controller,timecreated,timemodified) VALUES(. ) [array ( 0 => ‘8f057ac415a2423123f31d7af7478f8e’, 1 => ‘backup’, 2 => ‘course’, 3 => 141, 4 => ‘moodle2’, 5 => 1, 6 => 10, 7 => ‘1370’, 8 => 500, 9 => 1, 10 => 0, 11 => ‘391b9edf378a74ea52cb0af8687fef03’, 12 => lots of stuff that goes on in line 12 13 => 1355280794, 14 => 0, )] Error code: dmlwriteexception Stack trace: line 429 of libdmlmoodle_database.php: dml_write_exception thrown line 1107 of libdmlmysqli_native_moodle_database.php: call to moodle_database->query_end() line 1149 of libdmlmysqli_native_moodle_database.php: call to mysqli_native_moodle_database->insert_record_raw() line 87 of backuputildbopsbackup_controller_dbops.class.php: call to mysqli_native_moodle_database->insert_record() line 333 of backupcontrollerbackup_controller.class.php: call to backup_controller_dbops::save_controller() line 137 of backuputiluibase_ui.class.php: call to backup_controller->save_controller() line 91 of backupbackup.php: call to base_ui->save_controller()

Error Reading from database Debug info: MySQL server has gone away SELECT bi.id, bp.id AS blockpositionid, bi.blockname, bi.parentcontextid, bi.showinsubcontexts, bi.pagetypepattern, bi.subpagepattern, bi.defaultregion, bi.defaultweight, COALESCE(bp.visible, 1) AS visible, COALESCE(bp.region, bi.defaultregion) AS region, COALESCE(bp.weight, bi.defaultweight) AS weight, bi.configdata , ctx.id AS ctxid, ctx.path AS ctxpath, ctx.depth AS ctxdepth, ctx.contextlevel AS ctxlevel, ctx.instanceid AS ctxinstance

FROM mdl_block_instances bi JOIN mdl_block b ON bi.blockname = b.name LEFT JOIN mdl_block_positions bp ON bp.blockinstanceid = bi.id AND bp.contextid = ? AND bp.pagetype = ? AND bp.subpage = ? LEFT JOIN mdl_context ctx ON (ctx.instanceid = bi.id AND ctx.contextlevel = 80)

WHERE (bi.parentcontextid = ? OR (bi.showinsubcontexts = 1 AND bi.parentcontextid IN (. ))) AND bi.pagetypepattern IN (. ) AND (bi.subpagepattern IS NULL OR bi.subpagepattern = ?) AND (bp.visible = 1 OR bp.visible IS NULL) AND b.visible = 1

ORDER BY COALESCE(bp.region, bi.defaultregion), COALESCE(bp.weight, bi.defaultweight), bi.id [array ( 0 => ‘10582’, 1 => ‘backup-backup’, 2 => », 3 => ‘10582’, 4 => ‘10607’, 5 => ‘1280’, 6 => ‘1’, 7 => ‘backup-backup’, 8 => ‘backup-backup-*’, 9 => ‘backup-*’, 10 => ‘*’, 11 => », )] Error code: dmlreadexception Stack trace: line 426 of libdmlmoodle_database.php: dml_read_exception thrown line 960 of libdmlmysqli_native_moodle_database.php: call to moodle_database->query_end() line 628 of libblocklib.php: call to mysqli_native_moodle_database->get_recordset_sql() line 1373 of libpagelib.php: call to block_manager->load_blocks() line 829 of libpagelib.php: call to moodle_page->starting_output() line 729 of liboutputrenderers.php: call to moodle_page->set_state() line 2362 of liboutputrenderers.php: call to core_renderer->header() line 366 of libsetuplib.php: call to core_renderer->fatal_error() line ? of unknownfile: call to default_exception_handler()

I hope to spend some more time on it tomorrow.

Источник

PHP Warning: Error while sending QUERY packet after 1 job #269

I am getting this error, and i have been consistently looking for some solution to get this work around.

PHP Warning: Error while sending QUERY packet.

Even, i closed all mysql connections once the job is done, for the first time job gets done successfully.

Next time I get the above error I mentioned.

The text was updated successfully, but these errors were encountered:

You need to close and reopen the connection when the job starts. Forking reuses everything from the parent process, including the MySQL connection.

We were able to resolve the issue.

@danhunsaker didnt get you, could you please elaborate more?
I am facing the same issue. Here is my snippet:
public function perform()
<
$mysql = Mysql::getInstance();
EH::setErrorHandler();
$user_id = $this->args[‘user_id’];

I am reopening the connection at start, still get a «error while sending query packet». Also, this isnt a packet size issue since it works fine if put in main php thread and not in resque.

Reopening the connection needs to be done inside the perform() method, or if you have multiple jobs, you can add a beforePerform hook and reconnect there. Every job runs in a fork — a completely new process with an exact copy of the old one’s memory contents (though it’s copy-on-write, so it’s still really fast) — so every job needs to reconnect immediately before trying to use the DB, every time.

Источник

What steps will reproduce the problem?

I’m not sure. It seems to happen intermittently. From what I can tell from my researching, it sounds like there’s a MYSQL limit that’s being broken to get a query packet error. However, my queries are nowhere near the max limit. See below query, it’s just running a basic select.

What do you get instead?

I’m getting occasional errors. An example is below:

exception ‘yiibaseErrorException’ with message ‘Error while sending
QUERY packet. PID=6401′ in
/home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/Command.php:900
Stack trace:
#0 [internal function]: yiibaseErrorHandler->handleError(2, ‘Error

while sen…’, ‘/home/bookspro/…’, 900, Array)
#1

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/Command.php(900):
PDOStatement->execute()
#2

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/Command.php(376):
yiidbCommand->queryInternal(‘fetch’, NULL)
#3 /home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/Query.php(247):

yiidbCommand->queryOne()
#4

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/ActiveQuery.php(295):
yiidbQuery->one(NULL)
#5

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/BaseActiveRecord.php(107):
yiidbActiveQuery->one()
#6 /home/bookspro/booksproutapp/common/models/User.php(426):

yiidbBaseActiveRecord::findOne(Array)
#7 /home/bookspro/booksproutapp/vendor/yiisoft/yii2/web/User.php(665):

commonmodelsUser::findIdentity(2507)
#8 /home/bookspro/booksproutapp/vendor/yiisoft/yii2/web/User.php(188):

yiiwebUser->renewAuthStatus()
#9 /home/bookspro/booksproutapp/vendor/yiisoft/yii2/web/User.php(340):

yiiwebUser->getIdentity()
#10

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/base/Component.php(130):
yiiwebUser->getIsGuest()
#11

/home/bookspro/booksproutapp/frontend/controllers/ReviewRequestController.php(72):
yiibaseComponent->__get(‘isGuest’)
#12 [internal function]:

frontendcontrollersReviewRequestController->actionView(’11’,
‘totally-coached…’)
#13

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/base/InlineAction.php(55):
call_user_func_array(Array, Array)
#14

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/base/Controller.php(154):
yiibaseInlineAction->runWithParams(Array)
#15

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/base/Module.php(454):
yiibaseController->runAction(‘view’, Array)
#16

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/web/Application.php(87):
yiibaseModule->runAction(‘review-request/…’, Array)
#17

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/base/Application.php(375):
yiiwebApplication->handleRequest(Object(yiiwebRequest))
#18 /home/bookspro/public_html/index.php(18):

yiibaseApplication->run()
#19 {main}

Next exception ‘yiidbException’ with message ‘Error while sending
QUERY packet. PID=6401
The SQL being executed was: SELECT * FROM user WHERE (id=2507) AND
(status=10)’ in
/home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/Schema.php:633
Stack trace:
#0

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/Command.php(915):
yiidbSchema->convertException(Object(yiibaseErrorException),
‘SELECT * FROM `…’)
#1

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/Command.php(376):
yiidbCommand->queryInternal(‘fetch’, NULL)
#2 /home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/Query.php(247):

yiidbCommand->queryOne()
#3

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/ActiveQuery.php(295):
yiidbQuery->one(NULL)
#4

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/db/BaseActiveRecord.php(107):
yiidbActiveQuery->one()
#5 /home/bookspro/booksproutapp/common/models/User.php(426):

yiidbBaseActiveRecord::findOne(Array)
#6 /home/bookspro/booksproutapp/vendor/yiisoft/yii2/web/User.php(665):

commonmodelsUser::findIdentity(2507)
#7 /home/bookspro/booksproutapp/vendor/yiisoft/yii2/web/User.php(188):

yiiwebUser->renewAuthStatus()
#8 /home/bookspro/booksproutapp/vendor/yiisoft/yii2/web/User.php(340):

yiiwebUser->getIdentity()
#9

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/base/Component.php(130):
yiiwebUser->getIsGuest()
#10

/home/bookspro/booksproutapp/frontend/controllers/ReviewRequestController.php(72):
yiibaseComponent->__get(‘isGuest’)
#11 [internal function]:

frontendcontrollersReviewRequestController->actionView(’11’,
‘totally-coached…’)
#12

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/base/InlineAction.php(55):
call_user_func_array(Array, Array)
#13

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/base/Controller.php(154):
yiibaseInlineAction->runWithParams(Array)
#14

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/base/Module.php(454):
yiibaseController->runAction(‘view’, Array)
#15

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/web/Application.php(87):
yiibaseModule->runAction(‘review-request/…’, Array)
#16

/home/bookspro/booksproutapp/vendor/yiisoft/yii2/base/Application.php(375):
yiiwebApplication->handleRequest(Object(yiiwebRequest))
#17 /home/bookspro/public_html/index.php(18):

yiibaseApplication->run()

Additional info