About once a week or so Apache just stops listening and we have to restart
the Apache service. I had found in one of my php scripts a problem with
some database calls. The result set was being populated over and over
again in a loop that may occur several thousand times. I added an unset to
the bottom of the loop and we went from having this problem on almost a
daily basis to about once a week. I just went through my php code with a
fine tooth comb and found one other spot that this may be occuring and
changed it. I am hoping this will fix our problem. Has anyone seen this
problem before? Am I on the right track? Also, I am considering setting
up a scheduled event to restart Apache at 2AM every morning. Do you think
this might help?
[Pete Says:] How do you define ‘stops
listening’, and do you mean ‘stops responding’? If you note problems with
database calls, then that may be where all of your problems lie. Perhaps it is
timing out threads, consuming all of them, and denying requests as a result. Are
you sure your code is exiting properly? I would continue checking for that kind
of thing. You do not mention CPU use either. When apache does not respond, does
load go up on the cpu(s)?
