Hello,
I just experienced a bug with mongodb refusing to start on a mac M1 unexpected mongo exit code null.
Investigating, we found that the process exit signal was SIGILL, which is not handled to display a nice message to the user.
The final issue was that .meteor/packages/meteor-tool/3.2.2/mt-os.osx.arm64 was not present, instead it was the x86 version !
Removing all previous installations of Meteor and reinstalling fixed the issue.

I think this should be handled by indicating the proper information in order to provide a better DX

The issue wasn't present in earlier versions of Meteor (<=3.1), which is weird. I cannot double check why because .meteor was deleted and I didn't thought about this earlier...