Le mar 13/07/2004 à 22:30, Joe Orton a écrit :
> On Tue, Jul 13, 2004 at 03:09:50PM +0200, Xavier Brouckaert wrote:
> > xbr@bush:~/turner/papers$ svn up
> > svn: REPORT request failed on '/svn/papers/!svn/vcc/default'
> > svn: REPORT of '/svn/papers/!svn/vcc/default': Could not read response
> > body: SSL error: illegal padding (https://...)
>
> Check the server error_log, these things are usually associated with a
> "Provider encountered error streaming REPORT response" error.
>
> (in which case the SSL connection gets terminated abruptly which I
> believe causes these scary-looking errors from the SSL library)
You're right :
Provider encountered an error while streaming a REPORT response. [500,
#0]
A failure occurred while driving the update report editor [500, #103]
(84)Invalid or incomplete multibyte or wide character: Error writing
base64 data: Software caused connection abort [500, #103]
This guy has the same problem :
http://www.contactor.se/~dast/svnusers/archive-2003-12/0157.shtml
In that thread, you asked him to set LogLevel info. Unfortunately, he
didn't answer. In the meantime, I removed all the files locally (1.5
Gb) on the server that were mistakenly imported and things got working
again. (I used file:// instead of https://). So, a checkout with https
failed and a checkout with file succeeded.
The REPORT error message occured after a simple EPS file and before a
text file. Both files do not contain accentuated characters in their
names and both aren't big. I don't know if this can help.
I was wrong in my previous mail when I said that things were working
even with the error message. The connection stops after the error
message and all further updates aren't performed.
Have you an idea on how I can prevent this from arriving again ?
Thank you !,
Xavier
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 14 11:00:43 2004