Marc Breslow <marc2...@gmail.com> writes: > Did some more testing here and still stuck. > > In one test I changed the sync source to be a different repository on a > different server and sync worked. So pretty sure it is an issue with the > source repo now.
>> > >> > svnsync synchronize [target-http-url] [source-svn+ssh-url] >> > >> >>> It just hangs there. To rule out HTTP you could create a local repository and change the target URL from http://http-server/... to file:///... You said you already managed to get some svnserve logging, so the next step would be to examine the traffic. Something like wireshark will capture it but it will be encrypted. One way to get unencrypted svn+ssh traffic is to set up a proxy on the machine running svnsync: socat -v TCP-LISTEN:9630,reuseaddr,fork EXEC:'ssh ssh-server svnserve -t' and change your source URL from svn+ssh://ssh-server/... to svn://localhost:9630/... In this way the network traffic is still encrypted but the socat proxy dumps the unencrypted traffic to the terminal. If the svnserve process on the ssh server really is hanging then you need to log on to server and debug that process. Perhaps attach gdb to the running process and get a backtrace, or attach strace to the running process and see what system calls are happening. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
