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

Puma process/server didn't stops after procofile stop (production) or ctrl-c (--dev) #20

Open
ghost opened this issue May 23, 2018 · 2 comments

Comments

@ghost
Copy link

ghost commented May 23, 2018

Hi!
Here is a simple sinatra app with puma as a server: https://github.com/vfreefly/simple_app
Procfile from app: web: bundle exec puma -t 5:5 -p ${PORT:-3000} -e ${RACK_ENV:-development}

Environment: ubuntu 16.04
Steps to reproduce:

git clone https://github.com/vfreefly/simple_app.git
cd simple_app

rbenv local 2.5.1
gem install procodile

bundle install
procodile start
procodile stop

After these steps app still works on localhost:3000 and puma process is still alive:

Btw, in case of foreman or heroku local all is fine and app with puma stops correctly. Looks like procofile incorrectly determines puma's real process pid.

@brunow
Copy link

brunow commented Oct 1, 2018

Hi,

I had the same issue, have you fix it in any way ?

@antonyr
Copy link

antonyr commented May 14, 2019

I see that child processes are not getting killed.

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

No branches or pull requests

2 participants