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.

Sign up for GitHub

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

Jump to bottom

SIGTERM fails to kill puma running as a rack handler #911

Closed

veganstraightedge opened this issue Feb 28, 2016 · 0 comments

veganstraightedge commented Feb 28, 2016

I'm running Ruby 2.3.0, Rails 4.2.5.1 and Puma 3.0.2 on Mac OS X 10.11.3 (15D21).

Repro Steps

Open Terminal.app
Start Puma in a (pretty vanilla Rails) with rails s. (Starts on port 3000. All systems nominal.)
Quit Terminal.app without explicitly stopping Puma (with control-c).
Re-open Terminal.app
Re-start Puma (same as step 2)

=> Booting Puma
=> Rails 4.2.5.1 application starting in development on http://localhost:3000
=> Run `rails server -h` for more startup options
=> Ctrl-C to shutdown server
A server is already running. Check /Users/s/Dropbox/Projects/darkmatter/org-charter-server-rails/tmp/pids/server.pid.
Exiting

The text was updated successfully, but these errors were encountered:

evanphx closed this as completed in

eb6468d

herregroen mentioned this issue

Problem with nohup #1202

Closed

grosser mentioned this issue

allow app to also handle sighup and call super #1527

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment