Meteor: Unexpected exit code for mango 100. Restart. Do not start the mongo server

I had to force restart my mac and now get the following error when trying to run one specific meteor application on localhost.

Unexpected exit code mongo 100. Restart. Do not start Mongo server.MongoDB has an unspecified uncaught exception. This may be because MongoDB cannot write to the local database. Make sure you have write permissions in .meteor / local. MongoDB does not support file systems, such as NFS, which do not allow file locking.

Everything worked fine and no major changes were made until an error occurred. Look at other topics related to the issue, but so far none of the answers I found have fixed this. The main suggestion seems to be to delete the mongod.lock file and restart the application as usual, but this did not work. I also checked and verified that I have read / write permissions for the file.

Another suggestion uses meteor reset , but I cannot use it because I need the data currently in db applications, and reset will destroy it.

Other things I tried without success. Basically everything in this thread. Problems running examples in Meteor .

also tried just running sudo meteor as one of the last answers suggested in the section above.

I ran mongod directly from the meteorite installation directory on my system and ran mongodb on port 27017 without any problems.

In desperation, I also tried to create a new application and import the files / folders from the broken into it. This is normal, but I cannot register, which suggests that the associated mongodb not connected to a new instance of the application.

Is there a way to stop all the specific processes associated with the meteor from the terminal to make sure that the hidden process is not causing a problem? I seem to remember that I had a similar problem with postgres before it was solved this way. But at the moment I have no ideas.

Most of the previous threads on this issue are quite old, so if someone had recently encountered this problem and fixed it somehow other than those suggested, I would be very grateful for the help in starting my application again . If a few tips on how to dump data / restore a new application without having to start a meteorite application is very appreciated.

Sorry for the long question and thanks in advance!

EDIT: This question has been flagged as a possible duplicate and is being addressed here Meteor: unexpected mongo 100 exit code . However, none of the answers presented there solved this for me. A little additional trial version and a combination of several previous answers has been fixed for my case. I will post my answer below.

+7
mongodb meteor
Jul 24 '15 at 18:42
source share
1 answer

These are the steps that solved my instance of this problem.

  • Delete .meteor/local/db/mongod.lock
  • Delete .meteor/local/db/journal/j.* (Note: I just moved it just in case !; D)
  • sudo meteor

sudo might not be needed, but that was the only way back to the application for me. Hope this allows someone some time to come back and work.

+33
Jul 26 '15 at 23:51
source share



All Articles