Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fpm service not enabled automatically #18

Closed
marpada opened this issue Jun 21, 2014 · 2 comments
Closed

fpm service not enabled automatically #18

marpada opened this issue Jun 21, 2014 · 2 comments

Comments

@marpada
Copy link

marpada commented Jun 21, 2014

When using the fpm recipe on Ubuntu/Debian, the service php5-fpm is not being enabled. Log suggests that the resource on the fpm recipe is conflicting with the definition on providers/fpm.rb

[2014-06-21T08:12:48+00:00] INFO: *** Chef 11.12.8 ***
[2014-06-21T08:13:25+00:00] WARN: Cloning resource attributes for service[php5-fpm] from prior resource (CHEF-3694)
[2014-06-21T08:13:25+00:00] WARN: Previous service[php5-fpm]: /tmp/vagrant-chef-1/chef-solo-1/cookbooks/php/recipes/fpm.rb:70:in `from_file'
[2014-06-21T08:13:25+00:00] WARN: Current  service[php5-fpm]: /tmp/vagrant-chef-1/chef-solo-1/cookbooks/php/providers/fpm.rb:66:in `block in class_from_file'
@priestjim
Copy link
Owner

That's normal. Starting the service should only be done after defining a proper pool using the LWRP. Overriding attributes is also normal.

@marpada
Copy link
Author

marpada commented Jul 1, 2014

My bad. I had placed the socket file in /var/run/php5-fpm/, but didn't realize the content of /var/run is cleared on stop, which prevented the service from starting.

@marpada marpada closed this as completed Jul 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants