-
Notifications
You must be signed in to change notification settings - Fork 106
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
stale pidfiles not removed #11
Comments
Quick update: this situation can happen if the |
Oh you are correct:
The nginx_clean command has two optional flags which imho are not well named:
So it seems like we should have another flag, something like Even if that was the case, I think that from the user's perspective instead of seeing a I guess if this was happening we would at least want to know that stale pid files were automatically deleted - like log a warning somewhere. |
Since you are using the rpms from the /latest/ I can make sure to include a fix for this before we generate a new version. |
That'd be great, yes, thanks! |
Hi!
I just noticed that if a user PUN goes away, its pidfile in
/var/run/nginx/{%user%}/passenger.pid
stays there, which causes 503 "Service unavailable" errors from the user's perspective.I would have expected
nginx_stage nginx_clean
to remove those stale pidfiles, but that's not the case:Is there a way to automatically remove those pidfiles, so the PUN could be restarted on-demand, or should I just implement a cron job to remove them?
This is with
ondemand-1.4.3-2.el7.x86_64
on CentOS.Thanks!
The text was updated successfully, but these errors were encountered: