---
id: 5cb46539-cfdf-4807-8e97-16ddeb8988da
---

# Apache server down incident.
---

This incident type occurs when the Apache server is down on a particular instance. It may cause service disruptions and impact the availability of applications and services running on the server. The incident requires immediate attention and resolution to restore normal operations.

### Parameters
```shell
# Environment Variables

export APACHE_PORT="PLACEHOLDER"

export SERVER_IP="PLACEHOLDER"

export PATH_TO_APACHE_CONF_FILE="PLACEHOLDER"
```

## Debug

### Check if Apache service is running
```shell
systemctl status apache2
```

### Check Apache logs for any errors
```shell
tail -50 /var/log/apache2/error.log
```

### Check Apache configuration files for syntax errors
```shell
apachectl configtest
```

### Check if Apache is listening on the expected port
```shell
netstat -tuln | grep ${APACHE_PORT}
```

### Check server resource usage
```shell
top
```

### Check server disk usage
```shell
df -h
```

### Check network connectivity to the server
```shell
ping ${SERVER_IP}
```

### Check firewall rules to ensure traffic is allowed on Apache port
```shell
iptables -L -n | grep ${APACHE_PORT}
```

## Repair

### Restart Apache service
```shell
echo "Restarting Apache service..."

systemctl restart apache2
```

### Check service status again
```shell
if systemctl status apache2 | grep -q "active (running)"; then

  echo "Apache service has been restarted and is running"

  exit 0

else

  echo "Failed to restart Apache service"

  exit 1

fi
```

### Check for any configuration errors or updates that may have caused the issue and correct them as needed.
```shell

#!/bin/bash

# Set the path to the Apache configuration file

APACHE_CONF=${PATH_TO_APACHE_CONF_FILE}

# Check for any syntax errors in the configuration file

if ! apachectl configtest -f $APACHE_CONF; then

    echo "ERROR: Configuration file contains syntax errors"

    exit 1

fi

# If there are no syntax errors, restart the Apache service

systemctl restart apache2

```

This incident type occurs when the Apache server is down on a particular instance. It may cause service disruptions and impact the availability of applications and services running on the server. The incident requires immediate attention and resolution to restore normal operations.


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.


MongoDB instance down

This incident type refers to frequent mismatches between the virtual hosts configured on an Apache server. This can cause issues with routing traffic to the intended web application or website, resulting in downtime or other problems. It is important to address these mismatches promptly to ensure the proper functioning of the server and any associated applications.


Virtual Host Mismatches on Apache Server.

The Slowloris Attack is a type of Denial of Service (DoS) attack that exploits a vulnerability in the Apache web server. It works by sending HTTP requests to the server and keeping those connections open for as long as possible, thereby using up all the available resources of the server and rendering it unresponsive to legitimate requests. As a result, the server becomes slow or unresponsive, causing downtime for the affected website or service. This type of attack can be detected and mitigated by implementing specific security measures and tools.


Slowloris Attack Detected on Apache server.

This incident type refers to a security vulnerability in the SSL/TLS configuration of the Apache HTTP Server, which can leave the server and its users vulnerable to attacks. The SSL/TLS configuration is responsible for encrypting the communication between the server and its clients, and if it is not configured properly, it can be exploited by hackers to intercept or modify sensitive data. This type of incident requires immediate attention from software engineers to ensure that the SSL/TLS configuration is properly configured to prevent any potential security threats.


Inadequate SSL/TLS Configuration for Apache HTTP Server.

This incident type refers to a situation where the number of child processes created by an Apache server reaches a high threshold, causing performance issues and potentially leading to server crashes. This can occur due to factors such as high traffic volume or misconfigured server settings. The incident requires investigation and mitigation to restore normal server functioning and prevent future occurrences.


High Number of Apache Child Processes Incident

```shell
# Environment Variables

export APACHE_PORT="PLACEHOLDER"

export SERVER_IP="PLACEHOLDER"

export PATH_TO_APACHE_CONF_FILE="PLACEHOLDER"
```


### Check if Apache service is running

```shell
systemctl status apache2
```

### Check Apache logs for any errors

```shell
tail -50 /var/log/apache2/error.log
```

### Check Apache configuration files for syntax errors

```shell
apachectl configtest
```

### Check if Apache is listening on the expected port

```shell
netstat -tuln | grep ${APACHE_PORT}
```

### Check server resource usage

```shell
top
```

### Check server disk usage

```shell
df -h
```

### Check network connectivity to the server

```shell
ping ${SERVER_IP}
```

### Check firewall rules to ensure traffic is allowed on Apache port

```shell
iptables -L -n | grep ${APACHE_PORT}
```


### Restart Apache service

```shell
echo "Restarting Apache service..."

systemctl restart apache2
```

### Check service status again

```shell
if systemctl status apache2 | grep -q "active (running)"; then

  echo "Apache service has been restarted and is running"

  exit 0

else

  echo "Failed to restart Apache service"

  exit 1

fi
```

### Check for any configuration errors or updates that may have caused the issue and correct them as needed.

```shell

#!/bin/bash

# Set the path to the Apache configuration file

APACHE_CONF=${PATH_TO_APACHE_CONF_FILE}

# Check for any syntax errors in the configuration file

if ! apachectl configtest -f $APACHE_CONF; then

    echo "ERROR: Configuration file contains syntax errors"

    exit 1

fi

# If there are no syntax errors, restart the Apache service

systemctl restart apache2

```


Apache server down incident.

Overview

Parameters

Debug

Check if Apache service is running

Check Apache logs for any errors

Check Apache configuration files for syntax errors

Check if Apache is listening on the expected port

Check server resource usage

Check server disk usage

Check network connectivity to the server

Check firewall rules to ensure traffic is allowed on Apache port

Repair

Restart Apache service

Check service status again

Check for any configuration errors or updates that may have caused the issue and correct them as needed.

Learn more

Related Runbooks

MongoDB instance down

Virtual Host Mismatches on Apache Server.

Slowloris Attack Detected on Apache server.

Inadequate SSL/TLS Configuration for Apache HTTP Server.

Support