Can't connect to sandbox cluster!

Hi @Daniel_79560,

Please try connecting to your cluster using the following connection String:

mongo mongodb+srv://sandbox-7mkrb.mongodb.net/test --username m001-student --password m001-mongodb-basics

I have just removed the inverted commas from the original Connection String.

I hope it works now!!

Let me know, if it still shows any error.

Thanks,
Sonali

Yeah, I’ve tried it with and without quotes; I get the same error either way. I should point out I can connect with Compass, but not the shell.

Hello everyone!

I can’t connect to sandbox cluster, before joining MongoDB, I had a created a Sandbox with another name following the instructions of MongoDB site.
My questions are, can I solve this problem in some way? ,should I create the sandbox with another account? what makes me doubt is if I connect being two different accounts,

sorry for my Engish :confused: and thanks a lot to anyone can help me!!!

Hi @David_74433,

Do you remember the username and password of the Sandbox cluster that you had created earlier?
What is the connection String that you are using to connect to the Sandbox cluster?

You can also login into the Atlas account, to check the status of your cluster.

Thanks,
Sonali

Chapter 2 problem
I get the following error from OSX when connection to my new cluster.

user is not allowed to do action [getLog] on [admin.]

Here’s my connection string
mongo “mongodb+srv://m001-nl7my.mongodb.net/test” --username m001-student

I have verified my user has read/write

You can ignore that warning message.It says user does not have privs on admin DB
You must be already connected to mongodb.You can continue with your work

Thanks. Wasted about 30 minutes troubleshooting maybe we should put that safely ignore message on the lecture notes.

thanks again!

Hi @John_09893,

I apologise that you had to face such an issue.

Yes, you can ignore the warning and proceed further with the course.

I have noted your suggestion and will definitely look for a way to make it easy for the users.

Thanks,
Sonali

I found the following error. Says "Error while trying to show server startup warnings: user is not allowed to do action [getlog] on [admin.]

I not sure what I did wrong. image

Please ignore that error and continue with your work.You are already connected to mongodb
It is warning error which says user does not have privileges on admin DB

1 Like

thanks a lot Sonali_48808
I have other prolem, please help me

thanks I can do it with your indication

hi
I had an error in the cluster user, now I can connect

thanks!

Hi
I’m having same issue, but I’m trying to connect to sandbox using below link,

mongo “mongodb://sandbox-shard-00-00-ifiu7.mongodb.net:27017,sandbox-shard-00-01-ifiu7.mongodb.net:27017,sandbox-shard-00-02-ifiu7.mongodb.net:27017/video?replicaSet=Sandbox-shard-0” --ssl --authenticationDatabase admin --username m001-student --password m001-mongodb-basics

but unable to connect due to below error

C:\Windows\system32>mongo “mongodb://sandbox-shard-00-00-ifiu7.mongodb.net:27017,sandbox-shard-00-01-ifiu7.mongodb.net:27017,sandbo
x-shard-00-02-ifiu7.mongodb.net:27017/video?replicaSet=Sandbox-shard-0” --ssl --authenticationDatabase admin --username m001-studen
t --password m001-mongodb-basics
2019-07-09T00:14:02.549+0530 I CONTROL [main] Hotfix KB2731284 or later update is not installed, will zero-out data files
MongoDB shell version: 3.2.10
connecting to: mongodb://sandbox-shard-00-00-ifiu7.mongodb.net:27017,sandbox-shard-00-01-ifiu7.mongodb.net:27017,sandbox-shard-00-0
2-ifiu7.mongodb.net:27017/video?replicaSet=Sandbox-shard-0
2019-07-09T00:14:02.643+0530 I NETWORK [thread1] Starting new replica set monitor for Sandbox-shard-0/sandbox-shard-00-00-ifiu7.mo
ngodb.net:27017,sandbox-shard-00-01-ifiu7.mongodb.net:27017,sandbox-shard-00-02-ifiu7.mongodb.net:27017
2019-07-09T00:14:02.648+0530 I NETWORK [ReplicaSetMonitorWatcher] starting
2019-07-09T00:14:02.868+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:03.394+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:03.916+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:04.438+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:04.960+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:05.499+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:06.021+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:06.543+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:07.065+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:07.587+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:08.113+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:08.638+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:09.325+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:09.901+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:10.568+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:11.093+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:11.615+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:12.236+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:12.670+0530 W NETWORK [ReplicaSetMonitorWatcher] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:12.758+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:13.280+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:13.802+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:14.324+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:14.848+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:15.368+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:16.116+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:16.810+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:17.514+0530 W NETWORK [thread1] No primary detected for set Sandbox-shard-0
2019-07-09T00:14:17.515+0530 E QUERY [thread1] Error: connect failed to replica set Sandbox-shard-0/sandbox-shard-00-00-ifiu7.mo
ngodb.net:27017,sandbox-shard-00-01-ifiu7.mongodb.net:27017,sandbox-shard-00-02-ifiu7.mongodb.net:27017 :
connect@src/mongo/shell/mongo.js:223:14
@(connect):1:6

exception: connect failed

can anybody will able to help?

Are you still facing the issue?
I can connect.May be temporary N/W issue

C:\Users\ramrt>mongo “mongodb://sandbox-shard-00-00-ifiu7.mongodb.net:27017,sandbox-shard-00-01-ifiu7.mongodb.net:27017,sandbox-shard-00-02-ifiu7.mongodb.net:27017/video?replicaSet=Sandbox-shard-0” --ssl --authenticationDatabase admin --username m001-student --password m001-mongodb-basics
MongoDB shell version v4.0.5
connecting to: mongodb://sandbox-shard-00-00-ifiu7.mongodb.net:27017,sandbox-shard-00-01-ifiu7.mongodb.net:27017,sandbox-shard-00-02-ifiu7.mongodb.net:27017/video?authSource=admin&gssapiServiceName=mongodb&replicaSet=Sandbox-shard-0

MongoDB Enterprise Sandbox-shard-0:PRIMARY> db
video
MongoDB Enterprise Sandbox-shard-0:PRIMARY> show dbs
admin 0.000GB
local 3.589GB

MongoDB Enterprise Sandbox-shard-0:PRIMARY> show collections
MongoDB Enterprise Sandbox-shard-0:PRIMARY>

Looks like you have not loaded video yet

Hi @onkarramdin,

In addition to @Ramachandra_37567’s reply, I would recommend you to use latest version of the Mongo Shell. You can download the MongoDB Enterprise Server from MongoDB Download Center.

Please let me know, if you have any questions.

Thanks,
Sonali

Hi @Sonali_Mamgain,

Yes it seems to be version issue, I’ve installed MongoDB Enterprise Edition 3.2 version and also my PC doesn’t have KB2999226 patch installed due to which now I’m unable to install Enterprise Edition 4.10 version.

Due to which I missed my labs, is it possible to extend the deadline for labs?

Thanks @Ramachandra_37567 for reply.

I tried to connecting sandbox cluster from local mongo shell but it gave same error.
As mentioned by @Sonali_Mamgain it seems to be version compatibility issue between sandbox cluster i.e. 4.10 and my local mongo shell version i.e. 3.2.

I’ll try to install current 4.10 enterprise edition on my local machine today and will try connecting to sandbox.

Thanks !