When Gateway starts up, the container performs multiple initialization and validation checks to ensure that the container can successfully start. These checks include verifying the configuration environment, authentication mechanisms, and file system permissions. If any of these checks fail, the container exits automatically to prevent invalid or inconsistent running states.
Example exit scenarios
The following section outlines example scenarios where the Gateway container might not successfully start up:
Missing authentication mechanism
- Address Manager
- Micetro
- Standalone
Checking logs when Gateway fails to start up
If Gateway fails to start up, you can view the logs using the docker logs
<gateway_container_name> command to view errors that have occurred
and prevented Gateway from successfully starting. The docker logs
<gateway_container_name> command displays all logs written to the
container's STDOUT and STDERR.
docker logs command displays a message similar to the
following:ERROR: Missing configuration for authentication mechanism. Refer to documentation on configuring to use BlueCat Address Manager, Micetro or Standalone Gateway authentication.
INFO: Generated TLS certificate.
INFO: Start-up checks completed with errors.If your Gateway container successfully started and Gateway is running, logs are written to the relevant log files unless the output location has been modified.