---
id: c17e98e1-9adf-48d6-99aa-a729a1f36dc0
---

# Low Disk Space on RabbitMQ
---

This incident type refers to an alert triggered when the available disk space on RabbitMQ is low. This can be caused by an overload of messages or persistent messages that are being mismanaged. It is important to resolve this issue promptly to ensure the proper functioning of RabbitMQ and avoid any potential downtime.

### Parameters
```shell
# Environment Variables

export RABBITMQ_CONFIG_FILE="PLACEHOLDER"

export RABBITMQ_ERROR_LOG="PLACEHOLDER"

export RABBITMQ_HOST="PLACEHOLDER"

export RABBITMQ_PORT="PLACEHOLDER"

export RABBITMQ_USER="PLACEHOLDER"

export RABBITMQ_PASSWORD="PLACEHOLDER"
```

## Debug

### Check disk usage for the partition where RabbitMQ is installed
```shell
df -h 
```

### Check the size of the RabbitMQ data directory
```shell
du -sh /opt/rabbitmq/data
```

### Check the size of the RabbitMQ message queue
```shell
sudo rabbitmqctl list_queues name messages_ready messages_unacknowledged
```

### Check the size of the RabbitMQ log files
```shell
ls -lh /opt/rabbitmq/logs
```

### Check the RabbitMQ configuration file for disk space related settings
```shell
cat ${RABBITMQ_CONFIG_FILE} | grep disk
```

### Check the RabbitMQ process status
```shell
sudo systemctl status rabbitmq-server
```

### Check the RabbitMQ error log for disk space related errors
```shell
sudo cat ${RABBITMQ_ERROR_LOG} | grep disk
```

### Check the system log for disk related errors
```shell
sudo cat /var/log/syslog | grep disk
```

### Check if there are any old or unused files that can be deleted to free up space
```shell
sudo find / -xdev -type f -atime +30 -size +10M -exec ls -lh {} \;
```

## Repair

### Identify any messages or persistent messages that are being mismanaged and take action to resolve the issue (e.g., delete unnecessary messages, optimize message storage).
```shell


#!/bin/bash



# Set variables

RABBITMQ_HOST=${RABBITMQ_HOST}

RABBITMQ_PORT=${RABBITMQ_PORT}

RABBITMQ_USER=${RABBITMQ_USER}

RABBITMQ_PASSWORD=${RABBITMQ_PASSWORD}



# Identify messages or persistent messages that are being mismanaged

rabbitmqctl list_queues | while read line

do

    queue=$(echo $line | awk '{print $1}')

    messages=$(echo $line | awk '{print $2}')

    if [ $messages -gt 1000 ]; then

        echo "Queue $queue has $messages messages"

        # Take action to resolve the issue (e.g., delete unnecessary messages, optimize message storage)

        rabbitmqadmin -H $RABBITMQ_HOST -P $RABBITMQ_PORT -u $RABBITMQ_USER -p $RABBITMQ_PASSWORD delete queue name=$queue

        echo "Deleted queue $queue"

    fi

done


```


This incident type refers to an alert triggered when the available disk space on RabbitMQ is low. This can be caused by an overload of messages or persistent messages that are being mismanaged. It is important to resolve this issue promptly to ensure the proper functioning of RabbitMQ and avoid any potential downtime.


A Rabbitmq memory high incident occurs when a node uses more than 90% of the allocated RAM. This can cause performance issues and impact the overall functionality of the system. It is important to promptly address this issue to prevent any further damage.


Rabbitmq memory high incident.

This incident type occurs when the ratio of unacknowledged to acknowledged messages in a RabbitMQ queue is higher than usual. This may indicate a problem in the message pipeline and requires investigation to ensure that messages are being processed properly. It is often accompanied by a query alert monitor triggered by a specific metric threshold.


RabbitMQ Unacknowledged Messages Alert

This incident type refers to the restart of a MySQL instance that has caused an alert to trigger. It may be related to issues with the MySQL database or the server hosting the instance. The incident requires investigation and resolution to ensure the proper functioning of the affected services.


MySQL instance restart incident

This incident type refers to cases where the MySQL service, which is responsible for managing and storing data in a database, runs out of available space. This can happen due to a variety of reasons such as an unexpected increase in data volume or insufficient allocation of storage resources. When the MySQL service runs out of space, it can cause data loss, application errors, and even system crashes if not addressed promptly.


MySQL Service Out of Space.

This incident type occurs when there is a loss of connection to the MySQL server during the process of querying a database. This can happen due to various reasons such as network issues, server overload, or software errors. As a result, the query execution fails and users may experience disruptions in accessing data from the database. It is critical to resolve this issue promptly to avoid data loss or corruption.


Lost connection to MySQL server while querying a database incident.

```shell
# Environment Variables

export RABBITMQ_CONFIG_FILE="PLACEHOLDER"

export RABBITMQ_ERROR_LOG="PLACEHOLDER"

export RABBITMQ_HOST="PLACEHOLDER"

export RABBITMQ_PORT="PLACEHOLDER"

export RABBITMQ_USER="PLACEHOLDER"

export RABBITMQ_PASSWORD="PLACEHOLDER"
```


### Check disk usage for the partition where RabbitMQ is installed

```shell
df -h 
```

### Check the size of the RabbitMQ data directory

```shell
du -sh /opt/rabbitmq/data
```

### Check the size of the RabbitMQ message queue

```shell
sudo rabbitmqctl list_queues name messages_ready messages_unacknowledged
```

### Check the size of the RabbitMQ log files

```shell
ls -lh /opt/rabbitmq/logs
```

### Check the RabbitMQ configuration file for disk space related settings

```shell
cat ${RABBITMQ_CONFIG_FILE} | grep disk
```

### Check the RabbitMQ process status

```shell
sudo systemctl status rabbitmq-server
```

### Check the RabbitMQ error log for disk space related errors

```shell
sudo cat ${RABBITMQ_ERROR_LOG} | grep disk
```

### Check the system log for disk related errors

```shell
sudo cat /var/log/syslog | grep disk
```

### Check if there are any old or unused files that can be deleted to free up space

```shell
sudo find / -xdev -type f -atime +30 -size +10M -exec ls -lh {} \;
```


### Identify any messages or persistent messages that are being mismanaged and take action to resolve the issue (e.g., delete unnecessary messages, optimize message storage).

```shell


#!/bin/bash



# Set variables

RABBITMQ_HOST=${RABBITMQ_HOST}

RABBITMQ_PORT=${RABBITMQ_PORT}

RABBITMQ_USER=${RABBITMQ_USER}

RABBITMQ_PASSWORD=${RABBITMQ_PASSWORD}



# Identify messages or persistent messages that are being mismanaged

rabbitmqctl list_queues | while read line

do

    queue=$(echo $line | awk '{print $1}')

    messages=$(echo $line | awk '{print $2}')

    if [ $messages -gt 1000 ]; then

        echo "Queue $queue has $messages messages"

        # Take action to resolve the issue (e.g., delete unnecessary messages, optimize message storage)

        rabbitmqadmin -H $RABBITMQ_HOST -P $RABBITMQ_PORT -u $RABBITMQ_USER -p $RABBITMQ_PASSWORD delete queue name=$queue

        echo "Deleted queue $queue"

    fi

done


```


Low Disk Space on RabbitMQ

Overview

Parameters

Debug

Check disk usage for the partition where RabbitMQ is installed

Check the size of the RabbitMQ data directory

Check the size of the RabbitMQ message queue

Check the size of the RabbitMQ log files

Check the RabbitMQ process status

Check if there are any old or unused files that can be deleted to free up space

Repair

Identify any messages or persistent messages that are being mismanaged and take action to resolve the issue (e.g., delete unnecessary messages, optimize message storage).

Learn more

Related Runbooks

Rabbitmq memory high incident.

RabbitMQ Unacknowledged Messages Alert

MySQL instance restart incident

MySQL Service Out of Space.

Support