Kubernetes Apache2 Killed
It is what it is. Your Apache process is using more memory than you are allowing in your pod/container definition.
Reasons why it could be needing more memory:
- You have an increase in traffic and sessions being handled
- Apache is forking more processes within the container running into memory limits.
- Apache not reaping some lingering sessions because of a config issue.
If you are running Docker for containers (which most people do) you can ssh into the node in your cluster and run a:
docker ps -aYou should see the Exited container where your Apache process(es) was running. Then you can run:
docker logs <container-id>And you might get details on why Apache was doing before it was killed. If you only see minimal info, I recommend increasing the verbosity of your Apache logs.
Hope it helps.