"Exited with code: 1" after 1.8 upgrade

#1

I’ve updated from 1.6.0.1 to 1.8 and am still getting the dreaded “Exited with code: 1” error. This has been a perpetual problem with every update since 1.6.1. I haven’t been able to upgrade at all, but thought 1.8 would be different due to the relaxed version constraints (especially with coffeescript). I added the “!” to the coffeescript and npm-mongo packages.

I’ve got the following in a startup file, but it does nothing:

process.on('uncaughtException', err => {
    console.log(err.message);
});

process.on('unhandledRejection', (reason, p) => {
    console.log('Unhandled Rejection at:', p, 'reason:', reason);
});

Any way to figure out where this error is coming from?

#2

Have you tried a meteor reset?

Usually error codes after upgrade come from Mongo, because the underlying db needs upgrading. A reset forces Mongo to create a fresh db that it will be compatible with

If you don’t want to reset, you can upgrade the local database, but it needs to be done for each major version at a time.
Because Meteor 1.6.0.1 uses Mongo 3.2, that means upgrading three times: 3.2 -> 3.4 -> 3.6 -> 4.0