Unable to restart ManageIQ using the rake script - load constant error


#1

Hello:

I am a newbie to ManageIQ and am trying to prepare for a demo. For some reason I am not able to get the service to re-start. When I look at the evm.log, I see an error and am wondering if that is causing the service to fail. The full stack trace is presented below. When I say that the service is not coming up, then I mean that when I check for curl http://localhost:3000, the service does not respond. Thanks in advance for your help!

/home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/activesupport/lib/active_support/dependencies.rb:503:in load_missing_constant': Expected /home/miqbuilder/manageiq/vmdb/app/models/report_content.rb to define ReportContent (LoadError) from /home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/activesupport/lib/active_support/dependencies.rb:192:inblock in const_missing’
from /home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/activesupport/lib/active_support/dependencies.rb:190:in each' from /home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/activesupport/lib/active_support/dependencies.rb:190:inconst_missing’
from /home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/activesupport/lib/active_support/inflector/methods.rb:230:in block in constantize' from /home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/activesupport/lib/active_support/inflector/methods.rb:229:ineach’
from /home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/activesupport/lib/active_support/inflector/methods.rb:229:in constantize' from /home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/activesupport/lib/active_support/core_ext/string/inflections.rb:54:inconstantize’
from /home/miqbuilder/manageiq/vmdb/lib/evm_database.rb:43:in block in seed' from /home/miqbuilder/manageiq/vmdb/lib/evm_database.rb:41:ineach’
from /home/miqbuilder/manageiq/vmdb/lib/evm_database.rb:41:in seed' from /home/miqbuilder/manageiq/vmdb/lib/evm_database.rb:31:inseed_last’
from /home/miqbuilder/manageiq/vmdb/app/models/miq_server.rb:272:in start' from /home/miqbuilder/manageiq/vmdb/lib/workers/evm_server.rb:71:instart’
from /home/miqbuilder/manageiq/vmdb/lib/workers/evm_server.rb:85:in start' from /home/miqbuilder/manageiq/vmdb/lib/workers/evm_server.rb:89:in<top (required)>'
from /home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/railties/lib/rails/commands/runner.rb:52:in eval' from /home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/railties/lib/rails/commands/runner.rb:52:in<top (required)>'
from /home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/railties/lib/rails/commands.rb:64:in require' from /home/miqbuilder/.rvm/gems/ruby-1.9.3-p547/bundler/gems/rails-8cf411ee95e7/railties/lib/rails/commands.rb:64:in<top (required)>'
from script/rails:6:in require' from script/rails:6:in


#2

I am not 100% sure where the report_content.rb file showed up from but when I deleted it, the EVM re-started.