Error while sending STMT_PREPARE packet on queued jobs

For those who might have similar issues in the future: DB::connection()->reconnect() seems to work. In my case I wouldn't see the effect because I'm using a daemon to process the jobs, so they are cached. Don't forget to run php artisan queue:restart if you deploy any changes in your jobs!

Hi @jpral, I'm having this issue with a queued event listener. From what I could understand, the problem occurs when Laravel tries to restore the serialized model from the event. For instance:

public function handle($event)
{
    $player = $event->player; // <- here
    [...]
}

Can you explain to me how your "DB::connection()->reconnect()" trick would work?

Thanks!

Any additional information on this? I'm having this error pop up sporadically all over my 5.1 app.

Are you using MariaDB by any chance?

If so, https://laracasts.com/discuss/channels/laravel/stmt-prepare-error-only-with-mysqlnd after investigating I reported it and it has been fixed in Laravel

@REBELinBLUE no, plain MySQL

Interesting... Are you getting the same error though ? "Error while sending STMT_PREPARE packet"

If so the fix should still work https://github.com/laravel/framework/pull/10609/files it was that Laravel didn't have that in the strings it checked for to know the connection has died and so automatically reconnect

@REBELinBLUE cool, thanks! I'll give it a shot.

Interestingly, I've verified that this commit is on my server and the queue worker has been reloaded since the pull, but Rollbar is reporting this to me. I don't have a physical log entry for this, so somehow rollbar is receiving this, but my exception handler is not (which should not be possible). I'll reply here if I discover anything more.

@instanceofmichael or @rebelinblue Did you ever figure out this 'Error while sending STMT_PREPARE packet. PID=1759' that you received related to Laravel queued jobs?

I'm having the same problem on Laravel 5.7.

In the above comments, I don't understand what "DB::connection()->reconnect()" is about and why someone would recommend that because it doesn't seem to address a root cause.

Thanks!

@instanceofmichael and @rebelinblue and @jpral

I still have this problem months later (it has been driving me crazy!) and now has a 500-point bounty: https://stackoverflow.com/q/53469793/470749

What should I be investigating at this point?

How can I discover whether any of my cron jobs or queued jobs are problematic? Thanks.

Any news on this? I've the same problem after updating from 5.7 to 5.8.

I'm using:

• PHP 7.2.17
• MySQL 5.7.26
• Redis 3.0.6
• Horizon

ErrorException: Warning: Error while sending STMT_PREPARE packet. PID=19629
#38 /vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php(61): Doctrine\DBAL\Driver\PDOConnection::prepare
#37 /vendor/laravel/framework/src/Illuminate/Database/Connection.php(326): Illuminate\Database\Connection::Illuminate\Database\{closure}
#36 /vendor/laravel/framework/src/Illuminate/Database/Connection.php(657): Illuminate\Database\Connection::runQueryCallback
#35 /vendor/laravel/framework/src/Illuminate/Database/Connection.php(624): Illuminate\Database\Connection::run
#34 /vendor/laravel/framework/src/Illuminate/Database/Connection.php(333): Illuminate\Database\Connection::select
#33 /vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(2124): Illuminate\Database\Query\Builder::runSelect
#32 /vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(2112): Illuminate\Database\Query\Builder::Illuminate\Database\Query\{closure}
#31 /vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(2598): Illuminate\Database\Query\Builder::onceWithColumns
#30 /vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(2113): Illuminate\Database\Query\Builder::get
#29 /vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php(519): Illuminate\Database\Eloquent\Builder::getModels
#28 /vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php(503): Illuminate\Database\Eloquent\Builder::get
#27 /vendor/laravel/framework/src/Illuminate/Database/Concerns/BuildsQueries.php(77): Illuminate\Database\Eloquent\Builder::first
#26 /vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php(448): Illuminate\Database\Eloquent\Builder::firstOrFail
#25 /vendor/laravel/framework/src/Illuminate/Queue/SerializesAndRestoresModelIdentifiers.php(85): App\Jobs\Zipimport::restoreModel
#24 /vendor/laravel/framework/src/Illuminate/Queue/SerializesAndRestoresModelIdentifiers.php(55): App\Jobs\Zipimport::getRestoredPropertyValue
#23 /vendor/laravel/framework/src/Illuminate/Queue/SerializesModels.php(45): App\Jobs\Zipimport::__wakeup
#22 [internal](0): unserialize
#21 /vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(42): Illuminate\Queue\CallQueuedHandler::call
#20 /vendor/laravel/framework/src/Illuminate/Queue/Jobs/Job.php(86): Illuminate\Queue\Jobs\Job::fire
#19 /vendor/laravel/framework/src/Illuminate/Queue/Worker.php(327): Illuminate\Queue\Worker::process
#18 /vendor/laravel/framework/src/Illuminate/Queue/Worker.php(277): Illuminate\Queue\Worker::runJob
#17 /vendor/laravel/framework/src/Illuminate/Queue/Worker.php(118): Illuminate\Queue\Worker::daemon
#16 /vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(102): Illuminate\Queue\Console\WorkCommand::runWorker
#15 /vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(86): Illuminate\Queue\Console\WorkCommand::handle
#14 /vendor/laravel/horizon/src/Console/WorkCommand.php(46): Laravel\Horizon\Console\WorkCommand::handle
#13 [internal](0): call_user_func_array
#12 /vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(32): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}
#11 /vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(90): Illuminate\Container\BoundMethod::callBoundMethod
#10 /vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(34): Illuminate\Container\BoundMethod::call
#9 /vendor/laravel/framework/src/Illuminate/Container/Container.php(576): Illuminate\Container\Container::call
#8 /vendor/laravel/framework/src/Illuminate/Console/Command.php(183): Illuminate\Console\Command::execute
#7 /vendor/symfony/console/Command/Command.php(255): Symfony\Component\Console\Command\Command::run
#6 /vendor/laravel/framework/src/Illuminate/Console/Command.php(170): Illuminate\Console\Command::run
#5 /vendor/symfony/console/Application.php(908): Symfony\Component\Console\Application::doRunCommand
#4 /vendor/symfony/console/Application.php(269): Symfony\Component\Console\Application::doRun
#3 /vendor/symfony/console/Application.php(145): Symfony\Component\Console\Application::run
#2 /vendor/laravel/framework/src/Illuminate/Console/Application.php(90): Illuminate\Console\Application::run
#1 /vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(122): Illuminate\Foundation\Console\Kernel::handle
#0 /artisan(37): null

@gotesla did you get to the bottom of this at all?

I just started getting this issue also on L.8, redis and horizon.

Warning: Error while sending STMT_PREPARE packet. PID=10968

However it looks like the queue jobs are still going through as they don't appear in the Failed Jobs table. Is this the same for other people?

Also in Sentry I noticed that this Exception is only being report at 'warning' level as opposed to error.

Thanks

I am experiencing this same issue after an upgrade from Laravel 5.7 to 5.8, although that might be just a coincidence. It only occurs sporadically.

Same here, I started to get this error after upgrading to 5.8

Im getting this error via sentry too.

Same here!

Stack:

• Ubuntu (v18.04)
• PHP (v7.2.15)
• Laravel (v5.8.26)
• Horizon (v3.2.4)
• Sentry (v1.0.2)

If anyone knows why this happens please let me know!

Perhaps we should comment on the issue below, to siginify many people are dealing with this problem.

https://github.com/laravel/framework/issues/28920

I had the same problem with my laravel v6.18.0. And the error stopped coming to Sentry after update sentry/sentry-laravel library from v1.5.0 to v1.8.0 by command composer update sentry/sentry-laravel.