Jack Baty wrote:
> On 8/2/06, Nico Kadel-Garcia <nkadel@comcast.net> wrote:
>> Jack Baty wrote:
>>> I'm having trouble running svn checkout on a freshly built CentOS 4
>>> box. Checkout will just hang at some point and never finish. By
>>> "never" I mean at least 30 minutes, which is how long I've waited.
>>> This is via http. Other machines (all sorts of clients - running on
>>> OS X, Windows, FreeBSD, Debian) do not experience this problem.
>>>
>>> The server's Apache log sometimes, but not always, contains the
>>> following....
>>> [Wed Aug 02 16:16:34 2006] [error] [client 69.16.250.112] Provider
>>> encountered an error while streaming a REPORT response. [500, #0]
>>> [Wed Aug 02 16:16:34 2006] [error] [client 69.16.250.112] A failure
>>> occurred while driving the update report editor [500, #190004]
>>>
>>> ...which is specifically mentioned in the Subversion FAQ and which
>>> recommends rebuilding Apache/APR and Subversion after setting a
>>> certain environement variable - which I've done. The FAQ entry
>>> implies that this is only an issue when the server is running on OS
>>> X, but I thought I'd give it a shot anyway. So the server is now
>>> running 1.3.2 and Apache 2.0.54. Still hanging the CentOS client
>>> box though. This is happening on 2 nearly identical CentOS machines.
>>> I've tried
>>> building Subversion from source (1.2 and 1.3) and also the default
>>> package install via yum (1.1x) and all behave the same way.
>>>
>>> Anything I should try?
>
>>
>> Grab David Summers' SRPM's, from:
>>
>> http://summersoft.fay.ar.us/pub/subversion/latest/
>>
>> David *writes* the .spec files in the tarballs: you can use those to
>> build your own RPM's, which I find handy, although you may have to
>> apply the relatively recent patch for 64-bit use if your system is
>> 64-bit.
>
>
> Thanks, I've tried the source RPM with the same results. On a whim, I
> thought I'd (once again) check using svn+ssh:// and that also hung on
> me for the first time, so it seems it's not specifically a neon/dav
> sort of problem.
>
> Trouble is, it's intermittent. This morning I've been able to checkout
> from a number of different repositories using both svn+ssh and http.
> Works 5 out of 10 times. If I interrupt the checkout, then move into
> the partial working copy's directory and run 'svn up' it has always
> finished the checkout successfully.
>
> Not sure which tree to bark up next. Do you suppose it's a CentOS
> specific issue (since I have to CentOS boxes behaving this way) or
> something on the server or perhaps a combination of the two? I'm happy
> to provide more information if it will help.
You know.......
Do you have any network intermittency or DNS issues? I'm wondering if you
have a flaky network connection that's failing to close one step properly,
so SVN is just left haning there.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 3 22:08:07 2006