# Httpd already running

**URL:** <https://forums.docker.com/t/httpd-already-running/33397>\
**Category:** Docker Hub\
**Created:** [June 10, 2017, 11:49am UTC](https://forums.docker.com/t/httpd-already-running/33397 "2017-06-10T11:49:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![paniez46](https://avatars.discourse-cdn.com/v4/letter/p/bc8723/32.png) [@paniez46](https://forums.docker.com/u/paniez46)\
**Post date:** [June 10, 2017, 11:49am UTC](https://forums.docker.com/t/httpd-already-running/33397/1 "2017-06-10T11:49:51Z")

</div>

Hi,

I use Docker on Ubuntu 16.04 to have a container with Apache.

All worked fine since yesterday and my container stop this morning. When I try to start again, I have an error :

`httpd (pid 8) already running`

I restart docker, but nothing changes (no httpd pid is present)

```
$ docker version
Client:
 Version: 17.05.0-ce
 API version: 1.29
 Go version: go1.7.5
 Git commit: 89658be
 Built: Thu May 4 22:10:54 2017
 OS/Arch: linux/amd64
Server:
 Version: 17.05.0-ce
 API version: 1.29 (minimum version 1.12)
 Go version: go1.7.5
 Git commit: 89658be
 Built: Thu May 4 22:10:54 2017
 OS/Arch: linux/amd64
 Experimental: false

```

I have this error with docker status : `Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/..... segmentation fault (core dumped).`

I install cgroup-lite and I have already aufs-tools package, but nothing changes. I try with official CE edition (a little bit older v. 17.03.1-ce), but nothing changes.  
I already stop and start this container before, but now, it doesn’t want start again.

EDIT1 : I stop this container and make a `docker run ...` to have a new container from my image and I have the same result.

EDIT2 : When I go in `/var/lib/docker/aufs/mnt/`, I have some directories. The only which has something (a core file) is directory in my error : `/var/lib/docker/aufs/mnt/6a32630585211a651c406794ad20e7965c59318ea65d485855b8d7925b9f6e40`

Thanks

---

<div class="post-metadata">

**Author:** ![nbonniot](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/nbonniot/32/18497_2.png) [@nbonniot](https://forums.docker.com/u/nbonniot)\
**Post date:** [January 15, 2018, 3:37pm UTC](https://forums.docker.com/t/httpd-already-running/33397/2 "2018-01-15T15:37:47Z")

</div>

Hello,  
I ran into the same issue. This is because `/var/run/apache2.pid` is existing on Apache container up, and also I suspect you only use `docker stop` to stop your containers (whereas a `docker-compose down` is closer to Docker philosophy in here, because all persistant data should lie within a mapped volume). So, container is basically reused as is on start/stop processes. If it crashed on something similar, it will not restart with this PID story.  
2 solutions for me :

- Exclusively `docker-compose down` when stopping.

- Modifying Apache Dockerfile image to add :

Very last solution is actually setup in [php official image](https://github.com/docker-library/php/blob/bdfd0fc1d19102cd6f951614072a51eabf7191bf/5.6/apache/apache2-foreground).