Skip to content

fix(prod): rename gunicorn config so auto-discovery loads timeout=120#24

Merged
paritoshtripathi935 merged 1 commit into
mainfrom
fix/gunicorn-conf-discovery
May 10, 2026
Merged

fix(prod): rename gunicorn config so auto-discovery loads timeout=120#24
paritoshtripathi935 merged 1 commit into
mainfrom
fix/gunicorn-conf-discovery

Conversation

@paritoshtripathi935
Copy link
Copy Markdown
Owner

Summary

Render's start command (gunicorn -w 4 -k uvicorn.workers.UvicornWorker app.main:app) does not pass -c, so the only way the worker timeout is loaded is via gunicorn's config auto-discovery. Auto-discovery looks for gunicorn.conf.py (with a dot), not gunicorn_config.py (with an underscore) — so the timeout = 120 setting added in #20 was effectively a no-op and /answer continued to SIGKILL at the default 30s on long-form gpt-oss-120b / qwq-32b generations.

Rename to gunicorn.conf.py so discovery picks it up on Render's next deploy. No dashboard change needed.

Test plan

  • git mv preserves file content (rename detected as 100%)
  • Render redeploys on merge
  • First post-deploy /answer request to a reasoning model completes past 30s without WORKER TIMEOUT

Render's start command does not pass -c, so gunicorn auto-discovery is the only way the config file is loaded. Auto-discovery only matches gunicorn.conf.py (with a dot), not gunicorn_config.py — so the timeout=120 setting added in #20 was a no-op and /answer continued to SIGKILL at the default 30s. Rename the file to make discovery actually find it.
@netlify
Copy link
Copy Markdown

netlify Bot commented May 10, 2026

Deploy Preview for mini-perplexity canceled.

Name Link
🔨 Latest commit bd7aa7b
🔍 Latest deploy log https://app.netlify.com/projects/mini-perplexity/deploys/6a00ad094192d10008fc37bb

@paritoshtripathi935 paritoshtripathi935 merged commit 29f77ed into main May 10, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant