Skip to content

Sending SIGTERM exits with 255 #109

@danstewart

Description

@danstewart

When starting a rails app with thrust rails server, waiting for startup and then sending a SIGTERM using kill -15 <thrust pid> it exits with code 255.

When running just rails server without thrust it exits with code 143, which is the expected code for a succesful SIGTERM shutdown.

I've replicated this with the default app generated by rails new.

The logs I get when sending the SIGTERM are:

{"time":"2026-01-17T11:33:05.964931Z","level":"INFO","msg":"Relaying signal to upstream process","signal":"terminated"}
- Gracefully stopping, waiting for requests to finish
Exiting
{"time":"2026-01-17T11:33:05.978965Z","level":"INFO","msg":"Server stopping"}
{"time":"2026-01-17T11:33:05.979483Z","level":"INFO","msg":"Server stopped"}

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions