[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Problem/Crash doing large checkout via DAV

From: Gerald Richter <richter_at_ecos.de>
Date: 2002-06-04 09:21:20 CEST

> >
> > Any logs/debug infos I can enable to get more infos?
> Well, yeah... if the bug is perfectly reproducible, the best thing you
> can do is run httpd inside gdb and figger out the problem!

"figger out the problem" is always the best thing you can do!

> Make sure you compile both httpd and svn with --enable-maintaine-mode,
> and then read the section in our HACKING file on "Debugging the
> server".

Also I am familar with debuging Apache modules, you know debugging an more
or less unknown software of this size is not an 5 minute task...

So maybe you can give me some more hints. I rerun the checkout via DAV and
noticed when it comes to the point where it fails it does a PROPFIND on the
directory i586-linux. This directory is very large and the server seems to
go through the data (I see a lot of disk access), after 90 sec I get the
error. Is it possible that this is a simple time-out? The Apache TimeOut is
set to 300, but maybe there are some other time-out values either server or
client side?

Is it normal that a PROPFIND for a large directory (about 40MB & 40,000
files) takes such a long time. Does the svn server recurse through the
subdirs at this point or is it a part of the error that it takes such a long
time? (EVerything is on the same machine, so there is no network traffic
time involved)



Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting

Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: richter@ecos.de Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 4 09:18:30 2002

This is an archived mail posted to the Subversion Dev mailing list.