On Mon, Sep 12, 2011 at 6:15 PM, Daniel Shahaf wrote:
> We bumped the SQLite requirement to the rather recent 3.6.18 because of
> bugs/features we needed.
>
> On the other hand, the minimum Python is 2.4 and the minimum APR is 0.9.
> They are old enough to go to grade school.
Well, yes. And you
t; >
> >> >> > These versions are ancient, unsupported, and contain known security
> >> >> > holes.
> >> >> >
> >> >> >> Error Logs:
> >> >> >> apache error_log: A failure occurred while driving the update
4 svn version 1.4.4 ( r25188 ) (this version is
>> >> >> REQUIRED!)
>> >> >>
>> >> >
>> >> > These versions are ancient, unsupported, and contain known security
>> >> > holes.
>> >> >
>> >> &
t; >> >>
> >> >
> >> > These versions are ancient, unsupported, and contain known security
> >> > holes.
> >> >
> >> >> Error Logs:
> >> >> apache error_log: A failure occurred while driving the update
> >>
>> Error Logs:
>> >> apache error_log: A failure occurred while driving the update report
>> >> editor
>> >> apache error_log: Provider encountered an error while streaming a
>> >> REPORT response.
>> >
>> > Run tool
date report
> >> editor
> >> apache error_log: Provider encountered an error while streaming a
> >> REPORT response.
> >
> > Run tools/dev/which-error.py on the six-digit number in the above error
> > message.
>
> Felipe, note that it's not &
gt;
> These versions are ancient, unsupported, and contain known security holes.
>
>> Error Logs:
>> apache error_log: A failure occurred while driving the update report
>> editor
>> apache error_log: Provider encountered an error while streaming a
>> REPORT
> Error Logs:
> apache error_log: A failure occurred while driving the update report
> editor
> apache error_log: Provider encountered an error while streaming a
> REPORT response.
Run tools/dev/which-error.py on the six-digit number in the above error
message.
the VPN option (the TLS/SSL option will be
investigated at a later time...)
Error Logs:
apache error_log: A failure occurred while driving the update report editor
apache error_log: Provider encountered an error while streaming a
REPORT response.
apache access_log: REPORT /svn/r
I am seeing the above error with some frequency, generally producing
the following three messages in the logs.
[Wed Nov 03 17:11:16 2010] [error] [client 10.1.3.105] Provider
encountered an error while streaming a REPORT response. [500, #0]
[Wed Nov 03 17:11:16 2010] [error] [client 10.1.3.105
Server log file:
[Thu Sep 02 11:47:07 2010] [notice] Apache/2.2.15 (Unix) DAV/2
mod_ssl/2.2.15 OpenSSL/1.0.0 SVN/1.6.11 PHP/5.2.6 mod_python/3.3.1
Python/2.3.4 configured -- resuming normal operations
[Thu Sep 02 11:52:52 2010] [error] [client 192.x.x.x] Provider
encountered an error while streamin
Johan Corveleyn wrote:
> You could be experiencing a client-side timeout. Svn with neon (which
> is the default client-side http access library) has a default timeout
> of 30 seconds. If the client doesn't get something within those 30
> seconds, it terminates the connection.
>
> You can specify a
Johan Corveleyn wrote:
>> But i did not expect success here, because the error occurred after
>> about 15 minutes what is much longer than the http-timeout.
>
> [ Remember to put the list in cc as well, so the reply goes not only to me ]
Sorry for that.
> Alternatively, in your setup (with squid
On Tue, Mar 9, 2010 at 2:37 PM, Steffen Sledz wrote:
> Johan Corveleyn wrote:
>> You could be experiencing a client-side timeout. Svn with neon (which
>> is the default client-side http access library) has a default timeout
>> of 30 seconds. If the client doesn't get something within those 30
>> s
e to enable a few extra commands.
>
> The squid works fine for a long time on all other requests
> including git-svn on smaller repositories.
>
>>> Provider encountered an error while streaming a REPORT
>>> response. [400, #0]
>>
>> Smells like a proxy/fi
smaller repositories.
>> Provider encountered an error while streaming a REPORT
>> response. [400, #0]
>
> Smells like a proxy/firewall that refuses to let something pass.
H? I don't think so. As mentioned before the procedure
works fine on smaller repos. It looks like a size/timeout
problem.
Steffen
nal error comes from the SVN-Server itself and is this one:
>
> Provider encountered an error while streaming a REPORT
> response. [400, #0]
Smells like a proxy/firewall that refuses to let something pass.
Try
- with plain svn instead of git
- via HTTP instead of HTTP
y timeout comes from a squid transparent proxy which
acts as an auth gatekeeper. The original error comes from the
SVN-Server itself and is this one:
Provider encountered an error while streaming a REPORT response. [400, #0]
Any hints how we can fix the problem?
Steffen
18 matches
Mail list logo
