RE: error - "Provider encountered an error while streaming a REPORT response. [500, #0]"

Precision.. The files in the repository are all below 2 gigabytes.. Some of them are above 1 gigabyte though..

-----Original Message-----
From: Mark Phippard [mailto:markphip_at_gmail.com]
Sent: Thursday, March 26, 2009 4:02 PM
To: Christian Pare
Cc: users_at_subversion.tigris.org
Subject: Re: error - "Provider encountered an error while streaming a REPORT response. [500, #0]"

I thought you had to be running Apache 2.2 in order to support large
files ( > 2 GB).

I am a little surprised that it would not issue an "intelligible"
error message if that was the case though.

In testing I've done, you cannot commit files > 2 GB from a Windows
client via http because the Neon library does not support this. It is
fixed for non-Windows platforms in 1.5.6+, but it still does not work
on Windows. With the SVN 1.6.0 client you can use the Serf library in
place of Neon and it works.

Mark

On Thu, Mar 26, 2009 at 3:45 PM, Christian Pare
<christian.pare_at_octasic.com> wrote:
> Hi,
>
> Our subversion's Apache service been crashing on us for the last few
> days..  Before shuting down, this is what we find in the error.log:
>
> [Wed Mar 25 18:40:58 2009] [error] [client 192.x.x.x] Provider
> encountered an error while streaming a REPORT response.  [500, #0]
> [Wed Mar 25 18:40:58 2009] [error] [client 192.x.x.x] A failure occurred
> while driving the update report editor  [500, #190004]
>
> Tracking down the 190004 code, this seems to be the error
> SVN_ERR_APMOD_CONNECTION_ABORTED.  (Not sure why the first log prints #0
> as the error code). It actually seems to be a buggy error handling
> condition in the APR/APR_SVN interface.
>
> Actually, looking at Apache's error.log, I see that the above error
> occurs from time to time, but at some point crashes the Apache service.
> Looking at the access.log file, I see that a huge transaction was
> occuring just before the crash:
>
> 192.x.x.x - abcde [25/Mar/2009:18:28:09 -0400] "REPORT
> /svn/abc/!svn/vcc/default HTTP/1.1" 200 2435626465
>
> 2435626465 -> Something like 2.3 gigz.
>
> I do not have the output from the client side.
>
> I know the repository in question is pretty large (~30 gigz), with files
> in the 1 gigabyte range, but I was wondering why the service crashed on
> long/slow transfers? Is there a limitation on the file size/transfer
> size SVN-Apache can handle?
>
> Here are the versions running:
>
> SVN server 1.5.6
> Apache 2.0.63
>  w/mod_dav_svn.so (1.5.6)
>  w/mod_authz_svn.so (1.5.6)
> Clients all in the 1.5.x series
> Server OS: Windows 2003 Standard
>
> I've searched through the user-database and found this:
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageI
> d=27833
>
> But there doesn't seem to be an actual solution to the problem. Have you
> guys ever encountered this?  Any fix/workaround?  Let me know if you
> need more information on the setup -- the condition is somewhat easy to
> reproduce.
>
> Thanks for any input!
> Christian
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1434355
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
>

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1435192
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].