MongoDB Migration gives authentication error on mongodb in ubuntu 14
Closed this issue · 11 comments
I have an AWS machine where I have installed mongodb 3.2.7 and applied authentication there. Now when I call the migration scripts using the mongodb-migration library, it gives an authentication error saying that permission denied.
Please help.
Are you able to connect to it manually? By that I mean something like:
mongoClient = require('mongodb').MongoClient
dbName = 'test'
url = "mongodb://localhost:27017/#{dbName}"
mongoClient.connect url, (err, dbConn) ->
@dbConn.collection('posts').find {}, (err, posts) ->
console.log posts
If you run from "localhost" maybe try localhost and 0.0.0.0.
It runs perfectly fine on localhost. The problem comes when I try to run it on qa and production servers. I'm using mongoose to connect, however I even tried MongoClient, but it didn't work.
mongoose.connect("mongodb://{username}:{password}@localhost:27017/{dbName}?authMechanism=DEFAULT&authSource={authDB}");
This works well on localhost, but breaks on qa and production servers.
So it looks like this is not a migration module issue.
Have you tried connecting with an external client like mongohub or robomongo?
+1 to what @molszanski has said, so far I'm, not convinced it's this module's issue.
What happens @mehul-talentica when you run the code suggested above on the server?
mongoClient = require('mongodb').MongoClient
dbName = 'test'
url = "mongodb://localhost:27017/#{dbName}"
mongoClient.connect url, (err, dbConn) ->
@dbConn.collection('posts').find {}, (err, posts) ->
console.log posts
If it doesn't work the issue is with your setup.
Are you sure you run it on the same server the mongo instance is running on?
Should you use its public hostname instead of the localhost?
Closing due to lack of activity
@molszanski my apologies for not replying fast.
The migrations work when there is no authentication. The moment I enable authentication, either on my local machine or production servers, the migrations fail, giving the following error.
Files [ '001-moveProfilePictureToUserObject.js' ]
{ [MongoError: not authorized on QS to execute command { find: "dbMigrations", filter: {} }]
name: 'MongoError',
message: 'not authorized on {dbName} to execute command { find: "dbMigrations", filter: {} }',
ok: 0,
errmsg: 'not authorized on {dbName} to execute command { find: "dbMigrations", filter: {} }',
code: 13 }
D:\path to project\node_modules\mongodb-migrations\node_modules\mongodb\lib\utils.js:98
process.nextTick(function() { throw err; });
^
I'm pretty sure this is the setup issue unrelated to this module.
As suggested above you need to test it without the migrations and confirm/reject the hypothesis that you can't connect to the DB from a stand-alone node.js script.
I'm able to connect the application to the DB after removing the migration script.
Sure. Thanks mate!
Without debugging I have only one guess. Is it possible that the dbMigrations collection has some specific permissions that do not allow the user you use for migrations to run operations on it?
I see that mongo allows collection-level access control (https://docs.mongodb.com/v3.2/core/collection-level-access-control/), so is it possible, for example, that you've created the table yourself using the "master" account, and use the account with different permissions to access it?
Or maybe you don't have the collection in place and your user account doesn't have permissions to create it (normally it will be auto-created on the first write attempt)?