Expected Behavior

When an internal condition means Gotenberg cannot operate, the healthcheck should fail.

Current Behavior

When an internal condition appears to be failing, the healthcheck returns healthy.

Possible Solution

When an internal condition is failing, the healthcheck should also fail.

Steps to Reproduce (for bugs)

I'm afraid I do not know how to cause a reproduction for this issue.

Logs (LOG_LEVEL="DEBUG")

{
  "level": "error",
  "msg": "Get http://localhost:9222/json/version: dial tcp 127.0.0.1:9222: connect: connection refused",
  "op": "xhttp.htmlHandler: xhttp.convertSync: printer.chromePrinter.Print",
  "time": "2020-02-27T11:16:27Z",
  "trace": "9vALcycdMza3LSm5YGhQSd6CNwXosT56"
}

Context

As mentioned above I'm afraid I don't have a reproduction for how Gotenberg gets into this state, but it appears that something has gone wrong internally which then causes all subsequent requests to fail with a 500 error. But, the healthcheck continues to return ok so our service is not alerted on or restarted.

Any tips or hints greatly appreciated.

Your Environment

We're running Gotenberg 6.1.2 in AWS ECS.