Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Our system just suffered through a huge surge in connections. Our load balancer graphs reflect this surge in connections. Netstat graphs reflect this surge in connections. Our Apache Processes graph reflect this surge in connections. But the Apache Accesses graph does not.

What would cause a spike in apache processes but not apache accesses?

I had assumed that "apache accesses" meant "requests to apache".

share|improve this question
up vote 1 down vote accepted

It is a common situation when request processing time increases suddenly for a short period of time. Apache starts additional processes because existing processes are not able to keep up with the same number of requests. This can be caused by resource contention, say problems on a DB layer like long-running or I/O-intensive CPU queries performed, say, by maintenance scripts or something like this. You really need to monitor DB health too (and other resources like queue servers too if you have any).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.