Takes 2 runs for the FPM pool to be created
Closed this issue · 4 comments
I'm running the cookbook in Test Kitchen on EC2. I'm running the php::default
recipe, installing a few packages and installing and configuring php-fpm. The problem is that the fpm-pool doesn't get created on the first run, it takes 2 runs for it to add the /etc/php5/fpm/pool.d/www.conf
file.
I've tried rearranging the order of the script but doesn't seem to make a difference.
UPDATE
I've also tried using Vagrant on Test Kitchen and the same thing happens.
include_recipe 'php::default'
package "php5-memcached" do
action :install
end
package "php5-mysql" do
action :install
end
package "php5-curl" do
action :install
end
package "php5-mcrypt" do
action :install
end
php_fpm_pool "www" do
action :install
listen node['webnode']['php_listen_path']
user node['webnode']['web_user']['name']
group node['awebnode']['web_user']['group']
max_children 16
start_servers 8
min_spare_servers 4
max_spare_servers 12
end
Cookbook version
1.9.0
Platform Details
EC2
OK I found the problem if anyone is interested. I'm trying to create an fpm pool called www
but in the fpm recipe, it deletes the default resource pool after installing fpm - which is www.conf
. I've changed the resource pool name to web
and it works on first time install. Maybe a slight bug.
It sounds like we should probably warn against using www as a name
Closing due to inactivity.
If this is still an issue please reopen or open another issue. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help!
Thanks,
Sous-Chefs
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.