Celery celery worker -q --quiet seems not working with

The Fix

pip install celery==5.1.0b1

Based on closed celery/celery issue #6517 · PR/commit linked

Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.

Jump to Verify Open PR/Commit

@@ -325,6 +325,7 @@ def worker(ctx, hostname=None, pool_cls=None, app=None, uid=None, gid=None,
             statedb=node_format(statedb, hostname),
             no_color=ctx.obj.no_color,
+            quiet=ctx.obj.quiet,
             **kwargs)
         worker.start()

repro.py

worker = app.Worker(
        hostname=hostname, pool_cls=pool_cls, loglevel=loglevel,
        logfile=logfile,  # node format handled by celery.app.log.setup
        pidfile=node_format(pidfile, hostname),
        statedb=node_format(statedb, hostname),
        no_color=ctx.obj.no_color,
        quiet=ctx.obj.quiet,
        **kwargs)

verify

Re-run the minimal reproduction on your broken version, then apply the fix and re-run.

fix.md

Option A — Upgrade to fixed release\npip install celery==5.1.0b1\nWhen NOT to use: Do not use this fix if the logging behavior is required for debugging.\n\n

Why This Fix Works in Production

Trigger: Celery worker produces logs despite the --quiet flag being set, leading to unwanted output.
Mechanism: The --quiet flag was not passed to the worker, causing logs to be produced
Why the fix works: --quiet flag now actually makes celery avoid producing logs. (first fixed release: 5.1.0b1).

Production impact:

If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

The --quiet flag was not passed to the worker, causing logs to be produced
Production symptom (often without a traceback): Celery worker produces logs despite the --quiet flag being set, leading to unwanted output.

Proof / Evidence

GitHub issue: #6517
Fix PR: https://github.com/celery/celery/pull/6599
First fixed release: 5.1.0b1
Reproduced locally: No (not executed)
Last verified: 2026-02-09
Confidence: 0.95
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.58

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“> I've recently tried this with the latest celery version (5.0.5), and the issue remains. > > The reason seems to be that in celery.bin.worker.worker…”

@auvipy · 2021-01-17 · source

“I've recently tried this with the latest celery version (5.0.5), and the issue remains. The reason seems to be that in celery.bin.worker.worker the ctx.obj.quiet option…”

@strokirk · 2021-01-17 · source

“would you mind checking this https://github.com/celery/celery/pull/6599?”

@auvipy · 2021-01-17 · source

Failure Signature (Search String)

Celery worker produces logs despite the --quiet flag being set, leading to unwanted output.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
Celery worker produces logs despite the --quiet flag being set, leading to unwanted output.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
Celery worker produces logs despite the --quiet flag being set, leading to unwanted output.

Minimal Reproduction

repro.py

worker = app.Worker(
        hostname=hostname, pool_cls=pool_cls, loglevel=loglevel,
        logfile=logfile,  # node format handled by celery.app.log.setup
        pidfile=node_format(pidfile, hostname),
        statedb=node_format(statedb, hostname),
        no_color=ctx.obj.no_color,
        quiet=ctx.obj.quiet,
        **kwargs)

What Broke

Celery worker produces logs despite the --quiet flag being set, leading to unwanted output.

Why It Broke

The --quiet flag was not passed to the worker, causing logs to be produced

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install celery==5.1.0b1

When NOT to use: Do not use this fix if the logging behavior is required for debugging.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

Fix reference: https://github.com/celery/celery/pull/6599

First fixed release: 5.1.0b1

Last verified: 2026-02-09. Validate in your environment.

When NOT to Use This Fix

Do not use this fix if the logging behavior is required for debugging.

Verify Fix

verify

Re-run the minimal reproduction on your broken version, then apply the fix and re-run.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
Pin production dependencies and upgrade only with a reproducible test that hits the failing path.

Version Compatibility Table

Version	Status
5.1.0b1	Fixed

Related Issues

No related fixes found.

Cluster: celery:configuration-error Celery hub Celery best practices All hubs All clusters

Related clusters: Data consistency Duplicates Duplicate processing

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.

Celery celery worker -q --quiet seems not working with 4.4.7 (Fix)