Beanstalkd queue using old code after Envoyer Deploy.

HI all,

I have as part of my infrastructure a worker server that processes background events. (Laravel 4.2)

I have set this up with Forge as a non Daemon process and everything seems to work.

However when I deploy with Envoyer, the worker server gets the new code, but the beanstalk process continues to use old code.

Within Envoyer, I am sure php-fpm is restarted.

Running php artisan queue:restart doesn't work, nor does restarting beanstalkd.

When I click restart within the forge interface, then all is good.

What command do I need to add to my envoyer hook to have beanstalkd recognize the new deploy?

Thanks!

Level 2

After a quick envoyer support request to Taylor I (he) solved this as follows:

Setup the queue processor in Forge as a Daemon.

Then the queue:restart process will work properly.

Hope this helps someone!

3 likes

Level 2

I had the same problem and solved it too, by switching to running my queue processes as daemon and adding queue:restart to my deployment hooks.

1 like

Please or to participate in this conversation.