root <ebay_101011_0x2b@yahoo.com> writes:
> I've been trying to track down an svnserve hang issue
> for some time. The details are below:
>
> The problem is that a client checkout over the network
> (via svn: svn+ssh: or http: or https:) has the problem
> that for large repositories it eventually hangs on
> checkout.
Try running the client on the server, i.e. use svn://localhost/ or
http://localhost/. That should help to determine if it is a network
problem.
> imports and checkins work fine. the system
> details and version numbers of all the software are in
> a previous email to the list under the same subject
> heading.
You keep breaking the email threads, which makes it awkward when you
refer to "a previous email".
> A recent trial run where the problem
> happened is logged below.
>
> My biggest sticking point is figuring out where the
> code jumps to in the gdb backtrace. It seems to jump
> off to 0xfffe002 -- where debug symbols do not exist;
> It is not apr code.
The calling stack frame appears to make an apr call, and apr is what
calls read/write shown in the strace output.
> I completely rebuilt apache and
> apr included with apache with debug symbols.
Are you sure you built/installed it correctly?
> (gdb) bt
> #0 0xffffe002 in ?? ()
> #1 0x4007da8c in writebuf_output (conn=0x8055418,
> pool=0x80b9cf8,
> data=0x404824d7
> "Ð\t¯\206¶`\234áLeûíÙðWJ,69gÖ\214k[.G\003ë
> Ì\232²\023\217çMX%ÿÎt?%\036]-\020\236z``¥\201\206úà@\020i\017:ÒK\a-\235¬C3k@Î\034*DÝ\207¡¬#S´\230EkÝ®\e%üx\030\205±_\031\nÝY\002%^ãÂã£\215|\023h\021ÔQÈ\225}å£fÊw·\213ç\220µÐ\210\200Ô¢sJ",
>
> len=98420) at subversion/libsvn_ra_svn/marshal.c:157
Look at marshal.c:157, it calls apr_file_write. Do you get something
like
(gdb) p apr_file_write
$1 = {apr_status_t (apr_file_t *, const void *,
apr_size_t *)} 0x10b50 <apr_file_write>
or does gdb complain about "no debug info"?
You still haven't shown any gdb/strace output for the client, so I can
only guess what the client is doing, I assume it's blocked in a read.
If that's the case then the client is blocked in a read and the server
is blocked in a write. I don't know what to suggest other than a
network problem, particularly since you say it affects both http://
and svn://.
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 9 00:16:06 2004