Warning: Error While Sending Query Packet. Pid=8384 In /var/www/vhosts/mysite/httpdocs/app/tygh/backend/database/mysqli.php

General General Questions
1

Hello there,

I want to send a newsletter from cs-cart to about 130K subscribers! The problem is after a while I will get such an error in backend:

Warning: Error while sending QUERY packet. PID=8384 in /var/www/vhosts/mysite/httpdocs/app/Tygh/Backend/Database/Mysqli.php on line 79

Is it related to server config or something? Should I increase max_allowed_packet on the server?

Thanks

2

Hello there,

I want to send a newsletter from cs-cart to about 130K subscribers! The problem is after a while I will get such an error in backend:

Warning: Error while sending QUERY packet. PID=8384 in /var/www/vhosts/mysite/httpdocs/app/Tygh/Backend/Database/Mysqli.php on line 79

Is it related to server config or something? Should I increase max_allowed_packet on the server?

Thanks

Hello,

This simply means the entire table requested is too big for MySQL to handle. What you need to do is run this query via your MySQL editor or phpMyAdmin 

SET GLOBAL max_allowed_packet=524288000;

If you have any more questions please let me know.

Kind regards,

3

Hello,

This simply means the entire table requested is too big for MySQL to handle. What you need to do is run this query via your MySQL editor or phpMyAdmin 

SET GLOBAL max_allowed_packet=524288000;
If you have any more questions please let me know.

Kind regards,


If not, what does this error mean? Increased, but no result...
4

Please somebody help… Suddenly my site stop working at the checkout process! Nothing was changed at the server…

On the DELIVERY ADDRESS step after pressing NEXT it hanging.
“Ошибка Ой, произошла ошибка (Gateway Timeout). Пожалуйста, попробуйте еще раз.”
Log file contain:
[Mon Apr 08 22:09:15.996320 2019] [:error] [pid 6239] [client 46.138.142.57:40602] PHP Warning: Error while sending QUERY packet. PID=6239 in /home/admin/web/stencil-library.ru/public_html/app/Tygh/Backend/Database/Mysqli.php on line 79, referer: https://www.stencil-library.ru/
[Mon Apr 08 22:09:29.817355 2019] [:error] [pid 6239] [client 46.138.142.57:40602] PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes) in /home/admin/web/stencil-library.ru/public_html/app/functions/fn.log.php on line 80, referer: https://www.stencil-library.ru/
[Mon Apr 08 22:09:29.818266 2019] [:error] [pid 6239] [client 46.138.142.57:40602] PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes) in /home/admin/web/stencil-library.ru/public_html/app/functions/fn.control.php on line 88, referer: https://www.stencil-library.ru/
[Mon Apr 08 22:09:29.819539 2019] [:error] [pid 6239] [client 46.138.142.57:40602] PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes) in Unknown on line 0, referer: https://www.stencil-library.ru/

What I did:
- disable all modules, not results.
- increased memory_limit, no results.

So I did something wrong…

5

Are you on a shared server hosting? Looks like there is 1 1gb memory limit and you have hit that limit

6

You need to find out what is consuming so much memory. Error shows 1024MB which should be more than enough.

7

No, the problem not in memory_limit, it is actually 256 and everything worked during 5 years.



And now everything fine but only step after “delivery address” causing this error. All other things works including admin panel.
And I’m on VPS with 8 go of ram and 80 SSD.

8

Something server side happening. I have an abandoned site on the same VPS and it shows the same behaviors! For that site nothing we’re changed for 7 years or so.

9

Changed my.conf max_allowed_packed from 1M to 16M - no results. But now it is only one line in a log

2019/04/09 07:14:50 [error] 1120#1120: *6888 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 46.138.142.57, server: stencil-library.ru, request: “POST / HTTP/2.0”, upstream: “https://173.249.39.218:8443/”,host: “www.stencil-library.ru”, referrer: “https://www.stencil-library.ru/checkout/”

10

No, the same

Tue Apr 09 07:15:52.095069 2019] [:error] [pid 1553] [client 46.138.142.57:33062] PHP Warning: Error while sending QUERY packet. PID=1553 in /home/admin/web/stencil-library.ru/public_html/app/Tygh/Backend/Database/Mysqli.php on line 79, referer: https://www.stencil-library.ru/checkout/
[Tue Apr 09 07:15:53.531557 2019] [:error] [pid 1553] [client 46.138.142.57:33062] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 139264 bytes) in /home/admin/web/stencil-library.ru/public_html/app/functions/fn.log.php on line 86, referer: https://www.stencil-library.ru/checkout/
2019/04/09 07:27:36 [error] 1118#1118: *7043 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 46.138.142.57, server: stencil-library.ru, request: “POST / HTTP/2.0”, upstream: “https://173.249.39.218:8443/”,host: “www.stencil-library.ru”, referrer: “https://www.stencil-library.ru/checkout/”
[Tue Apr 09 07:31:05.268323 2019] [:error] [pid 7523] [client 46.138.142.57:33354] PHP Warning: Error while sending QUERY packet. PID=7523 in /home/admin/web/stencil-library.ru/public_html/app/Tygh/Backend/Database/Mysqli.php on line 79, referer: https://www.stencil-library.ru/checkout/
[Tue Apr 09 07:31:06.610940 2019] [:error] [pid 7523] [client 46.138.142.57:33354] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 135168 bytes) in /home/admin/web/stencil-library.ru/public_html/app/functions/fn.log.php on line 79, referer: https://www.stencil-library.ru/checkout/
[Tue Apr 09 07:33:24.372769 2019] [:error] [pid 7523] [client 54.36.150.184:33452] PHP Warning: Unknown: A session is active. You cannot change the session module’s ini settings at this time in Unknown on line 0

11

The reason was found and temporary solution applied

12

The reason was found and temporary solution applied

What was it?

13

What was it?


The roots of the problem are not discovered yet as I only 5 minutes ago reaches my notebook and all solutions before were made from mobile.

But The reason is the bad behavior of one standard module - calculation of shipping cost by post. Having troubles with receiving a response from source, it hanging the CMS at all.

Now I've disabled it and everything works. Will explore what the problem with data provider.