| |
@@ -9,11 +9,4 @@
|
| |
echo "#########################################################"
|
| |
EOF
|
| |
|
| |
- # We have a recurring problem with httpd, which manifests itself
|
| |
- # in the following way
|
| |
- # 1. httpd is running, while supervisorctl thinks it failed
|
| |
- # 2. It is not accessible e.g. via curl and returns "connection refused"
|
| |
- # 3. Killing httpd and starting it again fixes the issue
|
| |
- kill -9 `pidof httpd` && supervisorctl start httpd
|
| |
-
|
| |
/bin/bash
|
| |
I was trying to hackishly fix this in 6ae3127, but it probably won't
help, because
pidof httpd
is none.The mentioned PID is of the following process
Which is started by our supervisord. The question is, do we really need
it? I don't think so, since we can just remove it and the docker compose
environment works just fine.