The /health endpoint returns "status": "degraded" / "mqtt_connected": false even while the MQTT connection to the broker is active and events are being received normally. This causes Docker's healthcheck to mark the container as unhealthy after a few failed polls, despite the service functioning correctly.
- Image:
frigate-gdrive-sync:latest (built from this repo, main branch)
- Host: Fedora Linux 44, Docker Compose
- Broker: Mosquitto, reachable and confirmed to have active clients (
$SYS/broker/clients/connected returns non-zero)
curl http://localhost:8080/health
{"status": "degraded", "mqtt_connected": false, "pending": 0, "processing": 0, "done": 3, "failed": 0, "queued": 0}
docker ps | grep frigate-gdrive-sync
6e76defb05ad frigate-gdrive-sync:latest "python src/main.py" About an hour ago Up About an hour (unhealthy) 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp frigate-gdrive-sync
The
/healthendpoint returns"status": "degraded"/"mqtt_connected": falseeven while the MQTT connection to the broker is active and events are being received normally. This causes Docker's healthcheck to mark the container asunhealthyafter a few failed polls, despite the service functioning correctly.frigate-gdrive-sync:latest(built from this repo,mainbranch)$SYS/broker/clients/connectedreturns non-zero)curl http://localhost:8080/health
{"status": "degraded", "mqtt_connected": false, "pending": 0, "processing": 0, "done": 3, "failed": 0, "queued": 0}
docker ps | grep frigate-gdrive-sync
6e76defb05ad frigate-gdrive-sync:latest "python src/main.py" About an hour ago Up About an hour (unhealthy) 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp frigate-gdrive-sync