Lab - Initiate a Replica Set Locally [Solved]

Hi everyone!!!
I just starting the first lab for Replication, but if I try get into the replica set using the authentication the command response is:

vagrant@m103:~$ mongo --host “m103-repl/192.168.103.100:27002” -u “m103-admin” -p “m103-pass” --authenticationDatabase “admin”
MongoDB shell version v3.6.9
connecting to: mongodb://192.168.103.100:27002/?replicaSet=m103-repl
2018-11-27T20:16:31.546+0000 I NETWORK [thread1] Starting new replica set monitor for m103-repl/192.168.103.100:27002
2018-11-27T20:16:31.548+0000 I NETWORK [thread1] Successfully connected to 192.168.103.100:27002 (1 connections now open to 192.168.103.100:27002 with a 5 second timeout)
2018-11-27T20:16:31.550+0000 I NETWORK [thread1] Successfully connected to m103-repl.localhost:27002 (1 connections now open to m103-repl.localhost:27002 with a 5 second timeout)
2018-11-27T20:16:31.550+0000 I NETWORK [ReplicaSetMonitor-TaskExecutor-0] Successfully connected to m103-repl.localhost:27003 (1 connections now open to m103-repl.localhost:27003 with a 5 second timeout)
2018-11-27T20:16:31.551+0000 I NETWORK [thread1] Successfully connected to 192.168.103.100:27001 (1 connections now open to 192.168.103.100:27001 with a 5 second timeout)
2018-11-27T20:16:31.551+0000 I NETWORK [ReplicaSetMonitor-TaskExecutor-0] Successfully connected to 192.168.103.100:27003 (1 connections now open to 192.168.103.100:27003 with a 5 second timeout)
2018-11-27T20:16:31.551+0000 W NETWORK [ReplicaSetMonitor-TaskExecutor-0] Unable to reach primary for set m103-repl

HI again, luckily í Could finishing the lab without problems And it could be validate.
thanks so much

1 Like