Log file Viewer

[18:44:38] <tompaw> hi

[18:45:19] <tompaw> My mongod exits with status 100 providing no information about what causes the error, even when run with -vvvvvv. I made sure the file rights are correct - what else can I do to fix it?

[18:46:14] <GothAlice> http://lmgtfy.com/?q=mongod+exit+status+100 → first StackOverflow link gives the answer.

[18:46:17] <GothAlice> tompaw: ^

[18:47:00] <GothAlice> Dang, that animation used to point at Google. XD Wish I could get that pointed at DuckDuckGo, for result order consistency between users.

[18:51:21] <tompaw> as I said, it's not the file permissions. literally the first thing I said.

[18:51:43] <tompaw> there's nada in logs, output, dmesg or anywhere else, it just exits 100

[18:58:59] <GothAlice> tompaw: Running… in the foreground? (Not forking?) https://docs.mongodb.com/manual/reference/exit-codes/ says “uncaught exception”, exceptions tend to be messy, leaving stack traces in places. Trick is to find the place, and step one is to not try running whatever is crashing as a background service.

[19:13:09] <tompaw> GothAlice: ok, will keep debugging, thank you!