DEV Community: Hirakjyoti Das

The Missing 65-Byte File That Broke My Production Celery Setup

Hirakjyoti Das — Tue, 07 Jul 2026 02:51:08 +0000

There are bugs that teach you a new algorithm.

There are bugs that teach you a new framework.

And then there are bugs that make you question everything you know about software.

This was one of those bugs.

⸻

“It works in staging…”

I had just finished implementing email notifications in my Django application.

Whenever a new user signed up, a Celery task would send a notification email to the admin.

The code was straightforward.

@receiver(post_save, sender=get_user_model())
def notify_admin_on_new_user(sender, instance, created, **kwargs):
if not created:
return
send_new_user_notification_task.delay(
user_id=instance.id,
username=instance.username,
email=instance.email,
name=instance.name,
)

The task itself simply called Django’s send_mail().

Nothing fancy.

⸻

Everything worked locally

Local development?

Perfect.

The Celery worker received the task immediately.

Emails were delivered.

No errors.

⸻

So I deployed it…

Production came online.

I created a new user from Django Admin.

Instead of a success page, I got:

500 Internal Server Error

My first thought:

“Redis is down.”

It wasn’t.

⸻

The traceback

The logs were terrifying.

The first thing I saw was this:

AttributeError:
'ChannelPromise' object has no attribute 'value'

That looked like an internal Celery or Kombu bug.

Scrolling further…

kombu.exceptions.OperationalError:
[Errno 111] Connection refused

Even stranger.

Further down…

URI: amqp://guest:**@localhost:5672//

Wait…

RabbitMQ?

I wasn’t even using RabbitMQ.

I was using Redis.

Why on earth was Celery trying to connect to localhost:5672?

⸻

Maybe Redis?

I checked Redis.

Healthy.

I could connect to it.

The Celery worker itself was running perfectly.

Even manual tasks executed successfully.

This made no sense.

The worker clearly knew how to talk to Redis.

But Django apparently didn’t.

⸻

Maybe Docker?

I rebuilt every image.

No luck.

I deleted old images.

Rebuilt without cache.

Still broken.

⸻

Maybe uWSGI?

I noticed uWSGI was running with multiple workers.

Maybe Celery didn’t like that.

I reduced it to a single worker.

Still broken.

⸻

Maybe Celery 5.6?

Maybe I had discovered a regression.

I checked package versions.

Everything looked fine.

I seriously considered downgrading Celery.

Thankfully, I didn’t.

⸻

The weirdest part

I created an entirely separate staging deployment.

Same repository.

Same Dockerfile.

Same compose file.

Same environment variables.

Same Redis image.

Same PostgreSQL image.

Everything worked.

At this point the bug became even more frustrating.

How can the same code behave differently?

⸻

The clue

Instead of looking at logs, I started comparing behavior.

Inside the Django shell I ran:

from celery import current_app
print(current_app.conf.broker_url)

Staging

redis://redis:6379/0

Perfect.

Production

None

Now I finally had a direction.

If the broker URL is None, Celery falls back to its default broker:

amqp://guest@localhost:5672//

Exactly what the logs showed.

The traceback wasn’t the real problem.

It was only a symptom.

⸻

Comparing the projects

I started comparing files between staging and production.

Eventually one command stood out.

diff config/init.py

Production replied:

No such file or directory

The file simply didn’t exist.

A file so small that I had never even thought about it.

⸻

The fix

I recreated the file.

from .celery import app as celery_app
all = ("celery_app",)

That’s it.

Two lines.

Sixty-five bytes.

⸻

Suddenly everything worked

I restarted the containers.

Back into the Django shell.

from celery import current_app
print(current_app.conf.broker_url)

This time:

redis://redis:6379/0

I created another user.

No 500 error.

Celery received the task.

The email was sent.

Everything worked exactly as expected.

⸻

What was actually happening?

Celery has the idea of a default application.

If your Django project doesn’t expose your configured Celery app, shared_task uses Celery’s default app.

That default app has no broker configured.

So internally Celery assumes:

amqp://guest@localhost:5672//

Every .delay() call tries to publish a message through RabbitMQ.

Since RabbitMQ isn’t running, Kombu raises:

Connection refused

The scary ChannelPromise traceback is merely an internal consequence of that failed connection.

The missing init.py wasn’t adding functionality.

