Skip to content

Conversation

@martin-brennan
Copy link
Contributor

@martin-brennan martin-brennan commented Dec 12, 2025

When the rails server is already running, attempting to start
it again was giving an ArgumentError and outputting the backtrace.
When you are working locally, all you want here is the PID so you
can kill it.

I altered the error message to this in this case:

Unicorn is already running!

kill -9 150044 to stop the existing unicorn master process, then try again.

So you can easily copy and paste the command to stop the existing
server.

The old error:

image

When the rails server is already running, attempting to start
it again was giving an ArgumentError and outputting the backtrace.
When you are working locally, all you want here is the PID so you
can kill it.

I altered the error message to this in this case:

```
Unicorn is already running!

kill -9 150044 to stop the existing unicorn master process, then try again.
```

So you can easily copy and paste the command to stop the existing
server.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants