You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.
Hi, we're seeing the following MySQL error when running a job through the queue worker. When running the same class outside the queue environment the error doesn't appear.
PHP Warning: Error while sending QUERY packet. PID=7741 in private/lib/core/db.class.php on line 134
We've checked the query and the max packet size / timeouts in MariaDB and everything is within tolerances. The query is a simple update which updates a single row in the DB. We're using the MySQLi extension and php5-mysqlnd.
Any idea why this would only happen in php-resque-ex ?
Unfortunately although it's not just a PHP warning, the query has actually failed.
Like I said, this is not related to query size (although the error would seem to indicate that), the query was only about 100 bytes.
UPDATE: After some further testing this only seems to happen when sending an UPDATE query as the first query to the SQL server. If I send a dummy SELECT first then we don't get the error!?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, we're seeing the following MySQL error when running a job through the queue worker. When running the same class outside the queue environment the error doesn't appear.
PHP Warning: Error while sending QUERY packet. PID=7741 in private/lib/core/db.class.php on line 134
We've checked the query and the max packet size / timeouts in MariaDB and everything is within tolerances. The query is a simple update which updates a single row in the DB. We're using the MySQLi extension and php5-mysqlnd.
Any idea why this would only happen in php-resque-ex ?
PHP version: 5.5.9
php-resque-ex version: 1.3.0
MariaDB version: 10.0.30
The text was updated successfully, but these errors were encountered: