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

Re: Large Commits Fail

From: Rob Wilkerson <r.d.wilkerson_at_gmail.com>
Date: 2006-08-21 20:55:03 CEST

On 8/21/06, Erik Huelsmann <ehuels@gmail.com> wrote:
> > It's definitely this case. I'm not using BDB as my repository. Well,
> > I don't think I am. I installed via rpm, so I guess I don't know that
> > for a fact.
>
> Ok, well, you didn't say what Subversion version your server is
> running nor what command you used to create your repository. If you
> can look into the repository directory (you said you can't eliminate
> the network from the equation), you should see log.* files in the db/
> directory. If you do, your repository is BDB.
>
You're right, I should have specified. I didn't even think about it,
but I don't have any log.* files so I guess that makes it official.
:-)
>
> > I found the Apache directive I believe you referenced
> > (LimitXMLRequestBody) and set it to 0 to disable the limit, but still
> > no go. The error I get when trying to commit the merge is:
> >
> > COPY of path/to/file.ext: could not connect to server (http://saiprojects).
> >
> > The actual fail on which the commit fails varies, but the message is the same.
>
> Did you have a look in the error log? Maybe one of the Apache childs
> is segfaulting?
>
I've looked at the apache error and access logs and everything looks
pretty normal. Nothing gets reported at all when the failure occurs.
Are there any svn logs I can look at? I've tried to find some, but
either they don't exist or I can't find them.

Thanks again.

-- 
Rob Wilkerson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 21 21:01:39 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.