Closed Bug 717634 Opened 13 years ago Closed 13 years ago

issues with apache on hg.build.scl1.mozilla.com

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: arich, Assigned: cshields)

Details

hg2.build.scl1.mozilla.com (where hg.build.scl1.mozilla.com currently points) has run into trouble twice in the past week. The two issues I've seen are that it stops responding to http requests, and it starts swapping large processes out. When I looked at the swap issue, there were many 500M+ httpd processes that were swapped out. Restarting http cleared those up, but I suspect this is part of a larger issue (either a memory leak or a misconfiguration). When httpd stops responding to requests, the following can be found in the log: [error] server reached MaxClients setting, consider raising the MaxClients setting Could someone familiar with hg and these machines (bkero?) take a look to what we should be tuning/configuring and if we have other issues besides that?
Assignee: server-ops → cshields
oremj blessed this node with some apache/wsgi tweaks - it is much happier now. Please let us know if it runs into problems.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Just to verify, these will also apply to hg1 as well (and if it doesn't now, it will when hg1 is upgraded to match hg2)?
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.