CODEWITHSUNDEEP
node.jsmongodbrobo3t
N15
N15

Reputation: 305

MongoDB- Error1053: the service did not respond to the start or control request in a timely fashion

When I try to connect mongdb service i am getting error: **

Windows could not start the MongoDB service on Local Computer

**

Error1053: the service did not respond to the start or control request in a timely fashion

enter image description here

Mongodb installed path: C:\MongoDB //mongod.cfg file inside the MongodB folder not in bin folder

mongod.cfg file:

systemLog:

    destination: file

    path: c:\data\log\mongod.log

storage:

    dbPath: c:\data\db***

how do I resolve this error and run a mongodb service

Upvotes: 8

Views: 14310

Answers (10)

Islam Saeed
Islam Saeed

Reputation: 1

In my case, the enabled was inside double quotations

Wrong:

#security: security: authorization: "enabled" this is wrong

Correct:

#security: security: authorization: enabled

Upvotes: 0

tedo
tedo

Reputation: 1

In my case the error happened because of this ## Enterprise-Only Options: I removed one hashtag then it worked.

Upvotes: 0

Rizwan Ali Khan
Rizwan Ali Khan

Reputation: 1

I was facing the error 1053 when I try to start mongo db server in services option, services option mongodb server just search services and go to this by scrolling down and you will find this option , just right click and click on start. in case its not working then clear browsing history cache images and files, and then click on start option of mongo db server in services, and it worked so you can also try it. You are facing the error 1053, fixing of this error is very easy, just clear your cache images and files in browsing history option of Google Chrome and you will be fine.

Upvotes: 0

Artexias
Artexias

Reputation: 335

In my case it was a missing space [ ] . Re-added it and the service started fine.

net:

port: 00000

bindIp:[ ] 000:00:000:0

Upvotes: 0

el_noobito
el_noobito

Reputation: 67

For me the same error occurred when I edited the "mongod.cfg" file and added

#security:
  authorization: enabled

to #security

but the correct syntax is the following:

#security:
# authorization: enabled

I leave it here in case someone faces the same related issue.

Upvotes: 1

Nir
Nir

Reputation: 1874

Check if mongod.cfg is corrupted, If you changed this confiuration file recently, try to undo the latest changes to see if this is the cause for the failure

I wonder why a simple error message cannot be printed in such a common failure

Upvotes: 0

JulioCT
JulioCT

Reputation: 1117

In my case the error was caused by the server running out of space in the hard disk drive.

Clearing some space solved the problem for me.

Upvotes: 1

Tedi
Tedi

Reputation: 436

In my case, this failed:

security:
  authorization: 
    enabled

And this worked fine:

security:
  authorization: enabled

Upvotes: 0

SayJeyHi
SayJeyHi

Reputation: 1841

For me , this error was about mongod.cfg file , which I add security; authorization enabled. But it should be colon after security not semicolon.

security:
  authorization: enabled

Upvotes: 4

rale
rale

Reputation: 303

I had a similar problem with MongoDB 4. In auto generated config file, there is an extra configuration, that caused the problem.

#snmp:
mp:

When i deleted "mp:", i can finally start the server.

Upvotes: 19

Related Questions