Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

MongoDB cannot start server: The default storage engine 'wiredTiger' is not available with this build of mongod

Tags:

mongodb

MongoDB server failing to start with the following error:

2015-12-13T00:49:12.191+0600 I CONTROL [initandlisten] options: {}
2015-12-13T00:49:12.195+0600 I STORAGE [initandlisten] exception in

initAndListen: 28663 Cannot start server. The default storage engine 'wiredTiger' is not available with this build of mongod. Please specify a different storage engine explicitly, e.g. --storageEngine=mmapv1., terminating 2015-12-13T00:49:12.195+0600 I CONTROL [initandlisten] dbexit: rc: 100

like image 228
Rahul Baruri Avatar asked Dec 12 '15 19:12

Rahul Baruri


3 Answers

Well... There appears to be a version conflict: you are probably running a 32bit version of Mongo. Just do as they say and actually use the other default storage engine:

Write the command as follows in your Mongo/bin directory:

mongod --storageEngine=mmapv1 --dbpath [your-path] 

Should solve the problem. I guess you don't quite mind about using the good old mmapv1 instead of wiredTiger do you?

like image 165
Romain Delyfer Avatar answered Sep 26 '22 10:09

Romain Delyfer


Look carefully error, an error message is very clear that the causes and solutions for the problems, as long as we later in the installation MonogoDB command to add a parameter --storageEngine = mmapv1, will wiredTiger engine switched mmapv1 engine, you can successfully install.

So your complete command will be as follows:

mongod --dbpath MongoDb_Location_In_Your_HDD\data --storageEngine=mmapv1

Note: MongoDb_Location_In_Your_HDD means the location where you put your MongoDb e.g.- D:\mongodb

like image 24
Mojammel Haque Avatar answered Sep 25 '22 10:09

Mojammel Haque


I also come across this issues when i installed mongodb 32 bit msi for windows server.

Reason could be:

I think for mongodb 32 bit the database engine wont take automatically we need to explicitly give them while configuring the db path

The fix is below:

Run command prompt as administrator

d:\mongodb>mongod --dbpath "data" --storageEngine "mmapv1"

After adding the above bold code the issue resolved.

Thanks Dev

like image 25
Devanathan.S Avatar answered Sep 22 '22 10:09

Devanathan.S