Mongo exit code 100 in Meteor 0.7.1.2

Question

I had a perfectly functioning Meteor app. Today, I've updated it from Meteor 0.7.1.1 to 0.7.1.2. Upon starting the app, I get

Unexpected mongo exit code 100. Restarting.
Can't start Mongo server.
MongoDB had an unspecified uncaught exception.

Downgrading to 0.7.1.1 didn't help, nor running mrt reset, removing mongod.lock file and killing mongo process, as suggested here, here and here. Is there something that 0.7.1.2 could have broken? What more can I do to fix the issue?

score 0 · Answer 1 · answered Feb 28 '14 at 08:32

0

Apparently, the order of those commands do matter. First kill mongo, then run mrt reset. At least that's what worked for me this time.

answered Feb 28 '14 at 08:32

Hubert OG

19,314
7
45
73

Also, after updating to 0.7.1.2 again the app works fine. So this was probably just a random wandering bug. – Hubert OG Feb 28 '14 at 08:33
1

Was you running low on disk space? – 1321941 Feb 28 '14 at 10:14
I encountered this too and `ps aux | grep mongo` showed a mongo instance still running. After killing that meteor was able to start normally. – user728291 Mar 01 '14 at 07:45

Mongo exit code 100 in Meteor 0.7.1.2

1 Answers1