Meteor: unexpected mongo exit code 100

Question

I have just installed Meteor version 0.5.9 (45fef52095) to my CentOS release 6.3 (Final) server (Linux version 2.6.32-279.19.1.el6.i686 (mockbuild@c6b8.bsys.dev.centos.org) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Wed Dec 19 04:30:58 UTC 2012)

I have a samba share to a Windows SBS server mounted as /mnt/apshared under the apache user. I have created a directory inside this called 'webmeteor'. I have created an app called 'myapp' inside the 'webmeteor' directory, so my directory is like so: /mnt/apshared/webmeteor/myapp.

I am logged in as root. When I try to run the app using the meteor command, I am given the following error messages:

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.

My first point of call was this StackOverflow question: Creating a new meteor.js file and get error 100, MongoDB not able to write -- however, following these suggestions (sudo'ing the meteor command, and checking for disk space of which I have 70GB free) has not worked. I am quite certain that these issues are permission related.

I have tried to chown recursively to root:root (as I am logged in as root), and chmod to 777 recursively also, but to no avail.

I am asking you, what should I try next, to allow my Meteor app to start?

Thanks in advance.

This is similar to http://stackoverflow.com/questions/10103830/problems-to-run-examples-in-meteor — Prashant, Mar 25 '13 at 08:30
You might also want to try and startup the database at `./meteor/local/db` manually with mongod so you get more verbosity & description on what problem may be — Tarang, Mar 25 '13 at 11:25
After running `/usr/lib/meteor/mongodb/bin/mongod --dbpath /mnt/apshared/webmeteor/myapp/.meteor/local/db/` it certainly does give a lot of information. The error is `exception in initAndListen: 13651 Couldn't fsync directory` — Aaron Cunnington, Mar 28 '13 at 08:46
A full, feature-complete Meteor release is right around the corner for Windows! — mmmeff, Mar 16 '15 at 15:02

score 88 · Answer 1 · answered Mar 25 '13 at 08:33

88

Using meteor reset erases all the data from your database. If you're worried about this then navigate to your project folder.

cd /path/to/my/project

Here you need to erase the mongodb.lock file.

rm .meteor/local/db/mongodb.lock

Now you can run Meteor using the command,

meteor

answered Mar 25 '13 at 08:33

Prashant

1,825
1
15
18

2

Unfortunately, `meteor reset` does not work. The project resets, but it still fails to start with the same error. – Aaron Cunnington Mar 28 '13 at 08:38
Did you try erasing `mongodb.lock`? – Prashant Mar 28 '13 at 18:29
2

After removing `mongodb.lock` the problem persists. I have found that running it outside of the mounted drive works fine. I think I will just do this. – Aaron Cunnington Apr 04 '13 at 10:07
I'm seeing this issue in a mounted drive as well. I'll post back if I manage to find a solution. – mmmeff Apr 17 '13 at 03:30
1

thank you. I copied an app to another app and experienced this problem. Deleting the lock file worked. I wish the error would just say that. instead of Unexpected mongo exit code 100. Restarting. – Eric Leroy May 28 '13 at 13:51
9

For me the file was named `mongod.lock`, not `mongodb.lock`. Deleting it didn't fix the problem, but `meteor reset` did – user456584 Aug 13 '14 at 17:46
In some cases you'll also need to delete/move the journal folder. – prinzdezibel Oct 21 '15 at 15:44
10

I had to also remove the `.meteor/local/db/journal/j.*` to get it to work – nupac Dec 28 '15 at 03:18

score 43 · Answer 2 · edited Jun 11 '18 at 20:36

43

Removing this file and folder worked for me:

rm -rf .meteor/local/db/mongod.lock .meteor/local/db/journal/

edited Jun 11 '18 at 20:36

cela

2,352
3
21
43

answered Sep 13 '15 at 19:44

gabrielstuff

1,286
1
13
16

Yeah - same here. I had copied the project from Cloud 9 to my local computer and it was fixed by doing this. Thanks a lot. – Jason Cramer Jul 26 '16 at 17:34

score 16 · Answer 3 · edited May 23 '17 at 11:54

16

Mine was fixed in the end by running export LC_ALL=C. Found the error through the debugging steps suggested in this post: https://stackoverflow.com/a/15752736/1820510

edited May 23 '17 at 11:54

Community

1
1

answered Mar 31 '14 at 21:51

Xiv

8,862
3
27
30

Helped on CentOS! Thanks – Scholle Aug 19 '14 at 10:40
Helped on Ubuntu 14 on a droplet at Digital Ocean – Julio Marins Feb 24 '15 at 19:55
THIS fixed it for me! Runnung Amazon AWS Ubuntu 12.04 LTS – Thomas Feb 25 '15 at 23:20
1

What exactly does `export LC_ALL=C` do to fix the issues? – Dave Everitt Feb 28 '16 at 20:55

score 14 · Accepted Answer · edited May 23 '17 at 11:54

14

It looks like a temporary solution can be found by running meteor out of a directory that isn't in the mount. Mongodb doesn't seem to take too kindly to shares, so you'll need set up rsync to periodically copy the files from your share to the directory where meteor is running.

Source: Problems to run examples in Meteor

edited May 23 '17 at 11:54

Community

1
1

answered Apr 17 '13 at 03:40

mmmeff

1,025
9
20

Thanks for this. For now I'll look in to other options to access the files from a Windows machine. – Aaron Cunnington Apr 18 '13 at 10:28
1

I'm using a Vagrant VM on Windows, originally with no problems at all. I set up a new meteor project which now has the `Unexpected mongo exit code 100. Restarting.` error. My previous meteor projects still work fine. I followed the instructions [here](https://github.com/pixelhandler/vagrant-dev-env#readme) under **Build the meteor example todos app**. I tried using [lysnc](http://manpages.ubuntu.com/manpages/natty/man1/lsyncd.1.html) to keep the auto-reload working, but had problems so have to resort to using `touch ` each time I make a code change from Windows to trigger lysnc. – Meirion Jun 13 '13 at 11:05
would be pretty unelegant using rsync. just do a hard link from the shared folder to your meteor project. worked for me. – InsOp Sep 16 '16 at 11:31

score 11 · Answer 5 · edited May 08 '14 at 17:56

11

As suggested elsewhere, running meteor reset fixed the problem for me on OS X.

WARNING: meteor reset erases everything in your local database.

edited May 08 '14 at 17:56

colllin

9,442
9
49
65

answered Mar 03 '14 at 11:58

Jonatan Littke

5,583
3
38
40

score 5 · Answer 6 · answered Feb 14 '14 at 04:34

5

This is what helped me.

I deleted .meteor/local/db/mongod.lock
I killed mongod process. You can find this using "ps -ef | grep mongo"

answered Feb 14 '14 at 04:34

Navan

4,407
1
24
26

1

`killall mongod` did it for me..thanks for the nudge – TimDog Sep 07 '15 at 14:58
The first thing I tried was the comment above by TimDog: killall mongod. Worked like a champ; thanks TimDog. – SoEzPz Apr 12 '16 at 19:36

score 5 · Answer 7 · answered Jul 03 '14 at 21:43

5

Make sure you have enough free space on that partition. If not, you'll get this very error.

answered Jul 03 '14 at 21:43

Paul Sturm

2,118
1
18
23

That was my problem. Figured it after seeing this: http://stackoverflow.com/a/15752736/1820510. `mongod` says the following: "Please make at least 844MB available in ./journal or use --smallfiles" – agentofuser Jan 17 '15 at 12:22

score 3 · Answer 8 · edited Jun 11 '18 at 22:07

3

I'm running meteor under Vagrant and came across this issue, before finding this thread I removed my MongoDB files from /var/lib/mongodb as there was a .lock in there as well, this might or might not have been required but worth a look for other areas where MongoDB might be residing beside the .meteor folder.

edited Jun 11 '18 at 22:07

cela

2,352
3
21
43

answered Jul 13 '13 at 12:28

Robert Forbes

33
4

score 2 · Answer 9 · answered Oct 17 '14 at 15:47

this bug used to happen everytime I restarted meteor and

rm .meteor/local/db/mongod.lock

didn't work for me (i'm working on cloud9 online IDE)

