top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration
Print Preview

SVN freezes after the server upgrade

0 votes
37 views

I have svn server running on Windows XP as service (using svnserve.exe). Everything was working fine until I switched server from 1.7 to 1.8. From that moment, every few days, SVN server would freeze eating up all cpu it can (50% on dual core system). Note that I upgraded repository after upgrading svn software.

posted Aug 15, 2013 by Salil Agrawal

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

Similar Questions
+1 vote

I recently upgraded my Subversion client from version 1.7.5 to 1.8.3 and from that time on I experience hangs when executing multiple 'svn log' commands in a short amount of time. The "hanging" svn process consumes all CPU cycles it gets but never finishes.

I can reproduce the problem using the following shell script (on Windows using Cygwin):

#!/bin/bash
ROOT="http://example.com/svn/trunk"
for DIR in $(svn ls "${ROOT}" | head -n 4); do
 svn log -v -l 5 "${ROOT}/${DIR}" 2>&1 | head -n 100 > /dev/null
done

In my environment I need at least 4 svn processes to achieve the faulty behavior. The hang only occurs if the output is truncated using the head command (but it can be redirected to a normal file instead of /dev/null which then contains the expected log messages).

+1 vote

I am running subversion 1.4.2 server with apache 2.2.14 on Linux machine. Now I want to upgrade to subversion 1.8.8 with apache 2.2.25 . Please guide me how to upgrade?

0 votes

I am using subversion (version 1.9.4 (r1740329)) on centos 6..6
have created empty repository. and restored backup (hotcopy)
after restoring backup I am getting following error

Cant read file /svn/test/db/uuid: End of file found

tried searching for such errors but searches found refer to db/current or db/txn-current
I can not use any option svnadmin setuuid or svnlook uuid

How to resolve this issue ?

0 votes

Sometime back I upgraded our server from 1.7.5 to 1.8.8. On an automated build machine we had no issues with timeouts in 1.7.5. However, after upgrading to 1.8.8, client CLI as well, I am running into this time out error about 60% of the time. I have at least one other user running into this as well.

Any ideas or suggestions as to how to correct or work around this issue?


Useful Links with Similar Problem
Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#470/147, 3rd Floor, 5th Main,
HSR Layout Sector 7,
Bangalore - 560102,
Karnataka INDIA.
QUERY HOME
...