Pry session timing out because of Puma worker timeout

Asked Oct 25 '17 at 09:29

Active Oct 25 '17 at 09:29

Viewed 1,618 times

Whenever I hit a binding.pry while running an app locally, I enter the pry session as normal, but after about a minute, I see something like this in my server output. [54438] ! Terminating timed out worker: 54455

Then the server seems to run in a loop for a second or two (re-running queries that lead to the pry session) and I return to a new pry session from the same binding.pry, except in this new pry session whenever I type I can't see anything I'm typing. The only way to fix this problem is to quit the server and restart.

I've tried inserting the following line in my config/puma.rb file but it doesn't seem to make any difference. worker_timeout 900 if ENV["RACK_ENV"] == "development"

The only thing that works is setting the number of puma workers I have to 0 in my .env file. E.g PUMA_WORKERS=0

Is there any way around this issue that doesn't involve just eliminating all puma workers?

asked Oct 25 '17 at 09:29

James Stonehill

1,125
10
22

What command are you using to start your Puma server? – garythegoat Oct 25 '17 at 14:52
@garythegoat just using `rails s` but I've also tried `puma -C config/puma.rb` and I doesn't seem to make any difference. – James Stonehill Oct 25 '17 at 17:21
I think your condition is wrong. Try removing it or changing it to `ENV["RAILS_ENV"] == "development"` – Slicedpan Oct 25 '17 at 17:38
In rails you can also do `Rails.env.development?` – garythegoat Oct 25 '17 at 18:07
@Slicedpan it seems you were right. For some reason a this point RACK_ENV is not yet set but RAILS_ENV is set (by my .env file). – James Stonehill Oct 26 '17 at 16:49
Quick note - 5 years on! - puma doesn't have access to `Rails.env` during boot time, so checking ENV["RAILS_ENV"] is required – Phantomwhale Sep 16 '22 at 01:09

Pry session timing out because of Puma worker timeout

0 Answers0