starred/godoxy-yusing
1
0
Fork 0
mirror of https://github.com/yusing/godoxy.git synced 2026-01-11 22:30:47 +01:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

Idlewatcher doesn't work with python healthcheck #119

New Issue
Closed
opened 2025-12-29 14:25:19 +01:00 by adam · 2 comments
adam commented 2025-12-29 14:25:19 +01:00
Owner
Copy Link

Originally created by @mrg358 on GitHub (Nov 8, 2025).

Coqui Docker Compose

services:
  coqui-czech:
    container_name: coqui-czech
    image: ghcr.io/coqui-ai/tts-cpu
    restart: unless-stopped
    entrypoint:
      - "/bin/bash"
      - "-c"
    command: 
      - sh -c 'tts-server --port 5002 --model_name tts_models/cs/cv/vits'
    #ports:
    #  - 5102:5002
    volumes: 
      - models:/root/.local/share/tts
      - output:/root/tts-output
    environment:
      - TZ=Europe/Prague
    labels:
      proxy.idle_timeout: 5m
    healthcheck:
      test: ["CMD", "python3", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:5002/')"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 60s

Godoxy Logs

godoxy-proxy     | 11-08 12:43 INF awaken container=coqui-czech deps=[] idle_timeout="5 minutes" kind=docker url=http://172.27.0.2:0
godoxy-proxy     | 11-08 12:43 INF idlewatcher stopped container=coqui-czech deps=[] idle_timeout="5 minutes" kind=docker url=http://172.27.0.2:0
godoxy-proxy     | 11-08 12:43 INF idlewatcher started container=coqui-czech deps=[] idle_timeout="5 minutes" kind=docker url=http://:0
godoxy-proxy     | 11-08 12:54 ERR container stop with method "stop" failed error="watcher \"coqui-czech\" error: timeout" container=coqui-czech deps=[] idle_timeout="5 minutes" kind=docker url=http://172.27.0.3:0

Coqui container up and running healthy

coqui-czech   |  * Running on all addresses (::)
coqui-czech   |  * Running on http://[::1]:5002
coqui-czech   |  * Running on http://[::1]:5002
coqui-czech   | INFO:werkzeug:Press CTRL+C to quit
coqui-czech   | INFO:werkzeug:::1 - - [08/Nov/2025 12:44:05] "GET / HTTP/1.1" 200 -
coqui-czech   | INFO:werkzeug:::1 - - [08/Nov/2025 12:44:35] "GET / HTTP/1.1" 200 -
coqui-czech   | INFO:werkzeug:::1 - - [08/Nov/2025 12:45:06] "GET / HTTP/1.1" 200 -
coqui-czech   | INFO:werkzeug:::1 - - [08/Nov/2025 12:45:36] "GET / HTTP/1.1" 200 -
coqui-czech   | INFO:werkzeug:::1 - - [08/Nov/2025 12:46:06] "GET / HTTP/1.1" 200 -

Coqui frontend stuck in waiting mode

12:53:22.023coqui-czech started successfully
12:53:22.023Waiting for coqui-czech to be ready...
Originally created by @mrg358 on GitHub (Nov 8, 2025). Coqui Docker Compose ``` services: coqui-czech: container_name: coqui-czech image: ghcr.io/coqui-ai/tts-cpu restart: unless-stopped entrypoint: - "/bin/bash" - "-c" command: - sh -c 'tts-server --port 5002 --model_name tts_models/cs/cv/vits' #ports: # - 5102:5002 volumes: - models:/root/.local/share/tts - output:/root/tts-output environment: - TZ=Europe/Prague labels: proxy.idle_timeout: 5m healthcheck: test: ["CMD", "python3", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:5002/')"] interval: 30s timeout: 10s retries: 3 start_period: 60s ``` Godoxy Logs ``` godoxy-proxy | 11-08 12:43 INF awaken container=coqui-czech deps=[] idle_timeout="5 minutes" kind=docker url=http://172.27.0.2:0 godoxy-proxy | 11-08 12:43 INF idlewatcher stopped container=coqui-czech deps=[] idle_timeout="5 minutes" kind=docker url=http://172.27.0.2:0 godoxy-proxy | 11-08 12:43 INF idlewatcher started container=coqui-czech deps=[] idle_timeout="5 minutes" kind=docker url=http://:0 godoxy-proxy | 11-08 12:54 ERR container stop with method "stop" failed error="watcher \"coqui-czech\" error: timeout" container=coqui-czech deps=[] idle_timeout="5 minutes" kind=docker url=http://172.27.0.3:0 ``` Coqui container up and running healthy ``` coqui-czech | * Running on all addresses (::) coqui-czech | * Running on http://[::1]:5002 coqui-czech | * Running on http://[::1]:5002 coqui-czech | INFO:werkzeug:Press CTRL+C to quit coqui-czech | INFO:werkzeug:::1 - - [08/Nov/2025 12:44:05] "GET / HTTP/1.1" 200 - coqui-czech | INFO:werkzeug:::1 - - [08/Nov/2025 12:44:35] "GET / HTTP/1.1" 200 - coqui-czech | INFO:werkzeug:::1 - - [08/Nov/2025 12:45:06] "GET / HTTP/1.1" 200 - coqui-czech | INFO:werkzeug:::1 - - [08/Nov/2025 12:45:36] "GET / HTTP/1.1" 200 - coqui-czech | INFO:werkzeug:::1 - - [08/Nov/2025 12:46:06] "GET / HTTP/1.1" 200 - ``` Coqui frontend stuck in waiting mode ``` 12:53:22.023coqui-czech started successfully 12:53:22.023Waiting for coqui-czech to be ready... ```
adam added the bug label 2025-12-29 14:25:19 +01:00
adam closed this issue 2025-12-29 14:25:20 +01:00
adam commented 2025-12-29 14:25:20 +01:00
Author
Owner
Copy Link

@yusing commented on GitHub (Nov 8, 2025):

This image ghcr.io/coqui-ai/tts-cpu does not have EXPOSE defined in Dockerfile (which means no ports are exposed by default), so godoxy does not know which port to use.

Add proxy.#1.port: 5002 or

expose:
  - 5002
@yusing commented on GitHub (Nov 8, 2025): This image `ghcr.io/coqui-ai/tts-cpu` does not have `EXPOSE` defined in Dockerfile (which means no ports are exposed by default), so godoxy does not know which port to use. Add `proxy.#1.port: 5002` or ```yaml expose: - 5002 ```
adam commented 2025-12-29 14:25:21 +01:00
Author
Owner
Copy Link

@mrg358 commented on GitHub (Nov 8, 2025):

Oh, I see. That explains my troubles with idlewatcher.
Problem solved, thanks @yusing 👍

@mrg358 commented on GitHub (Nov 8, 2025): Oh, I see. That explains my troubles with idlewatcher. Problem solved, thanks @yusing 👍
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pull-request
Mirrored from GitHub Pull Request
 wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/godoxy-yusing#119
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?