Meteor: unexpected mango exit code 100

Question

I just installed Meteor version 0.5.9 (45fef52095) on my CentOS server version 6.3 (Final) (Linux version 2.6.32-279.19.1.el6.i686 ([e-mail]) (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 on a Windows SBS server installed as / mnt / apshared under the apache user. I created a directory inside it called "webmeteor". I created an application called "myapp" inside the "webmeteor" directory, so my directory looks like this: / mnt / apshared / webmeteor / myapp.

I am registered as root. When I try to start the application using the meteor command, I get 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 call point was this StackOverflow question: Creating a new meteor.js file and getting a 100 error, MongoDB cannot write - however, following these suggestions (sudo'ing the meteor command and checking the disk space on which I have 70 GB free), did not work. I am quite sure that these problems are related to resolution.

I tried to recursively relay chown to root: root (as I am registered as root) and chmod to 777 recursively, but to no avail.

I ask you what should I try to get my Meteor app to start?

Thanks in advance.

Answer 1

It seems like a workaround can be found by running meteor from a directory that is not in mount. Mongodb doesn't seem to be very nice about stocks, so you need to configure rsync to periodically copy files from your resource to the directory in which the meteorite is running.

Source: Problems for running examples in Meteor

Answer 2

Using meteor reset erases all data from your database. If you are worried about this, go to the project folder.

cd /path/to/my/project

Here you need to delete the mongodb.lock file.

rm .meteor/local/db/mongodb.lock

Now you can start Meteor with the command

meteor

Answer 3

Why do I need to delete this, delete this file and folder: rm -rf .meteor/local/db/mongod.lock .meteor/local/db/journal/

thank

Answer 4

In the end, the mine was fixed by exporting LC_ALL=C An error has been detected using the debugging steps suggested in this post: https://stackoverflow.com/a/4648772

Answer 5

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

WARNING: meteor reset erases everything in your local database.

Answer 6

Here is what helped me.

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

Answer 7

Make sure you have enough free space on this section. If not, you will get this very error.

Answer 8

I run a meteor under Vagrant and stumbled upon this problem before finding this thread, I deleted the mongodb files from / var / lib / mongodb since there was a .lock, it might or might not be needed, but it's worth looking at other areas where mongodb may be in addition to the .meteor folder.

I hope this helps someone.

Answer 9

this error usually happened every time I restarted a meteorite and

 rm .meteor/local/db/mongod.lock 

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

Now i do

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

and everything returns to normal without erasing my database

Answer 10

I had the same problem on Windows 8.1 x64: "Unexpected mongo 100 exit code. Reboot." And "meteor reset" or "delete mongod.lock" does not solve the problem. To display error information when running mongod, I added the proc.stdout.on function in the run-mongo.js file:

 // Let 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 an 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 that the db directory does not exist. However, it does exist. The problem was that I have a special character in the path (accent é on my behalf). I move my meteor project folder to another place on the disk where the path is accented and it worked fine.

Hope this helps.

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

Do not forget to delete 3 lines after solving the problem or you will have many console logs every time you load the project.

Answer 11

I accidentally turned off the computer, which led to the same problem. None of the options helped me delete the .lock file or run export LC_ALL = C, etc.
I'm on Ubuntu 15.04. I started mongo with the -dbpath option pointing to myApp / .meteor / local / db, and the mongo startup logs made it clear that mongo was trying to restore the database from the / s log in the log folder. He was looking for a local.1 file that was not there.

So, I tried mongo -recovery, which further indicated that it would not work until I had a log folder.
here what i did
1. Deleted the journal folder (moved it to another location - just in case)
2. launched mongo -recovery (not 100% sure that I actually did something)
3. launched a meteorite
And it started without any glitches and guessed that I had all my data as expected.

Answer 12

the first

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

if it does not work

as you can

.meteor / local / db / meteor *

and

$ meteorite reset

and restore

.meteor / local / db / meteor *

Answer 13

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

Thanks everyone!

Answer 14

If you get a notification with something like

 Local folder has run out of space 

Try go

 cd .meteor/local/bundler-cache/ 

and delete everything in this directory. His cache is why he should not influence too much. It seems that it grows 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 still does not work, you may need to free up disk space. Do this by checking through

 free -m 

or looking at your inodes and how much space is used through

 df -h 

Answer 15

I came across this problem when I first installed node and meteorite in my new laptop (Windows 10). I have not made any changes to the default settings.

Meteor reset or deleting files from .meteor / local / db did not work for me, as I was creating new applications to run locally and the directory was empty. Therefore, I could create them, but they did not start. I also tried to create applications with old versions of meteors, also failed.

Solved in my case, changing the directory to c: \

cd c: \

Meteor create testApp

This directory also worked with existing applications that I translated from my computer. I think something is related to NFS files, I am new to all of this, so if anyone can explain more about this, I would like to know more. It is already disappointing that I cannot use all possible directories to store my applications

Answer 16

I had a similar problem. This was because the directory of my project was part of my Dropbox, and there were some conflicting files in the .meteor / local / db directory. Removing these issues resolved the issue.

Answer 17

I could repair the error by removing the local Mogo db lock.

Steps to remove db lock:

• Go to the application directory (where you have the Meteor application files)
• Delete the file $ rm.meteor / local / db / mongod.lock

Error if Meteor is still running in the background. Locked locking is not released by the running application or due to improper shutdown of the system / application and is not available for the second instance of the same application. Therefore, make sure to leave the application every time.

Answer 18

I had the same problem, I decided that it changes the ownership of the .meteor folder (where MongoDB lives)

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

Hope to help someone!

Answer 19

I was able to fix this by exporting LC_ALL, I am using Ubuntu

export LC_ALL = "en_US.UTF-8"

Answer 20

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

For Ubuntu, the / db / folder is usually located in / data, so the full path is / data / db / journal. This may be different for other operating systems.

Answer 21

I came across this problem when I first installed node and meteorite in my new laptop (Windows 10). I have not made any changes to the default settings.

Meteor reset or deleting files from .meteor / local / db did not work for me, as I was creating new applications to run locally and the directory was empty. Therefore, I could create them, but they did not start. I also tried to create applications with old versions of meteors, also failed.

Solved in my case, changing the directory to c: \

cd c:\

 meteor create testApp 

This directory also worked with existing applications that I translated from my computer. I think something is related to NFS files, I am new to all of this, so if anyone can explain more about this, I would like to know more. It is already disappointing that I cannot use all possible directories to store my applications

Answer 22

I had this problem using Meteor 1.4 on Windows 10. However, I am developing the same meteor application to install Ubuntu. The problem for me was caused by differences in how Mongo 3.2 is implemented on Windows and Ubuntu. My 64-bit Ubuntu installation uses WiredTiger. However, as stated 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, cancel the WiredTiger database from Ubuntu and then rebuild it using the old MMAPV1 mechanism. This solved the exit code 100 error.

Answer 23

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

When I install it in my workspace in / mnt / c / Workspace, it does not work every time. But, as soon as I installed it in the home directory (~), it starts for the first time. Here is the image.

Answer 24

I have the same error and I decided that I just changed the name of the compañeros directory for companions ... I know that this is the fault for beginners, but I have to say this to help people. C: \ nube \ MEGA \ cursos \ coursera \ CursowebResposivaEjemplos \ compañeros \ meteor_portfolio_website does not work C: \ nube \ MEGA \ cursos \ coursera \ CursowebResposivaEjemplos \ companeros \ meteor_portfolio_website

Answer 25

I fixed this problem by changing the file / usr / local / lib / meteor.

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

---

Answer 26

work for me: I moved the project to a different directory because I have Windows 8.1. I had a project in the desktop directory when the project was changed to C:\meteor\project