Rails won't exit on first CTRL-C

Question

No Rails command will exit on the first CTRL-C. So rails s or rails c require me to hit control CTRL-C a second time and commands that previously wouldn't have required a CTRL-C at all such as rake routes / db:migrate now require me to press it.

The issue is not happening for any of my teammates. I'm on OSX using iTerm2. There are no instances of 'rescue Exception' in the app.

I've just reinstalled mysql using brew and the issue is still present. Rails version 4.0.5 and sql server version 5.6.27. Any idea where the issue might be?

[2016-01-13 16:18:33] INFO  WEBrick 1.3.1
[2016-01-13 16:18:33] INFO  ruby 2.1.2 (2014-05-08) [x86_64-darwin13.0]
[2016-01-13 16:18:33] INFO  WEBrick::HTTPServer#start: pid=2329 port=3000
^C[2016-01-13 16:18:54] INFO  going to shutdown ...
[2016-01-13 16:18:54] INFO  WEBrick::HTTPServer#start done.
Exiting
^C

My hunch tells me it's related to a gem with native extensions, how many of those do you have? :) — bbozo, Jan 18 '16 at 07:17
Try to find `Signal.trap` in the whole codebase. If the signal handler was declared in ruby code, you'll find a `Signal.trap("TERM")` statement. — Dieter Pisarewski, Jan 20 '16 at 00:44
I did find something, but commenting it out did not resolve. Signal.trap 'TERM' do puts 'Unicorn master intercepting TERM and sending myself QUIT instead' Process.kill 'QUIT', Process.pid end — zach, Jan 20 '16 at 00:59
Sorry, my bad, Ctrl + C should send SIGINT, not SIGTERM. `Signal.trap("INT")` — Dieter Pisarewski, Jan 20 '16 at 12:32
No trapping of SIGINT either. I also confirmed that the issue does not happen on a brand new blank project so it's not environment related but specific to this codebase / Gemfile. — zach, Jan 20 '16 at 23:39

score 3 · Answer 1 · edited May 23 '17 at 12:07

3

Honestly Webrick 1.3.1 was released in December 28, 2011 I would suggest moving away from this see webrick answer for the reasons.

As you have said that it happens in rails consoles and other tasks (You should really put this in the question as it helps with debugging) I would suggest it is a gem that is causing this (You should update your rails version anyway) but I would suggest using:

Ctrl-D

This should exit you straight away

edited May 23 '17 at 12:07

Community

1
1

answered Jan 19 '16 at 21:56

Jesse Whitham

824
9
32

The issue happens with Puma as well. I'm not so much looking for a workaround (It's very easy to hit CTRL-C twice) as the underlying cause of the issue. – zach Jan 19 '16 at 23:39

score 2 · Answer 2 · answered Jan 17 '16 at 12:34

I suspect this isn't as much an answer as a suggestion, but I started using Puma by default in my projects a while back, and given that Rails 5 is moving to Puma by default it may not be a bad suggestion.

I use a similar environment, OS X 10.11.2, iTerm 2, tmux, etc. I can't recall when or what prompted it, but at some point my WEBrick projects started behaving this same way, and I started moving them to Puma where possible which didn't seem to show the same behavior.

I know that doesn't really give a clear answer as to what's causing the issue, but also, I too know it's not system performance related.

No dice here. Same behavior. Just wondering...what benefit do you see using puma over webrick in dev? (We're using Nginx in production). — zach, Jan 18 '16 at 03:05

Rails won't exit on first CTRL-C

2 Answers2