---
id: c76d6346-feba-4d0d-9b14-d37bc515d4b8
---

# MongoDB instance down
---

This incident type refers to an issue where the MongoDB instance is down. This can cause disruption to any applications or services that rely on the database. It requires immediate attention from the appropriate personnel to diagnose and resolve the issue to minimize the impact on the affected systems.

### Parameters
```shell
# Environment Variables

export HOSTNAME="PLACEHOLDER"

export PORT="PLACEHOLDER"

export DATABASE="PLACEHOLDER"

export COLLECTION="PLACEHOLDER"

export INSTANCE_NAME="PLACEHOLDER"

export MONGODB_DATA_DIRECTORY="PLACEHOLDER"
```

## Debug

### Check if MongoDB is running
```shell
systemctl status mongodb
```

### Check MongoDB logs for errors
```shell
journalctl -u mongodb | grep ERROR
```

### Check MongoDB connectivity
```shell
mongo ${HOSTNAME}:${PORT}
```

### Check MongoDB database status
```shell
mongo ${HOSTNAME}:${PORT}/${DATABASE} --eval "db.stats()"
```

### Check MongoDB collection status
```shell
mongo ${HOSTNAME}:${PORT}/${DATABASE} --eval "db.${COLLECTION}.stats()"
```

### Check MongoDB process usage
```shell
top -p $(pgrep -d',' mongod)
```

### Check MongoDB disk usage
```shell
df -h ${MONGODB_DATA_DIRECTORY}
```

## Repair

### Define the affected MongoDB instance
```shell
INSTANCE=${INSTANCE_NAME}
```

### Restart the MongoDB service
```shell
sudo systemctl restart mongodb.service
```

### Check the status of the MongoDB service
```shell
STATUS=$(sudo systemctl status mongodb.service | grep "Active:" | awk '{print $2}')
```

### Check if the service has started successfully
```shell
if [ "$STATUS" == "active" ]; then

    echo "MongoDB service has been restarted successfully."

else

    echo "Failed to restart MongoDB service."

fi
```

This incident type refers to an issue where the MongoDB instance is down. This can cause disruption to any applications or services that rely on the database. It requires immediate attention from the appropriate personnel to diagnose and resolve the issue to minimize the impact on the affected systems.


This incident type refers to a situation where a SQLServer database goes offline, which can potentially cause disruptions in software or applications that rely on it. The incident is triggered by a monitoring system that detects the database's state is not available. A prompt response is necessary to resolve the issue and prevent any adverse impact on the system.


Database Offline (SQLServer)

This incident type refers to an issue with Redis replication, which means that there is a problem with the synchronization of data between Redis instances. This issue could impact the availability and performance of the system and may require immediate attention to restore the replication and ensure data consistency. The incident could be caused by various factors, such as network problems, hardware failures, or configuration issues. The incident must be investigated and resolved as soon as possible to avoid any data loss or downtime.


Redis replication broken incident.

A Redis instance down incident refers to a situation where the Redis server, which is a popular open-source in-memory data structure store, is not functioning or accessible. This can cause interruption in the service and impact the performance of applications that rely on Redis for caching or data storage. Typically, this type of incident is considered high urgency and requires immediate attention from the responsible team to investigate, diagnose, and resolve the issue.


Redis instance down incident

This incident type refers to an issue with Redis where one or more slave instances have become disconnected, resulting in replication failure. This can cause data inconsistencies and may require immediate attention to restore normal functioning. The incident may be caused by a variety of factors, such as network issues, server failures, or misconfiguration.


Redis disconnected slaves incident

This incident type is related to an issue with a Redis instance being down. Redis is an in-memory data structure store used as a database, cache, and message broker. This incident could potentially cause disruption to applications and services that rely on Redis for data storage or caching.


Redis Instance Down

```shell
# Environment Variables

export HOSTNAME="PLACEHOLDER"

export PORT="PLACEHOLDER"

export DATABASE="PLACEHOLDER"

export COLLECTION="PLACEHOLDER"

export INSTANCE_NAME="PLACEHOLDER"

export MONGODB_DATA_DIRECTORY="PLACEHOLDER"
```


### Check if MongoDB is running

```shell
systemctl status mongodb
```

### Check MongoDB logs for errors

```shell
journalctl -u mongodb | grep ERROR
```

### Check MongoDB connectivity

```shell
mongo ${HOSTNAME}:${PORT}
```

### Check MongoDB database status

```shell
mongo ${HOSTNAME}:${PORT}/${DATABASE} --eval "db.stats()"
```

### Check MongoDB collection status

```shell
mongo ${HOSTNAME}:${PORT}/${DATABASE} --eval "db.${COLLECTION}.stats()"
```

### Check MongoDB process usage

```shell
top -p $(pgrep -d',' mongod)
```

### Check MongoDB disk usage

```shell
df -h ${MONGODB_DATA_DIRECTORY}
```


### Define the affected MongoDB instance

```shell
INSTANCE=${INSTANCE_NAME}
```

### Restart the MongoDB service

```shell
sudo systemctl restart mongodb.service
```

### Check the status of the MongoDB service

```shell
STATUS=$(sudo systemctl status mongodb.service | grep "Active:" | awk '{print $2}')
```

### Check if the service has started successfully

```shell
if [ "$STATUS" == "active" ]; then

    echo "MongoDB service has been restarted successfully."

else

    echo "Failed to restart MongoDB service."

fi
```


MongoDB instance down

Overview

Parameters

Debug

Check if MongoDB is running

Check MongoDB logs for errors

Check MongoDB connectivity

Check MongoDB database status

Check MongoDB collection status

Check MongoDB process usage

Check MongoDB disk usage

Repair

Define the affected MongoDB instance

Restart the MongoDB service

Check the status of the MongoDB service

Check if the service has started successfully

Learn more

Related Runbooks

Database Offline (SQLServer)

Redis replication broken incident.

Redis instance down incident

Redis disconnected slaves incident

Support