I am creating MongoDB replication on local server by first manually creating three different databases folders with names like MongoDB, MongoDB1 and MongoDB2. Each one of them have data, bin and log sub folders and an individual mongod.cfg file. The data sub folders also have db sub folder and that is where I have all my database files.

For me MongoDB, MongoDB1 and MongoDB2 are all database instances and I am adding configuration to my first Mongo database folder (MongoDB) in mongod.cfg file as:

   fork: true
   port: 27017
   dbPath: C:\MongoDB\data\db
   destination: file
   path: "C:\MongoDB\log\mongo.log"
   logAppend: true
      enabled: true
   authorization: enabled
   replSetName: repl1   

I then change the parameters replSetName, dbpath, systemlog path and port number in each of the configuration files for the other two Mongo database folders (MongoDB1 and MongoDB2).

I am still not able to create replicaset between these three database folders.

  • What step is wrong?
  • Am I creating database folder in a wrong way?
  • May I know which step is wrong and how to fix it?

After I start the Mongodb service of first instance and use Windows CMD Prompt to enter the command like written below to start creating replica set, it continues running and never stops and creates a lock file in my folder.


mongod --port 27017 --dbpath "C:\Mongodb\data\db" --replSet repl1


Fri Jul 07 09:07:36.787 [initandlisten] MongoDB starting : pid=15892 port=27017 dbpath=\data\db\ 64-bit host=LT-SRA-EB-27ZL
Fri Jul 07 09:07:36.789 [initandlisten] db version v2.4.9
Fri Jul 07 09:07:36.791 [initandlisten] git version: 52fe0d21959e32a5bdbecdc62057db386e4e029c
Fri Jul 07 09:07:36.792 [initandlisten] build info: windows sys.getwindowsversion(major=6, minor=1, build=7601, platform=2, service_pack='Service Pack 1') BOOST_LIB_VERSION=1_49
Fri Jul 07 09:07:36.792 [initandlisten] allocator: system
Fri Jul 07 09:07:36.792 [initandlisten] options: { replSet: "rpl1" }
Fri Jul 07 09:07:36.798 [initandlisten] journal dir=\data\db\journal
Fri Jul 07 09:07:36.799 [initandlisten] recover : no journal files present, no recovery needed
Fri Jul 07 09:07:36.854 [websvr] admin web console waiting for connections on port 28017
Fri Jul 07 09:07:36.854 [initandlisten] waiting for connections on port 27017
Fri Jul 07 09:07:36.867 [rsStart] replSet can't get local.system.replset config from self or any seed (EMPTYCONFIG)
Fri Jul 07 09:07:36.867 [rsStart] replSet info you may need to run replSetInitiate -- rs.initiate() in the shell -- if that is not already done
Fri Jul 07 09:07:41.517 [initandlisten] connection accepted from #1 (1 connection now open)
Fri Jul 07 09:07:41.526 [conn1] end connection (0 connections now open)
Fri Jul 07 09:07:44.513 [initandlisten] connection accepted from #2 (1 connection now open)
Fri Jul 07 09:07:44.525 [conn2] assertion 13435 not master and slaveOk=false ns:sc82rev161221_tracking_contact.ProcessingPool query:{ $query: { Scheduled: { $lte: new Date(1499432864509) } }, $orderby: { Scheduled: 1 } }
Fri Jul 07 09:07:44.525 [conn2]  ntoskip:0 ntoreturn:16
Fri Jul 07 09:07:44.525 [conn2] end connection (0 connections now open)
Fri Jul 07 09:07:46.529 [initandlisten] connection accepted from #3 (1 connection now open)
Fri Jul 07 09:07:46.870 [rsStart] replSet can't get local.system.replset config from self or any seed (EMPTYCONFIG)
Fri Jul 07 09:07:56.505 [initandlisten] connection accepted from #4 (2 connections now open)
Fri Jul 07 09:07:56.515 [conn4] assertion 13435 not master and slaveOk=false ns:sc82rev161221_tracking_live.ProcessingPool query:{ $query: { Scheduled: { $lte: new D
  • Before ReplicaSet creation, how do I create three database instances/servers with database in them?

  • Is my method above is correct in regards to creating three databases instances/server?

  • May I know all the steps to create ReplicaSet between these three databases on my local, using windows cmd commands?

I know I am making mistake somewhere, but I do not know where. Your feedback will help.


2 Answers 2


Error is change that replSetName! If you have replica set, every member what belongs that replica set MUST have (of course) same replSetName.

So, in every mongod.conf file there must be same

replSetName: repl1

After you have started those three replica set nodes, connect one of them with mongo command and give rs.initiate( { _id : "repl1", members: [ { _id : 0, host : "localhost:27017" } ] }) command. After few seconds, press 'Enter' and it should say PRIMARY. After that you can add those two other nodes with rs.add("localhost:27018") and rs.add("localhost:27019") commands. rs.status() and rs.conf() will show that you have functioning replica set.

  • ok I changed the replSetName to repl1 in all three config files and sorry it is not two \\, it is one \. That is typing mistake. I fixed it in my question now.
    – john
    Jul 7, 2017 at 12:57
  • @john I edit my answer to have more information
    – JJussi
    Jul 7, 2017 at 14:40

Few things:

  • You need to have same replset name in all 3 config file
  • Look at the value of your dbpath. Why do you have two \\?
  • You mongod should continuously run and not stop. If you do not want too many windows open at the same time you can run those as a service or even use a batch file.
  • Start all 3 and let those run.
  • Connect to a mongo shell and initiate your replica set.

    rs.initiate( { _id : "rs0", members: [ { _id : 0, host : "mongodb0.example.net:27017" } ] })

  • Follow from step 4 of this document.

  • What do you mean when you said, You mongod should continuously and not stop? How to start all 3 servers using windows cmd command?
    – john
    Jul 7, 2017 at 13:03
  • @john edited my answer. Jul 7, 2017 at 13:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.