Context

When you're running Console, it must become "healthy" at some point, otherwise it means that something wrong is happening.

It might stay unhealthy because of multiple reasons:

• A wrong configuration
• A wrong health check configured
• Not enough resources

Wrong configuration

If the configuration of your Console is wrong, it might stop working, or stay unhealthy. In this case, we'd first recommend you check that your connection to your database is well configured, and that there is no typo anywhere.

You can refer to our variables list.

Wrong health check

By default, Console has an internal health check configured. It will check its own readiness, and the container will be considered healthy as soon as it's ready.

If you want, you can override this health check, but you're exposing yourself to some risks.

For example, if the health check endpoint isn't correct, Console will stay unhealthy.

Same, if you're Console is exposed in HTTPS, but you're configuring an health check on HTTP, you'll get some errors:

WARN o.h.blaze.pipeline.stages.SSLStage - SSLException in SSL handshake
  javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
  at java.base/sun.security.ssl.SSLEngineInputRecord.bytesInCompletePacket(SSLEngineInputRecord.java:145)
  at java.base/sun.security.ssl.SSLEngineInputRecord.bytesInCompletePacket(SSLEngineInputRecord.java:64)
  ...
ERROR o.h.b.s.Http1ServerStage$$anon$3 - Fatal Error: Error in requestLoop()
  javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
  at java.base/sun.security.ssl.SSLEngineInputRecord.bytesInCompletePacket(SSLEngineInputRecord.java:145)
  at java.base/sun.security.ssl.SSLEngineInputRecord.bytesInCompletePacket(SSLEngineInputRecord.java:64)
  ...
ERROR o.h.blaze.channel.nio1.NIO1HeadStage - Abnormal NIO1HeadStage termination
  javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
  at java.base/sun.security.ssl.SSLEngineInputRecord.bytesInCompletePacket(SSLEngineInputRecord.java:145)
  at java.base/sun.security.ssl.SSLEngineInputRecord.bytesInCompletePacket(SSLEngineInputRecord.java:64)
  ...

Not enough resources

If you don't provide enough memory to your container, it might die because of an OOM (Out Of Memory), or simply not start properly:

Error: Not enough RAM available, expected at least 2000000000 bytes, found 1073741824 bytes

To prevent that, make sure you follow our system requirements.