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

Question

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.

Could you check if theres a hidden `.meteor` folder in your app directory? also just see if `sudo meteor` works from your app directory? — Tarang, Jan 24 '13 at 07:44
ok if it did that with sudo, then try creating a new meteor app somewhere else and run it to see if that works? If that does, the app you made has its database/files changed around somehow — Tarang, Jan 24 '13 at 07:49
I created a whole new app on the desktop and a few other directories, same problem — William, Jan 24 '13 at 07:52
let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/23279/discussion-between-akshat-and-taoist) — Tarang, Jan 24 '13 at 07:54

score 14 · Answer 1 · answered Apr 16 '13 at 23:40

14

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

answered Apr 16 '13 at 23:40

Farzher

13,934
21
69
100

I encountered this issue after a sudden and unexpected shutdown. So, this makes sense. – jonS90 Nov 22 '13 at 20:35
+1 Exactly the solution I required. Frightened what would have happened if SO did not exist ! – Anmol Saraf Dec 18 '13 at 11:12
This is exactly what I needed, and it makes total sense in my situation (renamed the project dir while meteor was running). – T3db0t Nov 21 '14 at 17:28

score 7 · Answer 2 · answered Apr 05 '14 at 20:24

7

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

answered Apr 05 '14 at 20:24

Jorge Torres

271
3
2

Tarang · Accepted Answer · 2013-01-24T08:45:08.207

6

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

edited Jan 24 '13 at 08:45

answered Jan 24 '13 at 08:19

Tarang

75,157
39
215
276

This was happening a lot to me but freeing some space fixed the problem. (Weirdly some large db apps would work but smaller db apps wouldn't) – Matthew Wilcoxson Feb 24 '15 at 17:34

score 1 · Answer 4 · edited Mar 19 '15 at 13:38

1

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

edited Mar 19 '15 at 13:38

Christian Neverdal

5,655
6
38
93

answered Apr 08 '13 at 18:18

throb

11
1

score 0 · Answer 5 · answered Mar 14 '13 at 12:19

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.

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

5 Answers5