We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello and thanks a lot for this template app.
I noticed in our production environment that issuing a unicorn restart / reload via cap will often not restart the server successfully.
"Reloaded OK" does get printed, however the PIDs do not change and the server still points to the previous release.
Have you ever encountered this issue on your deployments?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hey, glad it's useful. What shows up in your unicorn.log when it fails? On 23 Apr 2014 03:28, "yourtallness" notifications@github.com wrote:
Hello and thanks a lot for this template app. I noticed in our production environment that issuing a unicorn restart / reload via cap will often not restart the server successfully. "Reloaded OK" does get printed, however the PIDs do not change and the server still points to the previous release. Have you ever encountered this issue on your deployments? Thanks in advance. — Reply to this email directly or view it on GitHubhttps://github.com//issues/13 .
— Reply to this email directly or view it on GitHubhttps://github.com//issues/13 .
Sorry, something went wrong.
Thanks for the quick feedback.
I have updated my deploy files with the latest changes I just noticed in this project, will retry and get back to you.
Have not been able to reproduce the problem since, may have been a copy-paste issue.
No branches or pull requests
Hello and thanks a lot for this template app.
I noticed in our production environment that issuing a unicorn restart / reload via cap will often not restart the server successfully.
"Reloaded OK" does get printed, however the PIDs do not change and the server still points to the previous release.
Have you ever encountered this issue on your deployments?
Thanks in advance.
The text was updated successfully, but these errors were encountered: