Bad Mongo authentication is silently swallowed by xAPI service (Open Source)

[Peterburnett]

What version were you using?

Open source

What steps can we follow to reproduce the behaviour?

in the xAPI/.env file, set the mongo connection string to a string that fails authentication, such as an incorrect set of credentials, but IS a valid mongo server to use.

What is the actual behaviour?

This error is silently swallowed when the xAPI service starts. The pm2 status for the application shows it running, but the port for xAPI is never bound, and anything attempting to route to the service fails.

What is the expected behavior?

A message about failed authentication is dumped to the application logs.

Is there any additional information that will help us replicate/understand the problem?