Skip to content
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.

Random "error 16550: not authorized for query on db_name.collection_name" #252

Closed
iabdulin opened this issue Jan 20, 2014 · 2 comments
Closed
Milestone

Comments

@iabdulin
Copy link

Sorry, I can't reproduce this myself, but I receive a lot of exception notification emails from my server (NewRelicPinger pings my website every couple minutes).

Moped 1.5.1 (also tried 1.4.5)
mongoid 3.1.6
mongodb 2.4.8

Maybe it's related to #247, but I am not sure (I don't use any replica sets).

See https://github.com/mongodb/mongo/blob/master/docs/errors.md
for details about this error.
vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:370:in `block in query'


Backtrace:

vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:370:in block in query' vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:573:in[]'
vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:573:in block (3 levels) in flush' vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:572:inmap'
vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:572:in block (2 levels) in flush' vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:138:inensure_connected'
vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:568:in block in flush' vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:583:inlogging'
vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:567:in flush' vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:556:inprocess'
vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/node.rb:358:in query' vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/session/context.rb:44:inblock in query'
vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/session/context.rb:105:in block in with_node' vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/cluster.rb:250:inwith_secondary'
vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/session/context.rb:104:in with_node' vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/session/context.rb:43:inquery'
vendor/bundle/ruby/2.1.0/bundler/gems/moped-675440c65f44/lib/moped/query.rb:115:in first' vendor/bundle/ruby/2.1.0/gems/mongoid-3.1.6/lib/mongoid/contextual/mongo.rb:278:inblock in last'
vendor/bundle/ruby/2.1.0/gems/mongoid-3.1.6/lib/mongoid/contextual/mongo.rb:527:in with_inverse_sorting' vendor/bundle/ruby/2.1.0/gems/mongoid-3.1.6/lib/mongoid/contextual/mongo.rb:277:inlast'
vendor/bundle/ruby/2.1.0/gems/mongoid-3.1.6/lib/mongoid/contextual.rb:19:in last' vendor/bundle/ruby/2.1.0/gems/mongoid-3.1.6/lib/mongoid/finders.rb:127:inlast'

@mgwidmann
Copy link

I'm seeing the same thing in conjunction with the bcdatabase gem. When encrypted we get this problem, when not encrypted everything works fine. If we use the wrong password we get an auth fails message (plus I am able to decrypt it via the rails console), so it doesn't seem to be related to bcdatabase.

@arthurnn
Copy link
Contributor

closing this as #324 was merged and it should solve this issue

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants