2012-07-31 53 views
22

我有一个Rails 3应用程序,成功部署到MongoID 3 Heroku(使用MongoHQ) - 但后来发生了一些事情(无法确定它到底是什么),并且构建开始在Heroku上崩溃。Heroku&MongoHQ:ActionView :: Template :: Error(操作:#<Moped :: Protocol :: Commands :: Authenticate failed with error“auth failed”)

所以这是我的错误:

TLDR:Moped::Errors::AuthenticationFailure (The operation: #<Moped::Protocol::Commands::Authenticate ... failed with error "auth fails")

是什么使这更难以调试的是,它的工作在本地主机上就好了。 现在我正在想出这可能是什么。

app[web.1]: >> Thin web server (v1.4.1 codename Chromeo) 
app[web.1]: >> Maximum connections set to 1024 
app[web.1]: >> Listening on 0.0.0.0:58731, CTRL+C to stop 
heroku[web.1]: State changed from starting to up 
app[web.1]: 
app[web.1]: 
app[web.1]: Started GET "/" for 212.86.9.90 at 2012-07-31 08:08:07 +0000 
heroku[router]: GET cool-name-123.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=171ms status=200 bytes=1286 
heroku[router]: GET cool-name-123.herokuapp.com/assets/application-8e7bfeeffc9291864e5b42d908c2fdda.css dyno=web.1 queue=0 wait=0ms service=11ms status=200 bytes=92524 
heroku[router]: GET cool-name-123.herokuapp.com/assets/application-aa557bde70f1236cdf90c913043c4382.js dyno=web.1 queue=0 wait=0ms service=16ms status=200 bytes=122836 
heroku[router]: GET cool-name-123.herokuapp.com/favicon.ico dyno=web.1 queue=0 wait=0ms service=3ms status=200 bytes=0 
app[web.1]: 
app[web.1]: 
app[web.1]: Started GET "/originals/new" for 212.86.9.90 at 2012-07-31 08:08:11 +0000 
heroku[router]: GET cool-name-123.herokuapp.com/originals/new dyno=web.1 queue=0 wait=0ms service=31ms status=200 bytes=1808 
app[web.1]: 
app[web.1]: 
app[web.1]: Started POST "/originals" for 212.86.9.90 at 2012-07-31 08:08:34 +0000 
app[web.1]: 
app[web.1]: Moped::Errors::AuthenticationFailure (The operation: #<Moped::Protocol::Commands::Authenticate 
app[web.1]: @length=154 
app[web.1]: @request_id=3 
app[web.1]: @response_to=0 
app[web.1]: @op_code=2004 
app[web.1]: @flags=[] 
app[web.1]: @full_collection_name="app123.$cmd" 
app[web.1]: @limit=-1 
app[web.1]: @skip=0 
app[web.1]: @selector={:authenticate=>1, :user=>"heroku", :nonce=>"xyz", :key=>"xyz"} 
heroku[router]: POST cool-name-123.herokuapp.com/originals dyno=web.1 queue=0 wait=0ms service=1486ms status=500 bytes=643 
app[web.1]: @fields=nil> 
app[web.1]: failed with error "auth fails"): 
app[web.1]: app/controllers/originals_controller.rb:19:in `block in create' 
app[web.1]: app/controllers/originals_controller.rb:18:in `create' 
app[web.1]: 
app[web.1]: 
heroku[router]: GET cool-name-123.herokuapp.com/favicon.ico dyno=web.1 queue=0 wait=0ms service=3ms status=304 bytes=0 
app[web.1]: 
app[web.1]: 
app[web.1]: Started GET "/" for 212.86.9.90 at 2012-07-31 08:09:40 +0000 
heroku[router]: GET cool-name-123.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=11ms status=304 bytes=0 

我最近在努力与Heroku的,并因此我想我应该有DB驱动程序的选择&服务的正确设置(使用新的YML方案+红宝石1.9.3中的Gemfile) 。

当我运行heroku config --app app_name我得到

DATABASE_URL  => postgres://rhalppyjrb:[email protected]/rhalppyjrb 
GEM_PATH   => vendor/bundle/ruby/1.9.1 
LANG    => en_US.UTF-8 
MONGOHQ_URL   => mongodb://heroku:[email protected]:27054/app123 
PATH    => bin:vendor/bundle/ruby/1.9.1/bin:/usr/local/bin:/usr/bin:/bin 
RACK_ENV   => production 
RAILS_ENV   => production 
SHARED_DATABASE_URL => postgres://rhalppyjrb:[email protected]/rhalppyjrb 

我mongoid.yml看起来是这样的:

production: 
    sessions: 
    default: 
      uri: <%= ENV['MONGOHQ_URL'] %> 
      options: 
      consistency: :strong 
      skip_version_check: true 
      safe: true 

的Gemfile是这样的:

source 'https://rubygems.org' 

gem 'bundler', '1.2.0.rc' 

ruby '1.9.3' 

gem 'rails', '3.2.6' 
gem 'thin' 
gem 'rmagick', :require => 'RMagick' 
gem "carrierwave-mongoid", :git => "git://github.com/jnicklas/carrierwave-mongoid.git", :branch => "mongoid-3.0", :require => 'carrierwave/mongoid' 

group :assets do 
    gem 'sass-rails', '~> 3.2.3' 
    gem 'coffee-rails', '~> 3.2.1' 
    gem 'uglifier', '>= 1.0.3' 
    gem "therubyracer", :platform => :ruby 
end 

gem 'jquery-rails' 
gem "haml", ">= 3.1.6" 
gem "mongoid", ">= 3.0.3" 
gem "devise", ">= 2.1.2" 
gem "devise_invitable", ">= 1.0.2" 
gem "cancan", ">= 1.6.8" 
gem "rolify", ">= 3.1.0" 
gem "bootstrap-sass", ">= 2.0.4.0" 
gem "simple_form" 

group :development do 
    gem "guard", ">= 0.6.2" 
    gem 'rb-fsevent' 
    gem 'growl' 
    gem "haml-rails", ">= 0.3.4" 
    gem "guard-bundler", ">= 0.1.3" 
    gem "guard-rails", ">= 0.0.3" 
    gem "guard-livereload", ">= 0.3.0" 
    gem "guard-rspec", ">= 0.4.3" 
end 

group :test do 
    gem "database_cleaner", ">= 0.8.0" 
    gem "mongoid-rspec", "1.4.6" 
    gem "email_spec", ">= 1.2.1" 
end 

group :development, :test do 
    gem "factory_girl_rails", ">= 3.5.0" 
    gem "rspec-rails", ">= 2.11.0" 
end 
+0

你有没有与MongoHQ_URL成功连接与蒙戈客户端使用? – shingara 2012-08-01 07:31:29

+0

刚刚有完全相同的问题。一切都很好,我跑db:重新调整空数据库来测试一些东西,现在得到这个错误。无法弄清楚什么是错的。一切工作正常localhost,和我的mongo连接在生产是好的,直到五分钟前。 – odigity 2012-08-03 10:45:09

+0

你弄明白了吗? – Nerian 2012-08-12 23:33:11

回答

20

的问题是,您的身份验证凭证不再正确。具体而言,您尝试认证的用户不再存在。

原因是,当你做一个rake db:reseed所有的数据被删除,包括数据库级别的用户。

例子:

➜ skadi git:(master) ✗ mongo   
    MongoDB shell version: 2.0.7 
    connecting to: test 
    > use skadi_development 
    switched to db skadi_development 
    > db.system.users.find() 
    > db.addUser("joe", "passwordForJoe") 
    { "n" : 0, "connectionId" : 191, "err" : null, "ok" : 1 } 
    { 
    "user" : "joe", 
    "readOnly" : false, 
    "pwd" : "dac588613249fe92703afb262ec53b82", 
    "_id" : ObjectId("5030d5181cefbd2b04a99e30") 
    } 
    > db.system.users.find() 
    { "_id" : ObjectId("5030d5181cefbd2b04a99e30"), "user" : "joe", "readOnly" : false, "pwd" : "dac588613249fe92703afb262ec53b82" } 
    > exit 
    bye 

    ➜ skadi git:(master) ✗ rake db:reseed 

    ➜ skadi git:(master) ✗ mongo   
    MongoDB shell version: 2.0.7 
    connecting to: test 
    > use skadi_development 
    switched to db skadi_development 
    > db.system.users.find() 
    => Nothing 

所以当您尝试连接到数据库,你的证书不再有效。

你可以在你的MongoHQ管理面板中检查。你可以通过Heroku找到它,选择你的应用程序,点击资源并点击MongoHQ。然后点击数据库用户选项卡。

rake db:reseed用于按照您的预期工作,但它随新版本的mongoid而改变。为了移除除system *之外的所有集合,您可以使用rake db:purge

您可能需要使用主分支,因为该耙机任务在稳定版本中尚不可用。或者在你的代码中使用Mongoid.purge!,这个工作稳定。

详情:https://github.com/mongoid/mongoid/issues/2275

+0

这工作;必须重新添加预期的用户。 – 2013-05-11 02:01:54

+0

也适用于我。谢谢! – okysabeni 2013-10-11 02:47:46

+0

完美,像魅力一样工作!谢谢 – RSB 2015-03-24 13:16:34

相关问题