bin/rails:6: warning: already initialized constant APP_PATH

[sadiqmmm]

I am using RVM. After installing Rails 4.1.0.RC1 and generating new app and running the rails server . Just after pressing the ctrl+ c to close it show the warning -> bin/rails:6: warning: already initialized constant APP_PATH

[superbilk]

+1, same here with thin

christian@~/projects/happinessmetric: rails s
=> Booting Thin
=> Rails 4.1.0.rc1 application starting in development on http://0.0.0.0:3000
=> Run `rails server -h` for more startup options
=> Notice: server is listening on all interfaces (0.0.0.0). Consider using 127.0.0.1 (--binding option)
=> Ctrl-C to shutdown server
Thin web server (v1.6.1 codename Death Proof)
Maximum connections set to 1024
Listening on 0.0.0.0:3000, CTRL+C to stop
^CStopping ...
Exiting
bin/rails:6: warning: already initialized constant APP_PATH
/Users/christian/projects/happinessmetric/bin/rails:6: warning: previous definition of APP_PATH was here

[sadiqmmm]

Uninstalling and Re-install RVM helped. Now i am not get this warning.
Use rvm implode to uninstall RVM.

[robin850]

I do not use RVM and I can see the same warning ; this is pretty strange.

[sadiqmmm]

okay, Try to uninstall your ruby and gems . And then restart your computer ,if possible . Again install back ruby and gems and try.

[robin850]

@sadiqmmm : Actually it's spring which cause this issue. Try to comment it in the Gemfile, then bundle install and restart the server ; shutting it down, the warning is not present anymore.

[robin850]

Let's continue the disccusion in rails/spring#259. Thank you for reporting!

[sadiqmmm]

Thanks +1

[cisolarix]

rake rails:update:bin to the rescue, don't know why.

[drakmail]

I'm have this issue when change database adapter in config/database.yml from sqlite3 to postgresql and forgot to add gem 'pg' to my Gemfile. After adding gem 'pg' to Gemfile issue was fixed.

[zackkitzmiller]

An invalid DATABASE_URL env var can also cause this.

[arcreative]

Both @cisolarix and @zackkitzmiller suggestions worked to varying degrees, thanks guys!

[tian-xiaobo]

remove this fix it

begin
load File.expand_path("../spring", FILE)
rescue LoadError
end

[wellington1993]

@cisolarix , I am run rake rails:update:bin with --traceand identify 2 problematic gems on my Gemfile: this gems: data_miner and sniff. After comment this gems rails s works. Works for me. Thanks.

[SurajShukla]

I tried by commenting spring gem and updating the bundle, that didn't work..
tried rake rails:update:bin, that didn't work either..

I had require 'iconv' in my application.rb and I removed that from the gem and the server started for me..

Not sure how..

[rlemaster]

I got this error message after upgrading postgres using brew but not uninstalling and reinstalling the pg gem. This error went away once pg gem was reinstalled.

[joshmn]

This can be due to an invalid Gemfile.lock -- I've seen it multiple times because people put, say, gem 'dotenv-rails' as the very first gem in their Gemfile (before the rails gem itself, even).

rm Gemfile.lock && bundle

[seangaffney]

I got this error after removing the brew version of openssl. In my case it was because mysql (also brew installed) was referencing the brew-installed version of openssl. Re-installing mysql via brew resolved the issue.

[b-mandelbrot]

I got this error when I removed ominiauth gem that was application dependency. I added the gem back to the Gemfile and it worked fine!

[djones]

rake rails:update:bin fixed this for me.

[beck]

rake rails:update:bin 👍

This was removed from the top of the bin:

begin
  load File.expand_path("../spring", __FILE__)
rescue LoadError
end

[Fedcomp]

This is how i fixed it: use rake -D to figure out what stops rails server from starting. In my case it was missing gem, so i installed it back and it works again.
I really doubt, but in case someone don't know what is spring, it is gem which speedup rails bootup, especially useful in developing rake tasks or running tests.

[cmavromoustakos]

This fixed it for me as well

[ constantine ~/Sandbox/mavromoustakos ] ✔ rake rails:update:bin                                                                                        
       exist  bin
   identical  bin/bundle
    conflict  bin/rails
    Overwrite /Users/constantine/Sandbox/mavromoustakos/bin/rails? (enter "h" for help) [Ynaqdh] Y
       force  bin/rails
    conflict  bin/rake
    Overwrite /Users/constantine/Sandbox/mavromoustakos/bin/rake? (enter "h" for help) [Ynaqdh] Y
       force  bin/rake
   identical  bin/setup

[Fedcomp]

@cmavromoustakos this way you just remove rails spring and slowdown rails loading a lot.

[sadaf2605]

rake rails:update:bin fixed for me too.

[tyronewilson]

rake rails:update:bin works but at the expense of killing spring. So that isn't a solution if you would like to still keep spring working.

In my case I had forgotten to install sinatra

gem 'sinatra'
bundle install

it worked 100% with spring and everything as before.

[gwzz]

I got this problem after I updated to EI Capitan. With:

rake rails:update:bin --trace

I find the problem is caused by bash libmysqlclient.18.dylib
In El Capitan /usr/lib/ now has a restricted flag and can't be written to without disabling security so I just put the link in /usr/local/lib instead,as follows:

sudo ln -s /usr/local/mysql/lib/libmysqlclient.18.dylib /usr/local/lib/libmysqlclient.18.dylib

Hope this can help anyone who is struggling to the problem.

[kalashnikovisme]

Fixed.

Remove gem spring
Add gem rest-client

[tyronewilson]

@kalashnikovisme those things are so unrelated. What was the underlying issue there? did you try keeping spring but adding rest-client and running bundle install && spring stop and restart your app?

Disabling spring seems to be the wrong approach to me, there is usually another issue at play

[kalashnikovisme]

@tyronewilson problem was in the gem, that uses gem rest-client but doesn't have it in dependency.

And you're right. spring stop solved problem.

[tyronewilson]

@kalashnikovisme Great! :)

[zulhfreelancer]

After running sudo ln -s /usr/local/mysql/lib/libmysqlclient.18.dylib /usr/lib/libmysqlclient.18.dylib

I get this error:
ln: /usr/lib/libmysqlclient.18.dylib: Operation not permitted

Then, I run:
brew install mysql it works for me.

[marcellosachs]

rake rails:update:bin worked for me as well! thanks!

[b3ccio]

+1 for rake rails:update:bin

[tyronewilson]

Dunno why everyone is so ready to kill spring with this sledgehammer
solution.
On 12 Feb 2016 2:49 AM, "Paul Beccio" notifications@github.com wrote:

+1 for rake rails:update:bin

—
Reply to this email directly or view it on GitHub
#14115 (comment).

[sibevin]

I have the same issue after I update OSX and brew. Here are steps I solve the problem:

• I try to reinstall ruby with RVM but not working.
• Run rake rails:update:bin and an error occurs.

$ rake rails:update:bin
rake aborted!
LoadError: dlopen(/Users/carlos/.rvm/gems/ruby-2.2.3/extensions/x86_64-darwin-14/2.2.0-static/mysql2-0.3.20/mysql2/mysql2.bundle, 9): Library not loaded: /usr/local/lib/libmysqlclient.18.dylib
  Referenced from: /Users/carlos/.rvm/gems/ruby-2.2.3/extensions/x86_64-darwin-14/2.2.0-static/mysql2-0.3.20/mysql2/mysql2.bundle
  Reason: image not found - /Users/carlos/.rvm/gems/ruby-2.2.3/extensions/x86_64-darwin-14/2.2.0-static/mysql2-0.3.20/mysql2/mysql2.bundle
/Users/carlos/.rvm/gems/ruby-2.2.3/gems/mysql2-0.3.20/lib/mysql2.rb:31:in `require'
...

• It seems that the msyql2 gem is broken, so I reinstall the mysql2 gem (gem uninstall mysql2; bundle install).
• And it works now.

[wellington1993]

Hi, I removed require 'bootsnap/setup' from boot.rb and worked for me.

[KiranJosh]

rake rails:update:bin to the rescue, don't know why.

Worked for me perfectly

[felipecsl]

With rails 6, bin/rake app:update:bin did the trick

[chunlea]

With Rails 6, bin/spring binstub --all works for me.