![]() T19:24:17.722+0200 W NETWORK Unable to reach primary for set MongoDB-Cluster T19:24:07.331+0200 I NETWORK Confirmed replica set for MongoDB-Cluster is MongoDB-Cluster/PrivateIP:27017,PrivateIP:27017 T19:24:07.199+0200 I NETWORK Starting new replica set monitor for MongoDB-Cluster/PublicIP:27017,PublicIP:27017 But then it redirects to the internal IP-address, which isn’t available from the outside.Ĭonnecting to: mongodb://PublicIP:27017,PublicIP:27017/?compressors=disabled&gssapiServiceName=mongodb&replicaSet=MongoDB-Cluster I have been stuck on this issue for quite some time and am not able to connect to my replica-set so that if my primary goes down, I’m able to write to my secondary. MongoDB Compass shows “Connection timeout”. T21:14:20.394+0000 I ACCESS Successfully authenticated as principal user on admin from client My.:57252 "īut when I try to connect to the replicaset with following connection -string using mongodb compass logs show: T21:14:20.262+0000 I NETWORK connection accepted from My.:57252 #22 (4 connections now open) Saying : "It looks like you are trying to access MongoDB over HTTP on the native driver port. Now when tying to connect from the public IP, I can get the http page for each node seperately. Replication over the internal network seems to work. The replica set gives the correct status for all three nodes, even when one is shut down the other one will take it over. PidFilePath: /var/run/mongodb/mongod.pid # location of pidfile I have recently built a mongodb replica-set with two replication nodes and one arbiter.Īll three nodes have a similar configuration: # nf For starters I’m sorry if I post this topic in the wrong category.
0 Comments
Leave a Reply. |