The order of initializing the global storage engine for mongod v3.6 could cause the process to crash if the attempt to setup TransportLayerManager fails (here). This is an issue due to this assumption for creating a new opCtx, that a global storage engine is available.

The shutdown code, in particular here, may attempt to create a new opCtx, which would result in violating the invariant.

This ticket should address the issue by making sure the process exits cleanly if the network setup fails.