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

nginx 1.8 loses pid upon nginx conf change #377

Closed
jshthornton opened this issue Aug 26, 2015 · 6 comments
Closed

nginx 1.8 loses pid upon nginx conf change #377

jshthornton opened this issue Aug 26, 2015 · 6 comments

Comments

@jshthornton
Copy link

When using the repo (1.8) package install on ubuntu 14.04 the pid location is changed from /var/run/nginx.pid to /run/nginx.pid. This causes nginx to delete it's current pid file and not replace it.

@StyleT
Copy link

StyleT commented Jan 6, 2016

Same issue here. Is there a workaround?

@jshthornton
Copy link
Author

@StyleT I just changed the node attribute of the pid location to be what nginx uses by default for the distro.

@StyleT
Copy link

StyleT commented Jan 6, 2016

@jshthornton still not working on Ubuntu 14.04.01 with package install. Right after provision sudo service nginx status returns nginx is not running and this is not true :(

@sean-kang
Copy link

I had the same problem in Ubuntu 14.04 when I used repo and default recipes to set up nginx from nginx.org repository. PID file was deleted although nginx service was running. I fixed the problem by overriding pid attribute as @jshthornton suggested. For example, I added the following attribute to our wrapper cookbook to override pid attribute defined in attribute/default.rb in nginx cookbook.

default['nginx']['pid'] = '/var/run/nginx.pid'

@tas50
Copy link
Contributor

tas50 commented Sep 17, 2017

Thanks for opening this issue. Just today we merged the changes from the chef_nginx fork of this cookbook back to master here. It’s a pretty huge change set and includes over a year of active development that resulted in several major releases. I think there’s a very high chance that this issue has been resolved with that work and at this point I’m going to close this issue out. I’d encourage you to checkout the master branch and please open this issue back up if you’re still having the problem there.

Here’s the changes that were just merged in: #435

@tas50 tas50 closed this as completed Sep 17, 2017
@lock
Copy link

lock bot commented Apr 25, 2020

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.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants