On Sat, Feb 09, 2002 at 12:33:33PM -0600, Ben Collins-Sussman wrote:
> Ok, I un-wedged the repository again with db_recover, but I *finally*
> ran capture-stacks.sh!
>
> The output is on svn.collab.net in /root/stackcapture.
>
> But it's here in the mail -- maybe this will give us a clue about
> which process is wedged and why:
This trace looks normal. I wonder what the memory usage was. Based
on the error logs, it sounds like Berkeley DB was complaining:
[Sat Feb 09 12:18:16 2002] [error] [client 64.81.140.147] Could not
fetch resource information. [500, #0]
[Sat Feb 09 12:18:16 2002] [error] [client 64.81.140.147] Could not
open the SVN filesystem at /usr/www/repositories/svn [500, #21074]
[Sat Feb 09 12:18:16 2002] [error] [client 64.81.140.147] (2)No such
file or directory: Berkeley DB error while opening `nodes' table for
filesystem /usr/www/repositories/svn/db:
Cannot allocate memory [500, #21074]
The server *was* responding to HTTP requests, so I'm not sure this
problem was related to Apache 2.0. But, I would strongly recommend
updating to httpd-2.0 HEAD as we've fixed some SEGVs in our code.
-- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:06 2006