Skip to content

First SIGTERM is ignored #11

@davidor

Description

@davidor

It looks like Falcon does not react to the first kill sent. I need to send it twice to terminate.
For example, when starting Falcon with bundle exec falcon serve --bind http://0.0.0.0 -p 4000 --count 2:

 0.12s     warn: Falcon::Command::Top [oid=0x2b0ba3d5ded0] [pid=20356] [2020-03-24 14:13:54 +0000]
               | Updating Encoding.default_external from US-ASCII to UTF-8
 0.12s     info: Falcon::Command::Serve [oid=0x2b0ba3d5dc00] [pid=20356] [2020-03-24 14:13:54 +0000]
               | Falcon v0.35.6 taking flight! Using Async::Container::Forked {:count=>2}.
               | - Binding to: #<Falcon::Endpoint http://0.0.0.0:4000/ {:port=>4000}>
               | - To terminate: Ctrl-C or kill 20356
               | - To reload configuration: kill -HUP 20356
 0.55s     info: Async::Container::Process::Instance [oid=0x2b0ba3d55c30] [pid=20373] [2020-03-24 14:13:54 +0000]
               | - Per-process status: kill -USR1 20373
 0.55s     info: Async::Container::Process::Instance [oid=0x2b0ba3d55de8] [pid=20370] [2020-03-24 14:13:54 +0000]
               | - Per-process status: kill -USR1 20370

The first kill 20356 is ignored. The second works.

I have this problem with all the 0.35.x versions. The latest 0.34 seems to work fine.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions