App close on replica set connection

[pcorderoe]

Hi,
when i try to connect using a replica set option the program close. I have a cluster over Google Cloud. I'll try to connect using this mongodb://xxx.xxx.xxx.xxx:27017,xx.xx.xx.xx:27017 but don't work. Please help!

[jeromelebel]

Which version do you use? Do you mean there is a crash? Can you give me the full details of the crash?

[tdegrunt]

I'm able to connect to a replicaset, using the following for the servers field:

db1.ams2.do.dev:27017,db2.ams2.do.dev:27017,db3.ams2.do.dev:27017

If you enter it exactly like this, does it still crash?
Also have you filled in a "Set Name"?

If it still doesn't work, can you show a screenshot of the settings?

[pcorderoe]

Thanks for your answers. I fill form like this:

Name:Replica Set
Set Name: rs0
Servers: mongodb://xxx.xxx.xxx.xxx:27017,xxx.xxx.xx.x:27017
ReadMode: Primary Preferred

errormongohub.pdf | uploaded via ZenHub

[tdegrunt]

Can you drop the mongodb:// and try again?

[jeromelebel]

Yes, that should be the reason of the crash. I need to fix this issue.

[pcorderoe]

i try (without mongodb://) but show an error message: No aceptable peer could be found

[jeromelebel]

do you use ssh tunneling?

[tdegrunt]

Can you connect to each of the servers from the command line using the following?

mongo --host xxx.xxx.xxx.xxx:27017

If not, what are you using? Also the output of rs.status() on the mongo console might help debug this.

[pcorderoe]

i am using normal connection, with Server: Standalone, one connection for each server, and work fine

[pcorderoe]

I'm not using ssh tunneling

[jeromelebel]

Should be fixed in 3.1. I let you verify this issue and close it.

[bolerovt]

same problem here, can not connect replica set, but can connect to each stand alone server

[bolerovt]

do we need to wait until the mongo 3.1 to fix this issue?