It was registering my configured Celery application as the project’s default application.

Without it, Django and Celery were speaking different languages.

⸻

What I learned

This bug taught me several lessons.

First, don’t trust the first exception you see.

The ChannelPromise error looked like the root cause.

It wasn’t.

It was only the messenger.

Second, compare a working system with a broken one.

The breakthrough wasn’t reading another stack trace.

It was noticing this single difference:

Working:

current_app.conf.broker_url

redis://redis:6379/0

Broken:

current_app.conf.broker_url

None

That single observation eliminated hours of guessing.

Third, tiny files can have enormous responsibilities.

A two-line file determined whether my application used Redis correctly or attempted to connect to a RabbitMQ server that didn’t even exist.

⸻

The moral

Sometimes the bug isn’t hidden inside a thousand lines of business logic.

Sometimes it isn’t Docker.

Sometimes it isn’t Redis.

Sometimes it isn’t Celery.

Sometimes the difference between a perfectly working production system and hours of frustration is a tiny file you never noticed because every tutorial quietly included it from the very beginning.

Those are the bugs you’ll never forget.

বিট, বাইনেৰী আৰু কম্পিউটাৰে কেনেকৈ সংখ্যা বুজে?

Hirakjyoti Das — Tue, 23 Jun 2026 09:26:47 +0000

যদি আপুনি অপাৰেটিং চিষ্টেম, CPU, মেম’ৰী, বা নিজৰ কম্পিউটাৰ বনোৱাৰ সপোন দেখে, তেন্তে এই লেখাটো আপোনাৰ বাবে।

এই লেখাটোত আমি একেবাৰে আৰম্ভণিৰ পৰা শিকিম:

Decimal Number System কি?
Binary Number System কি?
Decimal ↔ Binary Conversion
Binary Addition
Carry কি?
Negative Number কেনেকৈ সংৰক্ষণ কৰা হয়?
Two’s Complement কি?
CPU-এ কিয় এই পদ্ধতি ব্যৱহাৰ কৰে?

⸻

মানুহে সংখ্যা কেনেকৈ লিখে?

আমি দৈনন্দিন জীৱনত ব্যৱহাৰ কৰা সংখ্যা পদ্ধতিটোক Decimal System বোলা হয়।

ইয়াত ১০টা digit আছে:

0 1 2 3 4 5 6 7 8 9

উদাহৰণ:

6083

এইটো আচলতে হৈছে:

6 × 1000
0 × 100
8 × 10
3 × 1

অৰ্থাৎ:

6083

6×10³ + 0×10² + 8×10¹ + 3×10⁰

⸻

Infographic

6083
┌────┬────┬────┬────┐
│ 6 │ 0 │ 8 │ 3 │
└────┴────┴────┴────┘
10³ 10² 10¹ 10⁰

⸻

Binary System কি?

কম্পিউটাৰে Decimal System ব্যৱহাৰ নকৰে।

ই মাত্ৰ দুটা অৱস্থা বুজে:

ON
OFF

বা

1
0

সেয়েহে কম্পিউটাৰে ব্যৱহাৰ কৰে:

Binary System

য’ত মাত্ৰ দুটা digit আছে:

0
1

⸻

Power of 2

Binary ত প্ৰতিটো স্থান 2 ৰ power।

2⁰ = 1
2¹ = 2
2² = 4
2³ = 8
2⁴ = 16
2⁵ = 32
2⁶ = 64

এইবোৰ মুখস্থ কৰি লওক।

⸻

Binary → Decimal Conversion

ধৰা হওক:

1101

Power লিখো:

1 1 0 1
8 4 2 1

এতিয়া য’ত 1 আছে সেইবোৰ যোগ কৰো:

8 + 4 + 1

অতএব:

1101₂ = 13₁₀

⸻

Infographic

1101
┌───┬───┬───┬───┐
│ 1 │ 1 │ 0 │ 1 │
└───┴───┴───┴───┘
8 4 2 1
8 + 4 + 1 = 13

⸻

Decimal → Binary Conversion

ধৰা হওক:

Power of 2:

32 16 8 4 2 1

প্ৰশ্ন:

32 কি 45 ত সোমাব?

✔️ হয়

45 - 32 = 13

16 কি 13 ত সোমাব?

❌ নহয়

8 কি 13 ত সোমাব?

