500 error running with Passenger at Dreamhost
Added by Jacob Berggren almost 16 years ago
I'm getting the following error message in the Apache logs, is there anyone that could help me out?
/usr/lib/ruby/gems/1.8/gems/activesupport-2.1.2/lib/active_support/inflec
tor.rb:190: [BUG] Segmentation fault
ruby 1.8.7 (2008-08-11 patchlevel 72) [x86_64-linux]
- Exception NoMethodError in Passenger::Railz::FrameworkSpawner
(undefined method `child_exception' for
#<Passenger::Railz::ApplicationSpawner::Error:0x2b4108ce0300>) (process
22325):
from
/dh/passenger/lib/passenger/railz/framework_spawner.rb:274:in
`handle_spawn_application'
from
/dh/passenger/lib/passenger/railz/framework_spawner.rb:263:in
`synchronize'
from
/dh/passenger/lib/passenger/railz/framework_spawner.rb:263:in
`handle_spawn_application'
from /dh/passenger/lib/passenger/abstract_server.rb:317:in
`__send__'
from /dh/passenger/lib/passenger/abstract_server.rb:317:in
`main_loop'
from /dh/passenger/lib/passenger/abstract_server.rb:168:in
`start_synchronously'
from /dh/passenger/lib/passenger/abstract_server.rb:135:in
`start'
from /dh/passenger/lib/passenger/abstract_server.rb:112:in `fork'
from /dh/passenger/lib/passenger/abstract_server.rb:112:in
`start'
from /dh/passenger/lib/passenger/railz/framework_spawner.rb:87:in
`start'
from /dh/passenger/lib/passenger/spawn_manager.rb:218:in
`spawn_rails_application'
from /dh/passenger/lib/passenger/spawn_manager.rb:213:in
`synchronize'
from /dh/passenger/lib/passenger/spawn_manager.rb:213:in
`spawn_rails_application'
from /dh/passenger/lib/passenger/spawn_manager.rb:122:in
`spawn_application'
from /dh/passenger/lib/passenger/spawn_manager.rb:247:in
`handle_spawn_application'
from /dh/passenger/lib/passenger/abstract_server.rb:317:in
`__send__'
from /dh/passenger/lib/passenger/abstract_server.rb:317:in
`main_loop'
from /dh/passenger/lib/passenger/abstract_server.rb:168:in
`start_synchronously'
from /dh/passenger/bin/passenger-spawn-server:46
Replies (9)
RE: 500 error running with Passenger at Dreamhost - Added by Jean-Baptiste Barth almost 16 years ago
I don't see any redmine related line in this stack trace, it's difficult to help you find how it happenned.
Can you run a "ruby script/about" ? It could be interesting to have your version infos... And what is the version/configuration of Passenger ?
RE: 500 error running with Passenger at Dreamhost - Added by Jacob Berggren almost 16 years ago
Thank you for the reply!
How can I access the Passenger configuration? I'm assuming Dreamhost is the only ones able to access that.
About your application's environment
Ruby version 1.8.7 (x86_64-linux)
RubyGems version 1.3.1
Rails version 2.1.1
Active Record version 2.1.1
Action Pack version 2.1.1
Active Resource version 2.1.1
Action Mailer version 2.1.1
Active Support version 2.1.1
Application root /home/nordicfx/redmine.nordicfx.com
Environment development
Database adapter mysql
rails (2.2.2, 2.1.2, 2.1.1, 2.1.0, 2.0.5, 2.0.2)
rake (0.8.3, 0.8.2)
ruby-breakpoint (0.5.1)
ruby-debug (0.10.0)
ruby-yadis (0.3.4)
ruby_odeum (0.4.1)
rubyforge (0.4.5)
RubyInline (3.6.7)
rubypants (0.2.0)
rubyzip (0.9.1)
RE: 500 error running with Passenger at Dreamhost - Added by Jacob Berggren almost 16 years ago
I have also tried setting it to version 2.1.2.
I just noticed it says 'Environment: development', I set the database info in database.yml under production. Is there a way to switch it over to production? I tried un-commenting ENV['RAILS_ENV'] ||= 'production'.
About your application's environment
Ruby version 1.8.7 (x86_64-linux)
RubyGems version 1.3.1
Rails version 2.1.2
Active Record version 2.1.2
Action Pack version 2.1.2
Active Resource version 2.1.2
Action Mailer version 2.1.2
Active Support version 2.1.2
Application root /home/nordicfx/redmine.nordicfx.com
Environment development
Database adapter mysql
RE: 500 error running with Passenger at Dreamhost - Added by Jacob Berggren almost 16 years ago
Ok, some updates...
If I run dispatch.fcgi in a terminal it runs fine, outputs the html code and logs this:
Processing WelcomeController#index (for at 2009-03-03 17:50:33) [GET]
Session ID: 8820ef21222d5e09c2f296511875aa3f
Parameters: {"action"=>"index", "controller"=>"welcome"}
Rendering template within layouts/base
Rendering welcome/index
Completed in 0.15917 (6 reqs/sec) | Rendering: 0.01300 (8%) | DB: 0.02726 (17%) | 200 OK [http://:]
But when browsing the website gives me a 500 error in the Apache log.
I tried the webrick server and that works with a browser... but we aren't allowed to run that at Dreamhost.
So, I'm assuming there is a linking issue between the web access and the dispatch.fcgi
Anyone who has some enlightenment on this?
RE: 500 error running with Passenger at Dreamhost - Added by Jean-Baptiste Barth almost 16 years ago
Which version of Redmine are you using ? 0.8.1 stable ?
You should also check redmine logs : if you have a 500 error maybe there will be more explicit messages in those files.
RE: 500 error running with Passenger at Dreamhost - Added by Jacob Berggren almost 16 years ago
I downloaded the version that is up on the download page, it says 0.8.1... but the SVN url is 0.8-stable.
Normally when browsing to the site, Redmine doesn't write anything to the logs except # Logfile created on Tue Mar 03 22:27:16 -0800 2009.
But I did notice this in the log this time:
Processing ApplicationController#index (for 90.2.189.232 at 2009-03-03 22:34:24) [GET]
Session ID: be87403d32de89149e004d3477623d0e
Parameters: {}
ActionController::RoutingError (No route matches "/favicon.ico" with {:method=>:get}):
/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/routing/recognition_optimisation.rb:67:in `recognize_path'
/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/routing/route_set.rb:385:in `recognize'
/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:148:in `handle_request'
/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:107:in `dispatch'
/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:in `dispatch'
/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:120:in `dispatch_cgi'
/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:35:in `dispatch'
/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:103:in `process_request'
/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:153:in `with_signal_handler'
/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:101:in `process_request'
/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:78:in `process_each_request'
/usr/lib/ruby/1.8/fcgi.rb:612:in `each_cgi'
/usr/lib/ruby/1.8/fcgi.rb:609:in `each'
/usr/lib/ruby/1.8/fcgi.rb:609:in `each_cgi'
/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:77:in `process_each_request'
/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:76:in `catch'
/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:76:in `process_each_request'
/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:50:in `process!'
/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:24:in `process!'
dispatch.fcgi:24
Rendering /home/nordicfx/redmine.nordicfx.com/public/404.html (404 Not Found)
RE: 500 error running with Passenger at Dreamhost - Added by Jacob Berggren almost 16 years ago
I also got this at the same time in the fastcgi.crash.log:
[03/Mar/2009:22:34:24 :: 17794] starting
[03/Mar/2009:22:35:33 :: 17794] asked to stop immediately
[03/Mar/2009:22:35:33 :: 17794] stopping after explicit exit
RE: 500 error running with Passenger at Dreamhost - Added by Jean-Baptiste Barth almost 16 years ago
Ok, if I were you I'd contact dreamhost support ; maybe passenger does not find everything correctly, but it's hard to know without passenger conf (and I presume it's not an easy 3-lines conf if they offer mutualized hosting..)
RE: 500 error running with Passenger at Dreamhost - Added by Jacob Berggren almost 16 years ago
Yeah, I tried contacted them and they thought I should contact you... LOL.
I'll try them again, thanks for your help.