Opening this issue to track silent failure of TLS configuration in anchore-engine services due to things like typos in cert or key paths.

Expected behavior is for the service to fail to start if TLS cannot be configured as specified in the config.yaml and clear errors should be visible in the logs for things like files not found.

The current behavior is to swallow the errors and try to initialize with no cert or key (if both not found) which then starts the service without the expected tls configuration in place.

This is related to #53 , just the error reporting part.