deployer: Deployments timing out on PHP 7.1
Before submitting your issue, please make sure that you’ve checked all of the checkboxes below.
- You’re running the latest release version of Deployer.
- Ensure that you’re running at least PHP 5.6.4, you can check this by running
php -v - You’ve ran
composer install --no-devfrom the root of your installation. - You’ve ran
npm install --productionfrom the root of your installation. - You’ve ran
rm -rf bootstrap/cache/*from the root of your installation. - You have restarted the queue listener and node socket server.
To help us better understand your issue, please answer the following.
Expected behaviour
The deployment should be completed successfully
Actual behaviour
I have multiple servers deployed from one app and all of them used to work fine before ubuntu upgrade (not distro) and php upgrade from 7.0 to 7.1. All of the deployments now stuck at different stages showing “Running” icon endlessly spinning.
Steps to reproduce
I’ve upgraded ubuntu server (not distribution) and upgraded php from 7.0 to 7.1
Environment info
Visit /admin/sysinfo on your install and click the “Get System Report” button. Paste the report here, if you can’t
please provide the following instead.
- Operating System: Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-83-generic x86_64)
- PHP Version: 7.1.7-1+ubuntu16.04.1+deb.sury.org+1 (cli) (built: Jul 7 2017 09:41:45) ( NTS )
- Node Version: v6.11.1
- Database System: MySQL
- Database Version: 5.6.35-1+deb.sury.org~xenial+0.1
- Redis: v=3.2.9 jemalloc-4.0.3 bits=64
- beanstalkd: 1.10
- supervisor config exactly as in installation docs
- php max_execution_time=0 and memory_limit = -1 for both fpm and cli
Logs (see storage/logs/) or other output that would be helpful
Failed jobs table has:
Illuminate\Queue\MaxAttemptsExceededException: A queued job has been attempted too many times
storage/logs/cli-*:
production.ERROR: Pheanstalk\Exception\ServerException: Server reported NOT_FOUND in /var/www/deployer/vendor/pda/pheanstalk/src/YamlResponseParser.php:36
ps aux | grep deployer
root 13031 0.0 3.7 299124 38160 ? S 13:10 0:03 php artisan queue:work --queue=deployer-high,deployer-low --sleep=3 --tries=1 --daemon
root 13032 0.0 3.6 297012 36656 ? S 13:10 0:03 php artisan queue:work --queue=deployer-high,deployer-low --sleep=3 --tries=1 --daemon
root 13033 0.0 3.8 299124 38716 ? S 13:10 0:03 php artisan queue:work --queue=deployer-default --sleep=3 --tries=1 --daemon
root 13615 0.0 3.7 299124 38416 ? S 14:36 0:01 php artisan queue:work --queue=deployer-high,deployer-low --sleep=3 --tries=1 --daemon
I’ve restarted all of the services (supervisor, beanstalkd, redis etc), reset queue jobs, deployer:cleanup. Deployer was the latest release 0.0.45, I then switched to master but no avail.
Some servers fail on “Purge Old Releases”, but when I remove old releases manually on those servers the deployments run successfully for some time but then fail again. One of the servers always fails on gulp prod (similar to #333 ). I’ve spent two days so far but still can’t find solution.
Regards Den
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 22 (11 by maintainers)
This is now fixed in
master. I will tag a release on sunday