Killing abandoned process on Heroku

Heroku

Heroku Problem Overview


I killed an IRB prompt in a not-so-graceful manner (started with heroku run irb), and now I've got a zombie process which I can't seem to kill:

Process       State               Command
------------  ------------------  ------------------------------
run.3         up for 2h           irb -r ./init.rb
web.1         up for 0s           thin -p $PORT -e $RACK_ENV -R $HER..

I've tried:

  • heroku restart
  • heroku ps:scale run=0
  • heroku ps:restart run.3

Anyone know how I can force quit it?

Heroku Solutions


Solution 1 - Heroku

I noticed a new ps:stop command added to the Heroku command line client a few days ago:
https://github.com/heroku/heroku/commit/a6d9eb7f314bf2c5f162a508e8d764286fb577bb

I'm not sure if that change made it into version 2.9.0 but it would be worth a try.

Update

This is now in the Heroku Toolbelt. Just run:

heroku ps:stop <process id from heroku ps>

Example:

heroku ps:stop run.8729

Solution 2 - Heroku

Thanks James!! I needed to update my Heroku client first, and it worked like a charm.

$ sudo gem install heroku

$ heroku ps #to view processes

$ heroku stop <process name here>

Solution 3 - Heroku

edit: they've fixed this issue

Heroku doesn't have a way to kill abandoned run.x processes.

But it will be killed automatically after 24 hours.

Solution 4 - Heroku

If anyone else is struggling with killing using something like:

heroku run ps:stop run.789

Killing by id worked for me:

heroku ps:kill 61ff0687-eaf4-4299-9c65-f0b22af7ec67

I got the id using the platform api list dynos - https://devcenter.heroku.com/articles/platform-api-reference#dyno-list

Worked for a detached one-off that was abandoned.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionAshley WilliamsView Question on Stackoverflow
Solution 1 - HerokuJames WardView Answer on Stackoverflow
Solution 2 - HerokuMikeView Answer on Stackoverflow
Solution 3 - HerokuMax TilfordView Answer on Stackoverflow
Solution 4 - HerokuTom ZachView Answer on Stackoverflow