Unable to connect to mongod on Windows 10

unable to start mongod server cmd is showing as follow

2020-06-10T10:13:15.727+0530 I  CONTROL  [initandlisten] git version: 51d9fe12b5d19720e72dcd7db0f2f17dd9a19212
2020-06-10T10:13:15.727+0530 I  CONTROL  [initandlisten] allocator: tcmalloc
2020-06-10T10:13:15.728+0530 I  CONTROL  [initandlisten] modules: enterprise
2020-06-10T10:13:15.728+0530 I  CONTROL  [initandlisten] build environment:
2020-06-10T10:13:15.728+0530 I  CONTROL  [initandlisten]     distmod: windows-64
2020-06-10T10:13:15.728+0530 I  CONTROL  [initandlisten]     distarch: x86_64
2020-06-10T10:13:15.728+0530 I  CONTROL  [initandlisten]     target_arch: x86_64
2020-06-10T10:13:15.728+0530 I  CONTROL  [initandlisten] options: {}
2020-06-10T10:13:15.730+0530 I  STORAGE  [initandlisten] Detected data files in C:\data\db\ created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2020-06-10T10:13:15.731+0530 I  STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=5580M,cache_overflow=(file_max=0M),session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress],
2020-06-10T10:13:15.885+0530 I  STORAGE  [initandlisten] WiredTiger message [1591764195:884567][10776:140706903839984], txn-recover: Recovering log 1 through 2
2020-06-10T10:13:15.975+0530 I  STORAGE  [initandlisten] WiredTiger message [1591764195:974357][10776:140706903839984], txn-recover: Recovering log 2 through 2
2020-06-10T10:13:16.127+0530 I  STORAGE  [initandlisten] WiredTiger message [1591764196:126928][10776:140706903839984], txn-recover: Main recovery loop: starting at 1/24704 to 2/256
2020-06-10T10:13:16.392+0530 I  STORAGE  [initandlisten] WiredTiger message [1591764196:392214][10776:140706903839984], txn-recover: Recovering log 1 through 2
2020-06-10T10:13:16.516+0530 I  STORAGE  [initandlisten] WiredTiger message [1591764196:515672][10776:140706903839984], txn-recover: Recovering log 2 through 2
2020-06-10T10:13:16.573+0530 I  STORAGE  [initandlisten] WiredTiger message [1591764196:573567][10776:140706903839984], txn-recover: Set global recovery timestamp: (0, 0)
2020-06-10T10:13:16.975+0530 I  RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
2020-06-10T10:13:16.981+0530 I  STORAGE  [initandlisten] Timestamp monitor starting
2020-06-10T10:13:17.118+0530 I  CONTROL  [initandlisten]
2020-06-10T10:13:17.118+0530 I  CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2020-06-10T10:13:17.119+0530 I  CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2020-06-10T10:13:17.119+0530 I  CONTROL  [initandlisten]
2020-06-10T10:13:17.119+0530 I  CONTROL  [initandlisten] ** WARNING: This server is bound to localhost.
2020-06-10T10:13:17.122+0530 I  CONTROL  [initandlisten] **          Remote systems will be unable to connect to this server.
2020-06-10T10:13:17.123+0530 I  CONTROL  [initandlisten] **          Start the server with --bind_ip <address> to specify which IP
2020-06-10T10:13:17.124+0530 I  CONTROL  [initandlisten] **          addresses it should serve responses from, or with --bind_ip_all to
2020-06-10T10:13:17.124+0530 I  CONTROL  [initandlisten] **          bind to all interfaces. If this behavior is desired, start the
2020-06-10T10:13:17.125+0530 I  CONTROL  [initandlisten] **          server with --bind_ip to disable this warning.
2020-06-10T10:13:17.125+0530 I  CONTROL  [initandlisten]
2020-06-10T10:13:17.129+0530 I  SHARDING [initandlisten] Marking collection local.system.replset as collection version: <unsharded>
2020-06-10T10:13:17.131+0530 I  STORAGE  [initandlisten] Flow Control is enabled on this deployment.
2020-06-10T10:13:17.131+0530 I  SHARDING [initandlisten] Marking collection admin.system.roles as collection version: <unsharded>
2020-06-10T10:13:17.132+0530 I  SHARDING [initandlisten] Marking collection admin.system.version as collection version: <unsharded>
2020-06-10T10:13:17.134+0530 I  SHARDING [initandlisten] Marking collection local.startup_log as collection version: <unsharded>
2020-06-10T10:13:17.642+0530 I  FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory 'C:/data/db/diagnostic.data'
2020-06-10T10:13:17.645+0530 I  SHARDING [LogicalSessionCacheRefresh] Marking collection config.system.sessions as collection version: <unsharded>
2020-06-10T10:13:17.646+0530 I  SHARDING [LogicalSessionCacheReap] Marking collection config.transactions as collection version: <unsharded>
2020-06-10T10:13:17.649+0530 I  NETWORK  [listener] Listening on
2020-06-10T10:13:17.652+0530 I  NETWORK  [listener] waiting for connections on port 27017
2020-06-10T10:13:18.002+0530 I  SHARDING [ftdc] Marking collection local.oplog.rs as collection version: <unsharded>

The following indicates that the server is ready and waiting for connection.

Please post of screenshot of the issue showing you cannot connect.

1 Like

Hi @Charan_Narukulla and welcome to the community forums.

Note that this line means that you can only access the MongoDB server while on the machine that is running the mongod process. Are you trying to access from a remote machine by chance?


This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.