I now do

rm .meteor/local/db/mongod.lock .meteor/local/db/local.*

and everything gets back to normal without erasing my database

pal · Answer 10 · 2015-11-11T16:26:23.677

I had the same issue on Windows 8.1 x64 : 'Unexpected mongo exit code 100. Restarting.'. And 'meteor reset' or 'delete mongod.lock' didn't solve it. To display the error details when launching mongod, I added a proc.stdout.on function in the run-mongo.js file :

// Let's not actually start a process if we yielded (eg during
// findMongoAndKillItDead) and we decided to stop in the middle (eg, because
// we're in multiple mode and another process exited).
if (stopped) return;

proc = spawnMongod(mongod_path, port, dbPath, replSetName);

// added this 3 lines just to debug 'Unexpected mongo exit code 100. Restarting.'
proc.stdout.on('data', function (data) {
  console.log('stdout: ' + data);
});

Then i got the explicit error :

*********************************************************************
ERROR: dbpath (C:\Users\Pierre-André\Desktop\Pal\Meteor\simple-todos\.meteor\local\db) does not exist.
Create this directory or give existing directory in --dbpath.
See http://dochub.mongodb.org/core/startingandstoppingmongo
*********************************************************************

The error indicates the db directory doesn't exist. However, it exists. The problem was that i have a special character in the path (accent é in my name). I move my meteor project folder to another place in the disk which the path is accent free, and the it worked fine.

