RabbitMQ: connection blocked by a resource alarm

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

rabbitmqctl status | grep -A5 'alarms\|memory\|disk_free'
rabbitmq-diagnostics alarms
rabbitmq-diagnostics memory_breakdown

# Free space is the usual trigger: the default watermark is 50 MB
rabbitmqctl set_disk_free_limit "2GB"
rabbitmqctl set_vm_memory_high_watermark 0.6

# Real fix is a backlog: find the queue that grew
rabbitmqctl list_queues name messages consumers --formatter pretty_table

# Handle the signal in the client rather than blocking forever
# amqplib: connection.on('blocked', ...) / ('unblocked', ...)

How to diagnose MessageQueue errors

Queue errors are usually about the balance between producers and consumers. Growing lag means consumers cannot keep up. Endless rebalancing usually means consumers are being evicted for exceeding a poll or heartbeat interval, not that the cluster is unhealthy. A poison message, one that always fails processing, will block an ordered partition forever unless there is a dead-letter path, which is why a DLQ is not optional in production.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

1. Measure lag over time, not once: kafka-consumer-groups --describe --group <g>. The trend distinguishes a throughput problem from a stuck consumer.
2. For repeated rebalancing, compare processing time per batch against max.poll.interval.ms. Slow processing looks exactly like a dead consumer to the coordinator.
3. Always configure a dead-letter queue with a bounded retry count. Without one, a single malformed message stops the partition indefinitely.
4. Check message size against the broker limit before assuming a network failure: SQS caps at 256 KB, Kafka at message.max.bytes.
5. Verify consumer ACLs and topic authorisation separately from connectivity; an authorisation failure often surfaces as a metadata error.

Tools worth reaching for

• kafka-consumer-groups
• rabbitmqctl list_queues
• aws sqs get-queue-attributes
• kafkacat / kcat
• flower (Celery)

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

📖 rabbitmq.com

Related MessageQueue errors

• AWS SQS: Message too large (256KB limit)The SQS message body exceeds the 256KB maximum size limit.
• Celery: WorkerLostErrorA Celery worker process died unexpectedly during task execution, often due to OOM kill…
• Kafka: LEADER_NOT_AVAILABLEPartition has no elected leader. Broker down, ISR empty, or topic just created and metadata…
• Kafka: Offset out of rangeConsumer trying to read from offset that doesn't exist. Data retention deleted old messages.
• Kafka: RecordTooLargeExceptionA message exceeded a size limit. Three separate limits must agree: the producer's…
• Kafka: Topic authorization failedThe Kafka client does not have the required ACL permissions to produce to or consume from the…
• Kafka: UNKNOWN_TOPIC_OR_PARTITIONThe client asked for a topic the broker does not know about. Either the topic genuinely does…
• Message Queue: Consumer lag too highMessages accumulating faster than consumers can process. Queue backlog growing.

See all 14 MessageQueue errors →

Browse other categories

• HTTP 494xx client errors, 5xx server errors, redirects, headers and protocol problems.
• JavaScript 42npm resolution, async pitfalls, hydration, memory limits and runtime type…
• Database 41Connections, deadlocks, constraints, replication and memory limits.
• AI 35Rate limits, context windows, GPU memory and model-serving failures.
• Network 35Refused connections, timeouts, resets, MTU problems and port exhaustion.
• Python 35Imports, virtual environments, encoding, concurrency and dependency conflicts.
• Kubernetes 34CrashLoopBackOff, ImagePullBackOff, OOMKilled, RBAC, scheduling and storage.
• Docker 27Daemon connectivity, disk space, image pulls, ports and architecture mismatches.
• System 26Disk space, systemd units, file descriptors, OOM killer and scheduled jobs.
• Cloud 25IAM permissions, quotas, service limits and credential failures.
• Security 25JWT validation, CSRF, OAuth grants, SELinux, SSH host keys and CSP.
• TLS 24Untrusted authorities, expiry, hostname mismatch, chains and cipher negotiation.

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.