Meteor: unexpected mongo exit code 100

前端 未结 26 1120
栀梦
栀梦 2020-12-01 04:34

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)

相关标签:
26条回答
  • 2020-12-01 04:35

    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.

    0 讨论(0)
  • 2020-12-01 04:36

    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.

    0 讨论(0)
  • 2020-12-01 04:37

    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*

    0 讨论(0)
  • 2020-12-01 04:38

    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.

    0 讨论(0)
  • 2020-12-01 04:39

    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


    0 讨论(0)
  • 2020-12-01 04:40

    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.

    0 讨论(0)
提交回复
热议问题