Hope that'll help.

The run-mongo.js file is located in my pc at : C:\Users\Pierre-André\AppData\Local\.meteor\packages\meteor-tool\1.1.10\mt-os.windows.x86_32\tools\runners

Don't forget to delete the 3 lines after solving the issue, or you'll have a lot of console logs each time the project is loaded.

I was having this exact problem on Windows (`C:\Users\Fernando García\Proyectos\...`); this should be a Mongo bug... — Fer García, Mar 09 '17 at 19:26

score 1 · Answer 11 · answered Apr 12 '15 at 14:34

I had my machine shutdown accidentally that led to the same problem. None of the option helped i.e deleting .lock file or running export LC_ALL=C etc.
I am on Ubuntu 15.04. I started mongo with --dbpath option pointing to myApp/.meteor/local/db and the mongo start up logs made it clear that mongo was attempting to restore the database from the journal/s in the journal folder. It was looking for local.1 file that did not exist.

So I tried mongo --recovery that further pointed that it won't work until I have the journal folder.
here's what I did
1. Deleted the journal folder (moved it to another location - just in case)
2. ran the mongo --recovery (not 100% sure if that actually did something)
3. started meteor
And it started without any glitch and guess what I had all my data as expected

I just did 1 (delete journal) and deleted mongod.lock. This worked for me. — user1077851, Apr 21 '15 at 18:25

score 1 · Answer 12 · answered Apr 17 '15 at 06:21

1

first

$ rm .meteor/local/db/mongodb.lock

if this doesn't work

backup as you can

.meteor/local/db/meteor*

and

$ meteor reset

and restore

.meteor/local/db/meteor*

answered Apr 17 '15 at 06:21

DavidFM

193
7

score 1 · Answer 13 · answered Apr 04 '16 at 11:04

1

Solved! In my case deleting meteor/local/db/mongodb.lock and meteor reset fix the issue.

Thanks All!

answered Apr 04 '16 at 11:04

Nezir

6,727
12
54
78

2

Be careful using this command. I didnt realize it WIPED MY DATABASE! – Leon Apr 12 '16 at 22:56

Leon · Answer 14 · 2016-04-21T22:52:01.130

If you get a notification with something like

Local folder has run out of space

Try going to

cd .meteor/local/bundler-cache/

and deleting everything in that directory. Its a cache so it shouldnt affect too much. It seems to grow uncontrollably sometimes.

EDIT

Combining all the other answers try

rm -rf .meteor/local/db/mongod.lock .meteor/local/db/local.* .meteor/local/db/journal .meteor/local/bundler-cache/linker/

If this is still not working you might have to free up some space on your disk. Do so by checking via

free -m

or looking at your inodes and how much space is being used up via

df -h

score 1 · Answer 15 · edited Jun 20 '20 at 09:12

I stumbled on this issue when I first installed node and meteor in my new laptop (Windows 10). I did not made any changes in the default installations.

Meteor reset or removing files from .meteor/local/db did not work for me as I was creating new apps to run locally and the directory was empty. So, I could create them but they didn't run. Tried also to create apps with older meteor versions, failed also.

Solved in my case by changing directory to c:\

cd c:\

meteor create testApp

This directory worked also with preexisting apps that I transferred from my pc. I guess something to do with NFS filesytems, I am new in all this so if anyone can explain more about it I would love to learn more. It's already frustrating that I cannot use all possible directories to store my apps

score 0 · Answer 16 · answered Sep 17 '14 at 20:08

0

I had a similar issue. It was due to the fact that my project directory was part of my Dropbox and there was some conflicted files in the .meteor/local/db directory. Removing these solved the problem.

answered Sep 17 '14 at 20:08

Luke Clifton

81
1
8

score 0 · Answer 17 · answered Feb 13 '15 at 19:09

I could recover the error by deleting the Local Mogo db lock.

Steps to remove the db lock :

Navigate to your app directory(where you have Meteor application files)
Remove file $ rm .meteor/local/db/mongod.lock

Error occurs if Meteor Application is still running in background. Db lock is not released by the running application or due to improper system/application shutdown and unavailable for second instance of same application. So take care to quit the application every time.

