Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <43848FF5.40001@slive.ca>
Date: Wed, 23 Nov 2005 10:51:17 -0500
From: Joshua Slive <joshua@slive.ca>
User-Agent: Thunderbird 1.4 (Windows/20050908)
MIME-Version: 1.0
To: Paul Querna <chip@force-elite.com>
CC: dev@httpd.apache.org,  infrastructure@apache.org
Subject: Re: 2.1.10-worker core dumps on minotaur
References: <438343CB.9080002@slive.ca> <43837A3D.5020401@force-elite.com>
 <43837B7C.4090200@slive.ca> <20051123110206.GD357@redhat.com>
 <43847B42.6040904@slive.ca> <43848CFD.30607@force-elite.com>
In-Reply-To: <43848CFD.30607@force-elite.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


Paul Querna wrote:
> Joshua Slive wrote:
>> Interestingly, the
>> core files are all almost exactly the same size (538 MB) which, along
>> with the malloc failure, points strongly to hitting a resource limit
>> someplace.  Any freebsd gurus want to comment?
> 
> FreeBSD has a default memory resource limit of 512 mb max per process.
> 
> We need to set the MAXDSIZE in the kernel to something higher.  It can
> be compiled this way, or tuned via a sysctl.

But I guess we should really determine why svn is sucking up all that 
memory.  If we just increase the memory limit, we risk the whole server 
being taken down by this.

I don't really know how to debug svn problems; the request always seems 
to be just
REPORT /repos/asf/!svn/vcc/default HTTP/1.1
which doesn't help very much.

Joshua.