✔️ হয়

13 - 8 = 5

4 কি 5 ত সোমাব?

✔️ হয়

5 - 4 = 1

2 কি 1 ত সোমাব?

❌ নহয়

1 কি 1 ত সোমাব?

✔️ হয়

ফলাফল:

101101

অতএব:

45₁₀ = 101101₂

⸻

Binary Addition

Decimal ত যেনেকৈ:

9 + 1 = 10

Binary ত:

1 + 1 = 10

কাৰণ Binary ত digit “2” নাই।

⸻

চাৰিটা মূল নিয়ম

0 + 0 = 0
0 + 1 = 1
1 + 0 = 1
1 + 1 = 10

⸻

Carry কি?

যেতিয়া আমি পাওঁ:

1 + 1

উত্তৰ:

ইয়াৰ অৰ্থ:

Sum = 0
Carry = 1

⸻

উদাহৰণ

+ 01

সোঁফালৰ পৰা:

1 + 1 = 10

0 লিখিলো, Carry 1।

পিছৰ column:

1 + 0 + Carry(1)

ফলাফল:

100

⸻

Binary Counting

0 = 0000
1 = 0001
2 = 0010
3 = 0011
4 = 0100
5 = 0101
6 = 0110
7 = 0111
8 = 1000

লক্ষ্য কৰক:

0111 + 1 = 1000

যিদৰে:

9 + 1 = 10

⸻

Negative Number সমস্যাটো

এতিয়ালৈকে আমি Positive Number শিকিলো।

কিন্তু:

-1
-2
-3

কম্পিউটাৰে কেনেকৈ সংৰক্ষণ কৰিব?

⸻

Two’s Complement

আধুনিক CPU সমূহে ব্যৱহাৰ কৰে:

Flip All Bits + Add 1

⸻

উদাহৰণ: -5

প্ৰথমে:

+5

0101

Bits flip কৰো:

1010

1 যোগ কৰো:

1010

+0001

1011

অতএব:

1011 = -5

⸻

Negative Number Decode

ধৰা হওক:

1011

ই কি সংখ্যা?

Bits flip:

0100

1 যোগ:

0100

+0001

0101
0101 = 5

অতএব:

1011 = -5

⸻

4-bit Two’s Complement Table

0000 = 0
0001 = 1
0010 = 2
0011 = 3
0100 = 4
0101 = 5
0110 = 6
0111 = 7
1000 = -8
1001 = -7
1010 = -6
1011 = -5
1100 = -4
1101 = -3
1110 = -2
1111 = -1

⸻

CPU কিয় এই পদ্ধতি ব্যৱহাৰ কৰে?

ধৰা হওক:

5 - 3

CPU-এ ইয়াক লিখিব পাৰে:

5 + (-3)

অৰ্থাৎ CPU-ক মাত্ৰ Addition কৰিব জানিলেই হ’ল।

Subtraction ৰ বাবে পৃথক Hardware নালাগে।

এইটোৱেই Two’s Complement ৰ আটাইতকৈ ডাঙৰ সুবিধা।

⸻

আমি আজি কি শিকিলো?

✅ Decimal Number System

✅ Binary Number System

✅ Power of 2

✅ Decimal ↔ Binary Conversion

✅ Binary Addition

✅ Carry Concept

✅ Binary Counting

✅ Negative Numbers

✅ Two’s Complement

✅ CPU কিয় Two’s Complement ব্যৱহাৰ কৰে

⸻

আগলৈ কি?

এইবোৰ বুজিলে আপুনি Nand2Tetris ৰ পৰৱৰ্তী অধ্যায়ৰ বাবে সাজু।

য’ত আমি শিকিম:

NAND Gate
↓
NOT Gate
↓
AND Gate
↓
OR Gate
↓
XOR Gate
↓
Half Adder
↓
Full Adder
↓
ALU
↓
CPU

এটা মাত্ৰ NAND Gate ৰ পৰা সম্পূৰ্ণ Computer বনোৱাৰ যাত্ৰা এতিয়াই আৰম্ভ হৈছে।

How django helped me to build an edtech startup in 3 days...

Hirakjyoti Das — Mon, 07 Jul 2025 04:51:46 +0000

Wow the quickie posts are working 😍

Hirakjyoti Das — Wed, 21 May 2025 06:27:43 +0000