CODEWITHSUNDEEP
mongodbmeteor
William
William

Reputation: 4588

Creating a new meteor.js file and get error 100, MongoDB not able to write

I'm playing with meteor.js and I get this error:

Unexpected mongo exit code 100. Restarting.
Unexpected mongo exit code 100. Restarting.
Unexpected mongo exit code 100. Restarting.
Can't start mongod

MongoDB had an unspecified uncaught exception.
Check to make sure that MongoDB is able to write to its database directory.

I'm not sure how to remedy this, especially within the context of Meteor.js I installed using curl on snow leopard mac os.

It was actually working for a while as I did a few exercises from a book I have, then it conked out with the error. Not sure what I did.

Upvotes: 8

Views: 4113

Answers (5)

throb
throb

Reputation: 11

It could be that you have an instance of mongod running already, do a 

ps -el | grep mongo

and if it's running kill it and restart

Upvotes: 1

Jorge Torres
Jorge Torres

Reputation: 269

I had this problem when I updated from 0.7 to 0.8 in my local environment, I had nothing to loose in my local database, so I fixed by: 

rm -rf .meteor/local/db

Upvotes: 7

Farzher
Farzher

Reputation: 14593

I fixed this by going to .meteor\local\db and deleting mongod.lock

Upvotes: 14

jan-glx
jan-glx

Reputation: 9536

As @Akshat said:

If you even as root cannot run meteor, it's probably a full partion & you have to clean up or just move the folder to an other partition.

If you can run meteor as root, it's probably a rights issue solvable this way:
In the meteor project folder: sudo chown -R $USER:$USER .
I recommend not to use a NTFS partition as setting the correct rights there is difficult.

Upvotes: 0

Tarang
Tarang

Reputation: 75985

As with our discussion, you just need to free up some disk space, I wish meteor would give more descriptive errors.

If you free up some space it should sort itself out

Upvotes: 6

Related Questions