On Tue, Oct 26, 2010 at 5:40 AM, John Doe <jd...@yahoo.com> wrote: > If you google for: > > svn "Secure connection truncated" > > the first and second answers propose one solution. maybe try it and see if > your > problems disappear?
I just did that google, and the first post (http://gallery.menalto.com/node/53820) never solved the issue. The user just said he'll do the checkout 30+ times until he gets what he needs. The second (http://www.svnforum.org/2017/viewtopic.php?p=12332) recommended setting SVNPathAuthz to "off" which is already set that was in mgolovko's configuration. I checked out a few more posts: http://www.sharp-tools.net/archives/000928.html reported that he also set SVNPathAuthz to "off" which solved the issue. He also did the following: * Increased the timeout to 1000 seconds (which fixed an earlier connection issue) * Tried disabling apache worker mpm and relying on prefork, as per a suggestion for someone losing connections using svn+ssh. That didn't work; re-enabled. * Disabled http compression (by commenting out the loading of mod_deflate). Left that disabled just in case. * Enabled keepalive and upped the requests per connection. No change. The issue seems to be related to a memory leak in DAV (mod_dav_svn) which is probably beyond my personal expertise to trace down. However, mgolovk should check his Apache logs and see if Apache is dying. Since these posts are from 4 years ago, I'm surprised that the DAV memory leak hasn't yet been plugged. It looks like he's using the latest versions of Apache and Subversion. -- David Weintraub qazw...@gmail.com