score 0 · Answer 18 · answered Mar 19 '15 at 14:18

0

I had the same problem, I solved it changing ownership of .meteor folder (where MongoDB lives)

cd path-to-meteor-app
sudo chown -R youruser:yourgruop .meteor

Hope to help someone!

answered Mar 19 '15 at 14:18

Agus Arias

467
1
7
5

score 0 · Answer 19 · answered Aug 05 '15 at 13:21

0

I was able to fix it by export of LC_ALL, I am using Ubuntu

export LC_ALL="en_US.UTF-8"

answered Aug 05 '15 at 13:21

Alex Fernandez

1,892
14
17

score 0 · Answer 20 · answered Apr 06 '16 at 06:26

0

If you have installed Mongo globally, then be sure to delete all the prealloc files in the /db/journal folder.

For Ubuntu, the /db/ folder is normally located in /data so the full path is /data/db/journal. This might be different for other OS's.

answered Apr 06 '16 at 06:26

Timothy Nyota

11
3

score 0 · Answer 21 · edited May 31 '16 at 04:50

0

work for me: I moved the project to another directory, because I have Windows 8.1. I had the project in desktop directory, when change the project to C:\meteor\project

edited May 31 '16 at 04:50

Charlie

8,530
2
55
53

answered May 30 '16 at 21:55

TigerSpirt

161
1
12

score 0 · Answer 22 · answered Jun 26 '16 at 17:09

I stumbled on this issue when I first installed node and meteor in my new laptop (Windows 10). I did not made any changes in the default installations.

Meteor reset or removing files from .meteor/local/db did not work for me as I was creating new apps to run locally and the directory was empty. So, I could create them but they didn't run. Tried also to create apps with older meteor versions, failed also.

Solved in my case by changing directory to c:\

cd c:\

meteor create testApp

This directory worked also with preexisting apps that I transferred from my pc. I guess something to do with NFS filesytems, I am new in all this so if anyone can explain more about it I would love to learn more. It's already frustrating that I cannot use all possible directories to store my apps

score 0 · Answer 23 · answered Aug 31 '16 at 18:48

I had this problem using Meteor 1.4 on Windows 10. However, I am developing the the same meteor application on an Ubuntu install. The problem for me was caused by differences in the way Mongo 3.2 is implemented on Windows and Ubuntu. My 64 bit Ubuntu install uses WiredTiger. However as it says in the Meteor documentation:

If you are using Windows or 32bit Linux, you can update your development
database to 3.2, however it will continue to use the MMAPv1 storage 
engine, as the 32bit MongoDB binary does not support WiredTiger.

Using meteor reset on Windows blew away the WiredTiger format database from Ubuntu, and then rebuilt it using the old MMAPV1 engine. This solved the exit code 100 error.

score 0 · Answer 24 · answered Oct 10 '17 at 12:52

0

For those using bash on Windows (Windows Subsystem for Linux/WSL), I found that creating the meteor app outside of the /mnt directory solves the problem.

When I install it in my workspace in /mnt/c/Workspace it failed everytime. But, once I install it in the home directory (~), it runs the first time. Here's the image.

answered Oct 10 '17 at 12:52

Yoshua Elmaryono

1

How did you use your drive in Windows then? – insidesin Jul 15 '18 at 09:23
@insidesin I've given up on making it work on WSL. It's more time efficient to just install my whole stack in Windows directly (meteor, mongodb, etc.) – Yoshua Elmaryono Jul 16 '18 at 09:47
Did you symlink the files you want to edit in Windows? How did that fail? I might be going down the same path as you :( – insidesin Jul 17 '18 at 00:48

score -1 · Answer 25 · answered May 07 '16 at 20:58

I have the same error and I solved it just changing the name of the directory compañeros for companeros ... I know it is an fault for beginners but I have to tell this to help people whit. C:\nube\MEGA\cursos\coursera\CursowebResposivaEjemplos\compañeros\meteor_portfolio_website doesn't work C:\nube\MEGA\cursos\coursera\CursowebResposivaEjemplos\companeros\meteor_portfolio_website work correctly.

score -1 · Answer 26 · answered May 12 '16 at 02:32

-1

I fixed this issue by modifying the /usr/local/lib/meteor file.

Adding "export LC_ALL=C LANG=C" to this bash script

#!/usr/bin/env bash

export LC_ALL=C LANG=C

BUNDLE_VERSION=0.5.16

answered May 12 '16 at 02:32

N3RDPWR

1

Meteor: unexpected mongo exit code 100

26 Answers26

Linked