Skip to content

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

@ghost

Description

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions