2012-02-17 41 views
5

Estoy utilizando Rails 3.2.1 y la línea 'ruby-debug19' ha sido comentada en el Gemfile. Cuando inicio el servidor en modo de desarrollo, el servidor se inicia sin ningún problema. Sin embargo, cuando se inicia mi servidor en modo de producción (carriles servidor de producción -e, que endup consiguiendo el error siguiente (véase seguimiento de la pila siguiente):En el modo de producción obtengo - No hay tal archivo para cargar - ruby-debug (LoadError)

... `rescue in depend_on': No such file to load -- ruby-debug (LoadError) 

he pasado muy poco tiempo tratando de averiguar quién es requiriendo re-depuración sin suerte. No estoy seguro de qué incluir, excepto mi Gemfile y la pila. Realmente agradecería cualquier ayuda.

Una pieza más de información: la línea 5 en mi archivo environment.rb solo está llamando "Aplicación .initialize "

Gemfile:

gem 'rails', '3.2.1' 
gem 'mysql' 
gem 'gravatar_image_tag', '0.1.0' 
gem "devise", ">= 1.4.9" 
gem "paperclip", "~> 2.0" 
gem 'jquery-rails' 
gem 'aws-sdk' 
gem 'aws-s3', :require => 'aws/s3' 
gem 'formtastic' 
gem 'cancan'  
gem 'kaminari' 
gem 'date_validator' 
gem 'simple_form' 
gem 'heroku' 

gem 'pg', :group => :production 

# Gems used only for assets and not required 
# in production environments by default. 
group :assets do 
    gem 'sass-rails', " ~> 3.2.3" 
    gem 'coffee-rails', "~> 3.2.1" 
    gem 'uglifier', '>= 1.0.3' 
end 

gem 'annotate','2.4.1.beta1', :group => :development 
gem 'nifty-generators',  :group => :development 

gem 'rspec-rails', '2.6.1.beta1', :group => [:development, :test] 
gem 'faker', '0.3.1',    :group => [:development, :test] 
gem 'rspec', '2.6',    :group => [:test, :development] 
gem 'populator',     :group => [:development, :test] 

#gem 'ruby-debug19', :require => 'ruby-debug', :group => [:development, :test] 

gem "factory_girl_rails", ">= 1.1.0", :group => :test 
gem "cucumber-rails", ">= 1.0.2",  :group => :test 
gem "pickle", ">=0.4.10",    :group => :test 
gem "capybara", ">= 1.0.1",   :group => :test 
gem "database_cleaner", ">= 0.6.7", :group => :test 
gem "launchy", ">= 2.0.5",   :group => :test 
gem "email_spec",      :group => :test 
gem 'guard-rspec',     :group => :test 
gem "mocha",       :group => :test 

Y aquí es el seguimiento de la pila:

➜ taskfree git:(master) ✗ bundle exec rails server -e production 
=> Booting WEBrick 
=> Rails 3.2.1 application starting in production on http://0.0.0.0:3000 
=> Call with -d to detach 
=> Ctrl-C to shutdown server 
Exiting 
/usr/local/rvm/gems/ruby-1.9.2-p290/gems/activesupport- 3.2.1/lib/active_support/dependencies.rb:317:in `rescue in depend_on': No such file to load -- ruby-debug (LoadError) 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/activesupport3.2.1/lib/active_support/dependencies.rb:312:in `depend_on' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.1/lib/active_support/dependencies.rb:225:in `require_dependency' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/engine.rb:439:in `block (2 levels) in eager_load!' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/engine.rb:438:in `each' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/engine.rb:438:in `block in eager_load!' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/engine.rb:436:in `each' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/engine.rb:436:in `eager_load!' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/application/finisher.rb:53:in `block in <module:Finisher>' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/initializable.rb:30:in `instance_exec' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/initializable.rb:30:in `run' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/initializable.rb:55:in `block in run_initializers' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/initializable.rb:54:in `each' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/initializable.rb:54:in `run_initializers' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/application.rb:136:in `initialize!' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/railtie/configurable.rb:30:in `method_missing' 
from /Users/bidhan/code/taskfree/config/environment.rb:5:in `<top (required)>' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.1/lib/active_support/dependencies.rb:251:in `require' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.1/lib/active_support/dependencies.rb:251:in `block in require' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.1/lib/active_support/dependencies.rb:236:in `load_dependency' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.1/lib/active_support/dependencies.rb:251:in `require' 
from /Users/bidhan/code/taskfree/config.ru:4:in `block in <main>' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rack-1.4.1/lib/rack/builder.rb:51:in `instance_eval' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rack-1.4.1/lib/rack/builder.rb:51:in `initialize' 
from /Users/bidhan/code/taskfree/config.ru:1:in `new' 
from /Users/bidhan/code/taskfree/config.ru:1:in `<main>' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rack-1.4.1/lib/rack/builder.rb:40:in `eval' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rack-1.4.1/lib/rack/builder.rb:40:in `parse_file' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rack-1.4.1/lib/rack/server.rb:200:in `app' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/commands/server.rb:46:in `app' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rack-1.4.1/lib/rack/server.rb:301:in `wrapped_app' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rack-1.4.1/lib/rack/server.rb:252:in `start' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/commands/server.rb:70:in `start' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/commands.rb:55:in `block in <top (required)>' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/commands.rb:50:in `tap' 
from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.1/lib/rails/commands.rb:50:in `<top (required)>' 
from script/rails:6:in `require' 
from script/rails:6:in `<main>' 

Y aquí es la salida cuando acabo de empezar mi servidor en el modo de desarrollo:

➜ taskfree git:(master) ✗ bundle exec rails server    
=> Booting WEBrick 
=> Rails 3.2.1 application starting in development on http://0.0.0.0:3000 
=> Call with -d to detach 
=> Ctrl-C to shutdown server 
[2012-02-17 15:09:24] INFO WEBrick 1.3.1 
[2012-02-17 15:09:24] INFO ruby 1.9.2 (2011-07-09) [x86_64-darwin10.5.0] 
[2012-02-17 15:09:24] INFO WEBrick::HTTPServer#start: pid=33798 port=3000 

Respuesta

3

Su Gemfile.lock puede ayudar a rastrear el cual gem tiene ruby-debug como una dependencia. Ábrelo y busca 'ruby-debug' y debe estar anidado debajo de la gema que depende de él.

Dicho esto, me doy cuenta de un problema que puede causarle un poco de dolor. La gema aws-s3 y las gemas aws-sdk no son compatibles. Ambos usan la constante AWS :: S3, uno como módulo y el otro como clase. Obtienes diferentes comportamientos dependiendo del orden en que se requieren.

Paperclip reemplazó recientemente aws-s3 como una dependencia con aws-sdk. Debería poder eliminar simplemente aws-s3 de su Gemfile (a menos que use específicamente aws-s3 fuera del clip). Si depende de aws-s3 fuera del clip, querrá reemplazar esas llamadas con llamadas equivalentes usando aws-sdk.

+0

Comprobé Gemfile.lock - no hay referencia a ruby-debug. Gracias por el asesoramiento sobre aws-s3. Aprecio tu ayuda. –

+2

Solo tener una línea como ** requiere 'ruby-debug' ** que se ejecuta durante la inicialización causará este problema. Como no hay referencia a ruby-debug en mi código, empiezo a pensar que una de las gemas que estoy usando es probablemente la culpable. Ahora la pregunta es cómo lo averiguo fácilmente. Esta es solo una corazonada de que podría estar completamente fuera de aquí también. –

+0

impresionante Bidhan, mi problema fue similar, me ayudó después de un esfuerzo incansable de buscarlo por la mitad del día. – TheMouseMan

Cuestiones relacionadas