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

Don't call .stop on a server that doesn't exist #1655

Merged
merged 1 commit into from
Feb 20, 2019

Conversation

mipearson
Copy link
Contributor

Ignore the branch name - this turns out to work! Fixes #1523 for us on 3.12.0.

Issue we had was a misconfiguration was causing puma to be SIGTERM'd by ECS before it could set @server to anything, which meant that as it tried to graceful stop it hit #1523, confusing our debugging efforts.

@cpinto
Copy link

cpinto commented Dec 1, 2018

@mipearson I know it's been a while but are you able to share what the misconfiguration was? I'm trying to understand what's the root cause for this error on our production server. Thanks.

@mipearson
Copy link
Contributor Author

@cpinto I don't, sorry. I remember it was something specific to our code. I'd recommend sourcing this branch into your Gemfile if only to see where the source error lies, and then reverting to the gem version once fixed.

@evanphx evanphx merged commit 193674e into puma:master Feb 20, 2019
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

Successfully merging this pull request may close these issues.

None yet

3 participants