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

Re: Re: Provider encountered an error while streaming a REPORT response

From: J J <eggsgloriouseggs_at_gmail.com>
Date: Thu, 19 Jun 2008 11:42:21 -0500

On Thu, Jun 19, 2008 at 11:22 AM, J J <eggsgloriouseggs_at_gmail.com> wrote:
> Could this error be related?
>
> svn: Decompression of svndiff data failed

I'm now getting this error even when I point to a server running
Subversion 1.5.0, using a 1.4.5 Windows client with no content switch
between the server and client.

I haven't been able to reproduce the "forcibly closed" error yet with
1.5.0, but I really need to get a server setup with a content switch
and 1.5.0 to truly test that, since it has never happened when
bypassing the content switch.

> This happens sometimes instead of the forced disconnect error. Again,
> I only see it when the working copy is on NAS. I've run svnadmin
> verify on the repository and all looks good.
>
> On Thu, Jun 19, 2008 at 9:38 AM, J J <eggsgloriouseggs_at_gmail.com> wrote:
>> I've read http://svn.haxx.se/users/archive-2008-05/0361.shtml but I'm
>> already running Subversion 1.4.5 built against Apache 2.2.8, built
>> from scratch using the provided subversion-deps file.
>>
>> Part of the above post made it sound like this might be a problem even
>> with the latest APR, and that the new serf webdev client might perform
>> better.
>>
>> Can someone provide more information on this? Is this a bug with APR?
>> What is the actual source of the problem? Why am I only seeing it
>> when my working copy is stored on NAS?
>>
>> Thanks,
>> Justin
>>
>> On Thu, Jun 19, 2008 at 9:28 AM, <Sathish-S.Kumar_at_ubs.com> wrote:
>>> Hi,
>>>
>>> I am facing the very similar error while trying to checkout
>>> REPORT request failed on /prod/BroilDesktop/!svn/vcc/default
>>> Could not read response body: secure connection
>>> truncated(https://svn-server.com)
>>>
>>>
>>> Solaris 10 , Subversion 1.4.3 server.
>>> SVN over https
>>>
>>> I noticed that it happens even the working copy is in the local
>>> directory
>>>
>>> Thanks
>>> Sathish
>>>
>>>
>>> -----Original Message-----
>>> From: J J [mailto:eggsgloriouseggs_at_gmail.com]
>>> Sent: 19 June 2008 14:02
>>> To: users_at_subversion.tigris.org
>>> Subject: Re: Provider encountered an error while streaming a REPORT
>>> response
>>>
>>> One other piece of information that may be helpful...
>>>
>>> The error below also only occurs when going through a content switch
>>> that redirects traffic to the server. I did some research and found
>>> that the content switch changes the IP address of the client to that
>>> of the content switch. This seems to work in general, because when we
>>> aren't checking out to a working copy stored on NAS there is no
>>> problem (that I know of), and when checking out to NAS it gets through
>>> quite a few files before this error. Does anyone know if Subversion
>>> requires the source IP of the client? Should a setup like work? Are
>>> there any other configuration changes I should be making in Apache?
>>>
>>> Justin
>>>
>>> On Wed, Jun 18, 2008 at 10:10 AM, J J <eggsgloriouseggs_at_gmail.com>
>>> wrote:
>>>> Hello,
>>>>
>>>> I have a Solaris 10 server running Subversion 1.4.5 using the provided
>>>> dependencies, served by Apache 2.2.8.
>>>>
>>>> Lately I've seen the following error occur often when performing
>>>> Subversion operations against a working copy stored on NAS. As far as
>>>> I can tell it doesn't occur in any other circumstance.
>>>>
>>>> svn: REPORT request failed on '/svn/reponame/!svn/vcc/default'
>>>> svn: REPORT of '/svn/reponame/!svn/vcc/default': Could not read
>>>> response body: An existing connection was forcibly closed by the
>>>> remote host. (http://HOSTNAME)
>>>> command exit code: 1
>>>>
>>>> In the error logs on the server I see the following at the time of the
>>> error.
>>>>
>>>> [Wed Jun 18 08:22:03 2008] [error] [client xx.xx.xx.xx] Provider
>>>> encountered an error while streaming a REPORT response. [500, #0]
>>>> [Wed Jun 18 08:22:03 2008] [error] [client xx.xx.xx.xx] A failure
>>>> occurred while driving the update report editor [500, #190004]
>>>>
>>>> I followed the instructions at
>>>> http://subversion.tigris.org/faq.html#tiger-apr-0.9.6, even though I'm
>>>> not running on a Mac, but it didn't resolve the problem.
>>>>
>>>> Does anyone have any suggestions on how I can resolve this?
>>>>
>>>> Thanks,
>>>> Justin
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
>>> For additional commands, e-mail: users-help_at_subversion.tigris.org
>>>
>>> Visit our website at http://www.ubs.com
>>>
>>> This message contains confidential information and is intended only
>>> for the individual named. If you are not the named addressee you
>>> should not disseminate, distribute or copy this e-mail. Please
>>> notify the sender immediately by e-mail if you have received this
>>> e-mail by mistake and delete this e-mail from your system.
>>>
>>> E-mails are not encrypted and cannot be guaranteed to be secure or
>>> error-free as information could be intercepted, corrupted, lost,
>>> destroyed, arrive late or incomplete, or contain viruses. The sender
>>> therefore does not accept liability for any errors or omissions in the
>>> contents of this message which arise as a result of e-mail transmission.
>>> If verification is required please request a hard-copy version. This
>>> message is provided for informational purposes and should not be
>>> construed as a solicitation or offer to buy or sell any securities
>>> or related financial instruments.
>>>
>>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-19 18:42:51 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.