I am getting this error on my WordPress site "PHP event: code E_WARNING: Error while sending QUERY packet. PID=2238124 (line 2007, wp-includes/wp-db.php)
Hello and sorry for your issue. This is probably an issue with your PHP version, PHP.ini configuration, or MySQL/MariaDB settings. Please contact Live Support for further assistance.
Hello and sorry for your issue. This is probably an issue with your PHP version, PHP.ini configuration, or MySQL/MariaDB settings. Please contact Live Support for further assistance.
I too had this issue. I had to increase settings in my php.ini file to:
But even after this I still had this issue. In tracking down what cmd that was associated with that PID in the similar error in this post, I found it to be associated with php-fpm. Turns out, my RPM database had gotten corrupted and had to be rebuilt.
But even after this I still had this issue. In tracking down what cmd that was associated with that PID in the similar error in this post, I found it to be associated with php-fpm. Turns out, my RPM database had gotten corrupted and had to be rebuilt.
This is a good insight. If you're using php-fpm and initially changing the values in your php.ini does not work, you should start troubleshooting further up the chain like you did here. Php-fpm has some significant speed advantages, but can run into situations like this.
I too had this issue. I had to increase settings in my php.ini file to:
memory_limit = 384M
max_input_time = 60
max_input_vars = 3000
Then restarted PhP
But even after this I still had this issue. In tracking down what cmd that was associated with that PID in the similar error in this post, I found it to be associated with php-fpm. Turns out, my RPM database had gotten corrupted and had to be rebuilt.
I too had this issue. I had to increase settings in my php.ini file to:
memory_limit = 384M
max_input_time = 60
max_input_vars = 3000
Then restarted PhP
But even after this I still had this issue. In tracking down what cmd that was associated with that PID in the similar error in this post, I found it to be associated with php-fpm. Turns out, my RPM database had gotten corrupted and had to be rebuilt.
This is a good insight. If you're using php-fpm and initially changing the values in your php.ini does not work, you should start troubleshooting further up the chain like you did here. Php-fpm has some significant speed advantages, but can run into situations like this.