I just deployed my rails app to my production server. It's all working
locally, but when I switched it over to the production server (at
dreamhost) I get this error:
# Logfile created on Sun Aug 19 15:22:48 -0700 2007 by logger.rb/
1.5.2.9
[19/Aug/2007:15:22:48 :: 1841] starting
[19/Aug/2007:15:22:48 :: 1841] Dispatcher failed to catch: You have a
nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.split (NoMethodError)
/usr/lib/ruby/1.8/cgi.rb:897:in `parse'
/usr/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/
cgi_ext/raw_post_data_fix.rb:45:in `initialize_query'
/usr/lib/ruby/1.8/cgi.rb:2274:in `initialize'
/usr/lib/ruby/1.8/fcgi.rb:594:in `new'
/usr/lib/ruby/1.8/fcgi.rb:594:in `each_cgi'
/usr/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:141:in
`process_each_request!'
/usr/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:55:in
`process!'
/usr/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:25:in
`process!'
./dispatch.fcgi:24
almost killed by this error
[19/Aug/2007:15:22:48 :: 1841] Dispatcher failed to catch: You have a
nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.split (NoMethodError)
/usr/lib/ruby/1.8/cgi.rb:897:in `parse'
/usr/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/
cgi_ext/raw_post_data_fix.rb:45:in `initialize_query'
/usr/lib/ruby/1.8/cgi.rb:2274:in `initialize'
/usr/lib/ruby/1.8/fcgi.rb:594:in `new'
/usr/lib/ruby/1.8/fcgi.rb:594:in `each_cgi'
/usr/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:141:in
`process_each_request!'
/usr/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:55:in
`process!'
/usr/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:25:in
`process!'
./dispatch.fcgi:24
killed by this error
Does anyone have any ideas of what's going on?
dispatch is set to the correct path, db is right. So I don't know what
I'm doing wrong here.
Hey brien,
even i am not sure here,
but i guess just you can try this,
try change the path of your /tmp/mysql.sock' (2))
(i assume that user who creates /tmp/mysql.sock in production mode has
write permission)