"bin/rails: No such file or directory" w/ Ruby 2 & Rails 4 on Heroku

Question

While following the Rails 4 Beta version of Michael Hartl's Ruby on Rails Tutorial, my app fails to start on Heroku, but runs fine locally with bundle exec rails server. Checking heroku logs -t reveals the following error:

$ heroku[web.1]: State changed from crashed to starting
$ heroku[web.1]: Starting process with command `bin/rails server 
-p 33847 -e $RAILS_ENV`
$ app[web.1]: bash: bin/rails: No such file or directory
$ heroku[web.1]: Process exited with status 127
$ heroku[web.1]: State changed from starting to crashed
$ heroku[web.1]: Error R99 (Platform error) -> Failed to launch the 
dyno within 10 seconds
$ heroku[web.1]: Stopping process with SIGKILL

If I heroku run bash and check the bin directory, I can see that there is not a rails executable:

~$ ls bin
erb  gem  irb  node rdoc  ri  ruby  testrb

What have I done wrong? I followed the tutorial exactly.

score 105 · Answer 1 · answered Jul 20 '13 at 00:41

105

I had this problem also since I upgraded to rails 4.0.0

Run this command

rake rails:update:bin

You can go here for more info https://devcenter.heroku.com/articles/rails4

answered Jul 20 '13 at 00:41

JanuskaE

1,284
2
8
12

2

Good info for those that are upgrading from Rails 3, etc., but the problem in the question occurred in a new application. Also, this won't help you if you have those directories gitignored, because they still won't get git pushed to Heroku. – Justin Garrick Aug 21 '13 at 19:41
2

Moving to Rails 4.0.0, this was definitely the problem. – John Siladie Sep 28 '13 at 00:46
Issuing this command helped me getting my heroku app running again. Thanks a lot. – Francisco Quintero Dec 13 '14 at 06:40
`rake app:update:bin` for Rails 6+ as of this writing – Victor S Dec 05 '21 at 00:03

score 40 · Accepted Answer · answered Jul 11 '13 at 01:04

40

After struggling with this for a bit, I noticed that my Rails 4 project had a /bin directory, unlike some older Rails 3 projects I had cloned. /bin contains 3 files, bundle, rails, and rake, but these weren't making it to Heroku because I had bin in my global .gitignore file.

This is a pretty common ignore rule if you work with Git and other languages (Java, etc.), so to fix this:

Remove bin from ~/.gitignore
Run bundle install
Commit your changes with git add . and git commit -m "Add bin back"
Push your changes to Heroku with git push heroku master

answered Jul 11 '13 at 01:04

Justin Garrick

14,767
7
41
66

3

There is a Heroku guide on running Rails4 applications on Heroku - https://devcenter.heroku.com/articles/rails4 – John Beynon Jul 11 '13 at 07:23
1

Yep, it mentions not having bin in your .gitignore, but the tutorial doesn't. Just thought I would create this in case someone else has a similar problem. – Justin Garrick Jul 11 '13 at 12:45
@justingarrick do you really need to run `bundle install`? Seems like an extra step. – Josh Nov 18 '13 at 02:42
Make sure it's not in your global gitignore. That's what bit me. – courtsimas Jun 17 '14 at 20:20
I had the same problem for Dokku: 502 bad gateway. Thanks for the help. – Hugo Logmans Aug 15 '14 at 12:28
although i removed /bin dir from .gitignore file, it doesn't get pushed to git repo, whats the issue. – codemilan Jun 14 '16 at 10:46

score 9 · Answer 3 · edited Feb 06 '16 at 09:38

9

Steps :

bundle config --delete bin # Turn off Bundler's stub generator

rake rails:update:bin # Use the new Rails 4 executables

git add bin or git add bin -f # Add bin/ to source control

git commit -a -m "you commit message"

git push heroku master

heroku open

edited Feb 06 '16 at 09:38

Igor Ivancha

3,413
4
30
39

answered Mar 16 '15 at 19:19

Kirit Vaghela

12,572
4
76
80

Ryan Taylor · Answer 4 · 2014-11-12T04:58:05.267

3

I had this issue because the permissions on my ~/bin directory were 644 instead of 755. Running rake rails:update:bin locally (on Mac/*nix) and then pushing the changes fixed the problem.

edited Nov 12 '14 at 04:58

answered Apr 16 '14 at 05:16

Ryan Taylor

12,559
2
39
34

score 1 · Answer 5 · answered Jan 31 '15 at 09:42

I had the very same problem that you did. The issue lied in the fact that the bin folder was never pushed to the heroku repository.

I looked, I looked, and then I looked again, there was no rule in the .gitignore file for the bin/ folder...

Then, after a lot of pain and anguish, I realized that a couple of months before I had created a global .gitignore that would ignore all bin folders of all my repositories (why lord, why??).

I deleted the global .gitignore, and everything worked fine.

score 0 · Answer 6 · answered Aug 19 '13 at 15:48

We didn't have a myapp/bin directory in our rails 4 app, so we created one and then copied in the my app/script/rails file, plus the bundle and rake files from under rvm/ruby/bin and then added these to the repo for git and pushed it up to heroku and all was well.

score 0 · Answer 7 · answered Dec 15 '21 at 05:54

0

On rails 5.2.6, rake app:update:bin worked for me. Now deployment to heroku is working.

answered Dec 15 '21 at 05:54

tomb

1,374
1
13
23

score -1 · Answer 8 · answered Jan 28 '15 at 12:24

I can confirm running rake rails:update:bin works, as said by @Ryan Taylor.

I think I had this problem because I originally created this Rails app on Windows. Running the command above on Linux solved for me.

Also, on changing from Windows to Linux for development, it is a good idea to delete Gemfile.lock file and run bundle install to generate it again without Windows specific gems listed there.

"bin/rails: No such file or directory" w/ Ruby 2 & Rails 4 on Heroku

8 Answers8

Linked

Related