ABinitio connectivity issues to MOngo DB

[mongod...@gmail.com]

HI Gurus,

We are having issues connecting MOngoDB to Ab-Initio .We are having the below issue with both Mongo 2.6 and 3.0 .I am able to connect successfully with the credentials but with ABinitio we see the below error:

 The command "/appl/abinitioV3/abinitio-V3-2-2/bin/m_db test /appl/SandBoxes/GDXV3/****/sand/SFDC/SFDC_0_0_0/db/mongo.dbc" failed.

Command output: ABINITIO(DB29010): Error retrieving Mongo server status: not authorized on admin to execute command { serverStatus: 1 }

We tried contacting Abinitio and they said its Priviliges issue.I tried connecting with Root user but the issue persists

Thanks,

Ravi

[Stephen Steneker]

Hi Ravi,

I'm not familiar with ABinitio .. is that a hosted Database-as-a-Service company or have you deployed your own instance of MongoDB?

If this is DBaaS, privileges are something you'd have to sort out with the provider. You may not have access to certain global commands (like `serverStatus`) on shared database instances.

Regards,

Stephen

[mongod...@gmail.com]

Hi Stephen,

Abinitio is a datawarehousing tool and we are trying to use ABinitio to extract data from a legacy database and push it to MOngoDB.

When we try to query Serverstatus(using Abinitio  drivers)then we see this error .I did a server status using the same credentials on the MOngo DB and its showing me the status.

Thanks,

Ravi

[Stephen Steneker]

On Thursday, 9 April 2015 12:41:46 UTC+10, mongod...@gmail.com wrote:

Abinitio is a datawarehousing tool and we are trying to use ABinitio to extract data from a legacy database and push it to MOngoDB.

When we try to query Serverstatus(using Abinitio  drivers)then we see this error .I did a server status using the same credentials on the MOngo DB and its showing me the status.

Hi Ravi,

If you are connecting with the exact same credentials in the mongo shell and Abinitio, it sounds like the issue is specific to the Abinitio driver if the mongo shell works.

Are you able to connect with Abinitio and successfully run a different command (for example, a `find()` query)?

Also, you mentioned both MongoDB 2.6 & 3.0 in your first post. Which one are you using? If you've recently updated to MongoDB 3.0, it's possible that the Abinitio driver has not been updated to support the new SCRAM-SHA-1 default authentication.

Regards,

Stephen

[mongod...@gmail.com]

Stephen,

We started our project with MongoDB 3.0 but the authentication in place didn't support our custom tools so we had to go back to 2.6 so that our custom tools and open source MongoDB connectors would support them .

Animation in particular worked with mongo 2.6 when authentication is not enabled but once the authentication is enabled we are seeing issues.

Abinitio is an popular DW tool and the support said there is an issue with Mongo which is not possible because it works with 2.6 with no authentication enabled.

Are we missing something here ??


Ravi

[Stephen Steneker]

Hi Ravi,

If you had problems as soon as you upgraded to MongoDB 3.0 with authentication, I expect the issue is that Abinitio has not been updated to support the new default SCRAM-SHA-1 authentication in MongoDB 3.0: http://docs.mongodb.org/manual/release-notes/3.0-scram/. An update to a MongoDB 3.0 compatible driver is also required to use the new WiredTiger storage engine in MongoDB 3.0.

I would suggest asking Abinitio if they have tested for MongoDB 3.0 compatibility yet.

Note: there is a workaround to use the older MONGODB-CR authentication in 3.0, but a better approach would be to use updated tools:

 https://groups.google.com/forum/#!topic/mongodb-user/4-nbyYch7bA

Regards,

Stephen

[mongod...@gmail.com]

Stephen,

We didn't do an upgrade we just started with an fresh 3.0 installation as it didn't work with 3.0 we thought 2.6 works and installed 2.6 freshly and started it.Abinitio works with 2.6 with no auth mode so why are we seeing issues when auth mode is enabled??

I been through the link you sent but I am not sure if MongoDB would support ??this kind of upgrade where authozation part is upgraded in later point of time .

Thanks,
Ravi

[Stephen Steneker]

On Thursday, 9 April 2015 23:16:51 UTC+10, mongod...@gmail.com wrote:

We didn't do an upgrade we just started with an fresh 3.0 installation as it didn't work with 3.0 we thought 2.6 works and installed 2.6 freshly and started it.Abinitio works with 2.6 with no auth mode so why are we seeing issues when auth mode is enabled??

I been through the link you sent but I am not sure if MongoDB would support ??this kind of upgrade where authozation part is upgraded in later point of time .

Hi Ravi,

The default authentication in MongoDB 3.0 has changed from MONGO-CR to SCRAM-SHA-1. I assumed you did an upgrade, but if you did a fresh install then SCRAM-SHA-1 auth is definitely in effect.

If you are using a tool/driver that doesn't support the new SCRAM-SHA-1 authentication you will be unable to login to a 3.0 instance with default auth enabled. This sounds like the issue you are experiencing.

It would be best to contact Abinitio about MongoDB 3.0 support, as it seems like the version you are using is not compatible with MongoDB 3.0 yet.

In your initial post you suggested you were having problems with auth in both 2.6 and 3.0. Is the issue only with 3.0, or are you also getting an error in 2.6?

If you are having troubles with MongoDB 2.6, can you provide information on the user & role that you have created?

  db.getUser('username')
  db.getRole('rolename', {showPrivileges: true})  // if the user has a custom role

In MongoDB 2.6 the serverStatus command requires the "clusterMonitor" role (or a user-defined role including the "serverStatus" privilege at a cluster level): http://docs.mongodb.org/v2.6/reference/built-in-roles/#clusterMonitor.

Thanks,

Stephen

[mongod...@gmail.com]

Stephen,

Here is what i have :

With dbausr which i have created on "ADMIN" db i am abale to see the server status.I provided developer to access tst DB with read write role and he is unable to connect to MOngo.

I tried adding the clusteradmin role to the user "tstai" but below is the error:

Error: Could not find user ilmai@admin at src/mongo/shell/db.js:1287

> db.getUser('root')

null

> db.getUser('dbausr')

{

        "_id" : "admin.dbausr",

        "user" : "dbausr",

        "db" : "admin",

        "roles" : [

                {

                        "role" : "root",

                        "db" : "admin"

                }

        ]

}

> db.getUser('tstai')

null

> use tst

switched to db tst

> db.getUser('tstai')

{

        "_id" : "tst.tstai",

        "user" : "tstai",

        "db" : "tst",

        "roles" : [

                {

                        "role" : "readWrite",

                        "db" : "tst"

                }

        ]

}

> db.grantRolesToUser(

...   "tstai",

...   [

...     { role: "clusteradmin", db: "tst" }

...   ]

... )

2015-04-09T11:24:32.422-0400 Error: No role named clusteradmin@tst at src/mongo/shell/db.js:1287

>

>

>

> use admin

switched to db admin

> db.grantRolesToUser(

...   "tstai",

...   [

...     { role: "clusteradmin", db: "tst" }

...   ]

... )

2015-04-09T11:24:43.473-0400 Error: Could not find user tstai@admin at src/mongo/shell/db.js:1287