Looks like other users encountered this issue as well. To overcome the issue, they simply dropped this collection even though it contradicts mongodb’s documentation. See: Cannot create collection config.system.sessions because we already have an identically named collection