> Source: [sk100707](https://support.checkpoint.com/results/sk/sk100707)

# sk100707 - When trying to start Apache 2.2 service, get following response: "Apache is currently not running and it is trying to start"

| Property | Value |
|----------|-------|
| Solution ID | sk100707 |
| Date Created | 2014-05-30 |
| Last Modified | 2014-06-03 |
| Technical Level | General |
| OS | Linux, Gaia |

## Symptoms

- * When trying to start the Apache 2.2 service, get the following response: "Apache is currently not running and it is trying to start".
* See the following error in the apache_error.log: '\[Date and Time\] \[emerg\] (28)No space left on device: Couldn't create accept lock (/opt/CPuepm-R77/apache22/logs/accept.lock.22233) (5)'

## Cause

Found that this is a general issue with Apache 2.2 service in Linux OS platforms.

What is believed to have caused this problem is Apache not being able to write due to active semaphores using all of the predefined space in the Apache directory.

Semaphores are used for communicating between the active processes of a certain application. They are used to communicate between parent and child processes. Due to the semaphores not being cleaned out properly, Apache can't write this information and therefore can't communicate properly with all of the processes it starts.

The following URL Link explains the issue further: <http://major.io/2007/08/24/apache-no-space-left-on-device-couldnt-create-accept-lock/>

## Solution

**Environment:**Clients are 'Offline' or 'Disconnected'.

**Important:** Please make sure you have the symptoms listed above before proceeding with the solutions, as this only applies to Endpoint Management Servers and certain environments.

**Solution #1:**

1. A reboot of the server should automatically resolve the semaphore issue.

2. After the reboot, test the Apache service to see if it is running with the following commands:

\>**To stop Apache service, run:** $UEPMDIR/apache22/bin/httpd -d $UEPMDIR/apache22 -k stop

\>**To start, run:** $UEPMDIR/apache22/bin/httpd -d $UEPMDIR/apache22 -k start

3. Apache should start up properly and your clients should be able to communicate with the Endpoint Server momentarily. The clients usually take up to 5 minutes to see Apache up and running.

**\*\*\*If this does not resolve the issue, please refer to Solution #2 below\*\*\***

**Solution #2:**

1. To see if semaphores exist run: # ipcs -s

2. If you see a list of semaphores, Apache has not cleaned up after itself, and semaphores are stuck. Run the following command to clear them out:

# for i in 'ipcs -s \| awk '/httpd/ {print $2}''; do (ipcrm -s $i); done

3. Then try to start Apache using the following command:

$UEPMDIR/apache22/bin/httpd -d $UEPMDIR/apache22 -k start

4. In most cases, Apache should start up properly.

5. If the this does resolve the issue, this may not be the problem you are facing or the issue could be that you are completely out of available semaphores. **Please refer to the URL Link provided under "Cause".** It explains how to increase your available semaphores. You would need to get into the kernel of the OS to do so.

**\*\*\*If none of the above solutions resolve the issue, please [Contact Check Point Support](http://www.checkpoint.com/services/contact/index.html) to open a new SR, if you have not done so.\*\*\***

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content