Deploy Logs frozen at "Starting Container" — Python app stdout/stderr not captured (mexc service)
gablemethod-lgtm
HOBBYOP

2 months ago

Service: mexc (197f1fc6-040b-44ae-b1f9-ddc2f97f0a71)

Project: acceptable-liberation (6c91d24d-5c0d-454d-b322-326f36a39ee6)

Environment: production (98e16a72-47e1-4e66-baac-1bbc45678094)

Deployment ID: 6cb7c18a-96ea-4b5a-a5f6-ef5c5044dad9

Region: sfo

Deploy Logs only show "Starting Container" (2026-08-19T11:21:07.823Z). Container is online

and healthy, but zero application stdout/stderr appears — even with a trivial test script

(python -c "print('hello', flush=True)") and PYTHONUNBUFFERED=1 set. Tried across two separate

redeploys, waited 90+ seconds each. Restarting did not fix it.

Build is clean (Railpack 0.37.0, Python 3.13.14), no app crashes, metrics normal.

Not an application-code issue — ruled out with the trivial script test above.

Request: Investigate log capture/shipping pipeline — possibly a Railpack v0.37.0 or sfo-region

log-agent issue.

$10 Bounty

1 Replies

Railway
BOT

2 months ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 2 months ago


What's your start command?


Welcome!

Sign in to your Railway account to join the conversation.

Loading...