rails server bin / rails : 6 : 경고 : 이미 초기화 된 상수 APP_PATH 오류

rails server bin / rails : 6 : 경고 : 이미 초기화 된 상수 APP_PATH 오류

---

레일과 보석을 제거 / 재설치하는 것과 같은 여러 가지를 시도했지만 아무 소용이 없습니다.

새 프로젝트로 이동하여 rails s 또는 bundle exec rails 서버를 실행하면이 오류가 발생합니다.

bin/rails:6: warning: already initialized constant APP_PATH
/Users/toabui/Sites/cms/bin/rails:6: warning: previous definition of APP_PATH was here Usage: rails COMMAND [ARGS]

내 빈 / 레일 안에 다음 코드가 있습니다.

#!/usr/bin/env ruby
begin
load File.expand_path("../spring", __FILE__)
rescue LoadError
end
APP_PATH = File.expand_path('../../config/application',  __FILE__)
require_relative '../config/boot'
require 'rails/commands'

누구든지 내가 rails s를 실행할 때 왜 계속 그 오류가 발생하는지 알고 있습니까?

나는 봤는데 봄 보석에 오류가있는 것 같지만 작동하지 않는 것 같습니다.

---

내 디렉토리에서 an_initilizer.rb를 찾을 수 없었고 spring gem을 제거 / 설치하려고 시도했지만 작동하지 않았습니다.

그러나 나는 마침내 그것을 작동시킬 수 있었다.

분명히 스프링 및 레일 4+와 약간의 충돌이 있습니다.

다음을 실행해야했습니다.

rake rails:update:bin 

하지만 다른 오류가 발생했습니다.

Library not loaded: libmysqlclient.18.dylib

다른 stackoverflow 게시물에서 찾은 다음 명령을 실행했습니다.

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

그런 다음 원래 명령을 실행했습니다.

 rake rails:update:bin 

그런 다음 서버 명령을 실행하십시오.

 rails s

이제 내 WebBrick 서버가 실행 중입니다.

---

rake rails:update:bin 구조에.

---

El Capitan (OS X 10.11)을 사용중인 경우 SIP (Security Integrity Protection)는 mysql을 수정하기 위해 / usr / lib에 연결하는 것을 방지합니다. 대신 / usr / local / lib에 링크하십시오.

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

---

이것은 나를위한 일입니다.

gem uninstall mysql2

bundle install 또는 gem install mysql2

---

같은 오류가 발생했습니다. Gemfile에서 스프링을 제거하고 다시 번들로 제공합니다. 그래도 실제로 해결책은 아닙니다.

이 오류를 생성 한 코드를 config/initializers/an_initializer.rb

require "lib/a_file_i_need"

나는 그것을 변경했다

require "#{ Rails.root }/lib/a_file_i_need"

---

Rails 4와 imagemagick 및 rmagick을 업데이트하려고하면이 오류가 발생했습니다. 그래서 방금 달렸어요

보석 제거 rmagick

모든 버전 옵션을 선택합니다. 그런 다음 다시 시도하십시오

편집 : 이것은 필요한 기본 gem을 설치하지 않고 gem을 사용하려고했기 때문에 방금 저와 함께 다시 발생했습니다. 제 경우 해결책은 'omniauth-google-oauth2'를 사용하기 전에 'omniauth-google'을 설치하는 것이었지만 설치하지 않았기 때문에 동일한 오류가 다시 발생했습니다.

---

postgresql을 업그레이드 한 후이 오류가 발생했습니다.

$ gem uninstall pg
$ gem install pg

나를 위해이 문제를 해결했습니다.

---

이것은 brew upgrade. 내 생각에 이것은 오류 메시지가 나타나지 않았지만 기본 확장으로 일부 보석을 깨뜨렸다는 것입니다.

내가 한 일은 설치된 gem을 완전히 제거하는 것입니다 (제 경우에는를 사용하여 루비 버전을 완전히 제거하고 다시 설치했습니다 rbenv).
실행 bundle install하면 기본 확장이 다시 컴파일되고 모든 것이 다시 실행되었습니다.

---

I got the same error. I had ruby 2.1.3 and rails 4.1.6 running on Mavericks and then I migrated to Yosemite and installed the 4.2.0 rails version an ruby 2.1.5 and my apps I made in the previous version didn't work with the new one, so I made some gem sets with RVM and installed the 2.1.3 version. Now when I wanted to run the server I got these error:

bin/rails:6: warning: already initialized constant APP_PATH
/Users/Lexynux/_WebProjects/RoR_Apps/SAIIP2/bin/rails:6: warning: previous definition of APP_PATH was here
Usage: rails COMMAND [ARGS]

And as tobu mentioned I ran:

rake rails:update:bin

I got this:

LoadError: dlopen(/Users/Lexynux/.rvm/gems/ruby-2.1.3@SAIIP2/extensions/x86_64-darwin-14/2.1.0-static/mysql2-0.3.16/mysql2/mysql2.bundle, 9): Library not loaded: libmysqlclient.18.dylib

Then I ran this:

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

And finally I repeated the first command it the terminal asked me for this:

Overwrite /Users/Lexynux/_WebProjects/RoR_Apps/SAIIP2/bin/rails? (enter "h" for help) [Ynaqdh]

I just typed 'Y' and hit return.

After all this I started working and going well.

Thanks.

---

I got the same error, it happend to be related to gem dotenv. Instructions were to add the following to Gemfile:

gem 'dotenv', :require => 'dotenv/rails-now'

But as it turned out, dotenv/rails-now caused the error. If you use dotenv don't require rails-now

---

Are you using pg and mysql in different branches ? If yes, please confirm db config file.

---

I'll post what worked for me.

Comment out

gem 'spring'

Add gem 'net-shh'

and run bundle install

And restart your sever

---

I received this error after upgrading rails. Disabling spring give me a hint that the issue was with:

gem 'google-api-client', require: 'google/api_client'

Changed to:

gem 'google-api-client', '0.9'

Resolved the issue.

---

I had the same error message output when trying to start an application within a Vagrant environment. It cropped up out of nowhere after zero changes to the application code (and other weird behaviour followed, such as development.rb being deleted upon attempting to run the app).

In the end I simply halted the VM & restarted it, everything was then fine so I'm assuming it was an issue with file syncing / shared folders perhaps? (default Vagrant shared folder being used).

---

Run these in console:

rake tmp:clear
rake secret

---

IF rake rails:update:bin gives additional errors:

I had recently been doing some server maintenance and had subsequently updated OpenSSL.

When I tried running the rake rails:update:bin command, I was presented with an error relating to openSSL.

Having rebuilt my version of Ruby (`rvm reinstall ruby-x.x.x' with RVM), both errors went away.

This is always worth a try I guess.

---

My problem was I was using an outdated version of ruby 1.9.3 with rails 4.2. I upgraded to 2.1.2 , removed the broken project, ran rails new blog to recreate my project, navigated into my newly created app and ran rails server and it worked.

---

I just had this problem and found that it was being caused by the fact that I had removed a gem from the gemfile without deleting the other require references. In my case, I just had to remove it from config/application.rb.

---

Had this error recently, it is caused by spring, because of its suggested code in executables:

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

It originally expects a LoadError for spring itself in production, but by this code all other load error will be ignored too.

Thus if you have any other LoadError in rails loading process (for example in routes/init) spring worker startup fails and then there goes branch that tries to load everything again like there was no spring.

---

For me this issue presented as a result of bundle upgrading rvm-capistrano amongst other things.
Adding this require:false fixed things in the end as per this previous post

gem  'rvm-capistrano',  require: false

Although could possibly be an additional issue - as running rake rails:update:bin may have helped clear the initial issue.

참고URL : https://stackoverflow.com/questions/23402820/rails-server-bin-rails6-warning-already-initialized-constant-app-path-error