Error Calling Dispatcher.dispatch # Nomethoderror
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Weird problem with Rails app and Mongrel up vote 13 down vote favorite I originally posted a question relating to this problem on serverfault.com: http://serverfault.com/questions/152587/apache-mod-proxy-to-another-server I have since realized that this is not an issue with my server setup, but my rails application. I have set this application up server-wise the exact same as another functioning rails app I have running on the same server. When I start the server my mongrel.log looks like this: ** Daemonized, any open files are closed. Look at /var/www/osuwebdev/tmp/pids/mongrel.pid and log/mongrel.log for info. ** Starting Mongrel listening at 0.0.0.0:8080 ** Starting Rails with production environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload (without restart). It might not work well. ** Mongrel 1.1.5 available at 0.0.0.0:8080 ** Writing PID file to /var/www/osuwebdev/tmp/pids/mongrel.pid When I load a page this pops up in the log: Wed Jun 30 19:46:10 +0000 2010: Error calling Dispatcher.dispatch #
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about http://stackoverflow.com/questions/3152909/weird-problem-with-rails-app-and-mongrel hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join http://stackoverflow.com/questions/3903717/error-calling-dispatcher-dispatch-nameerror-uninitialized-constant-actioncont them; it only takes a minute: Sign up Error calling Dispatcher.dispatch #
hopefully this will help you save a little time. The environment prior to upgrade: rails 2.3.2 ruby 1.8.6 rack 1.1.5 rubygems 1.3.1 http://www.andrewhavens.com/posts/23/how-to-upgrade-a-rails-2.3.2-app-to-rails-2.3.15/ mongrel 1.1.5 nginx I hade one console tab open tailing the mongrel log at all times so I could see when something broke. Having not worked with a mongrel rails app, I didn't https://saz.sh/2011/06/10/mongrel-error-calling-dispatcherdispatch/ know where I would find the log, but it was in the app's log directory (of course). The first step was to install the Rails gem: sudo gem install rails -v 2.3.15 error calling If you see these messages, just ignore them because they don't cause an error: config.load_paths is deprecated and removed in Rails 3, please use autoload_paths instead Next, update rails version in config/environment.rb: RAILS_GEM_VERSION = '2.3.15' unless defined? RAILS_GEM_VERSION Vendored Gems If your app has a vendored version of rails, remove it because we're going to use the one we just error calling dispatcher.dispatch installed: rm -rf vendor/rails If you have any files (non-directories) in vendor/gems, remove those too: rm vendor/gems/init.rb If you have any errors in the log about your vendored gems missing .specification files, make sure the gem is installed with ruby gems first, then use the rake task to create the specs: rake gems:refresh_specs Rake If you have any rake errors, you will see the message of what you need to fix. RubyGems You might have seen this error before upgrading Rails: Warning: Gem::Dependency#version_requirements is deprecated and will be removed on or after August 2010. Use #requirement And if you see this error after upgrading Rails... /usr/lib/ruby/gems/1.8/gems/rails-2.3.15/lib/rails/gem_dependency.rb:81:in `add_load_paths': undefined method `requirement' for # 05:21:20 +0000 2011: Error calling Dispatcher.dispatch #