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

svnsync: initial sync fails partway through with "SSL negotiation failed: Cannot allocate memory"

From: Marinus Damm <marinus_at_jivesoftware.com>
Date: 2006-11-29 17:06:57 CET

Trying to go from a svn 1.4.2 source to a 1.3.2 destination.

a. Created a new empty 1.4.2 source repository, svnadmin load'ed a
3.9GB dump file into it.
b. Created a new empty 1.3.2 destination repository on another host.
c. svnsync init https://dest.example.com/svn2/repos file:///local/
svn/repos <-- works fine
d. svnsync sync https://dest.example.com/svn2/repos <-- fails after
several hours

The sync gets to around rev 15000 and then dies; command line error
message is:

...
Copied properties for revision 15540.
Committed revision 15541.
Copied properties for revision 15541.
svnsync: OPTIONS request failed on '/svn2/repos'
svnsync: OPTIONS of '/svn2/repos': SSL negotiation failed: Cannot
allocate memory (https://dest.example.com)

Both O.S.'s are CentOS 4 (clone of RedHat Enterprise Linux 4).
Subversion was built on the local machine in both cases.

The destination machine has Apache 2.0.52 w/ same version of mod_ssl.

I'm not sure where to begin looking for the problem; is the error
message passed out of svnsync from the destination machine? Or is
svnsync (and neon I guess) on the source machine complaining?

Any suggestions to relieve the condition? This will be a one-time
sync as part of our mirroring setup, so subsequent svnsync's should
be much smaller than this initial one. The sync is roughly 40% done
(both in terms of rev#s and size) when it dies.

Marinus Damm
Received on Wed Nov 29 18:47:40 2006

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