You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Justin <ju...@hush.cc> on 2006/09/27 20:08:49 UTC
Help! REPORT fail & SSL error...
Hi everyone,
Out of the blue, after over 150 revisions in our repository, we ran
into this error trying to checkout a revision:
subversion/libsvn_ra_dav/util.c:826: (apr_err=175002)
svn: REPORT request failed on '/svn/!svn/vcc/default'
subversion/libsvn_ra_dav/util.c:296: (apr_err=175002)
svn: REPORT of '/svn/!svn/vcc/default': Could not read response body:
SSL error: decryption failed or bad record mac (https://my.ip.goes.here)
Checkout start grabbing a handful of parts of the revision, but then
fails with this error. In the log itself, this error is FIRST before
the list of "A /Path/to/the/bitsAndPieces", FWIW.
Nothing changed on the server, other than one of our devs grabbing
our whole repository folder for the purposes of an off-site backup,
which they've done before. This is on OS X Server running Apache2 and
SSL, with a self-signed certificate. Googled the parts of the error
but nothing seems too helpful.
We're coming up on milestones, so I need to get this fixed ASAP. Any
help would be so greatly appreciated, as I'm very new at SubVersion.
Thanks so much!
*justin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Justin <ju...@hush.cc>.
Hi again,
Turns out that this problem may (also?) be related to OpenSSL,
although again, nothing changed in regards to the SSL setup - but the
error is one that has ties to OpenSSL. I'm able to checkout
subfolders of our main project, but not the whole thing - other folks
have had similar problems, but the info I found on their issues ended
up being related to them updating OpenSSL to 0.9.8. The fix was
downgrading to 0.9.7 - I already have 0.9.7i.
As I work for a developer/publisher, I'd be happy to send a bunch of
OS X software to anyone that can save me from an all-nighter... not
that there's much information on the problem to go though - Google
doesn't turn up more than 2 or 3 pages depending on the query. =)
Thanks as always,
*justin
On Sep 27, 2006, at 6:09 PM, Justin wrote:
> Hi listers,
>
> Also FWIW, attempting to checkout another "test" project that only
> has four tiny tiny text files in it, works perfectly. It's just the
> main, big project that I receive the error below with.
>
> Thanks,
>
> *justin
>
> On Sep 27, 2006, at 5:51 PM, Samay wrote:
>
>> are u able to access https://ip.ad.dr.ess/pathtorepo/ through your
>> web browser ... whats the error there? then try https://
>> ip.ad.dr.ess/somelocal.file/ via ur web browser? do both work?
>>
>>
>> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
>> To: <us...@subversion.tigris.org>
>> Cc: "Garrett Rooney" <ro...@electricjellyfish.net>
>> Sent: Thursday, September 28, 2006 7:31 AM
>> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>>
>>
>>> Hi Garrett,
>>>
>>> Trying it locally (using https://127.0.0.1/pathToRepository)
>>> results in the same error message actually! I'm thinking about
>>> recreating the self-signed certificate in the meantime, while I
>>> wait to see if anyone else has some input on the issue...
>>>
>>> Thanks a ton!
>>>
>>> *justin
>>>
>>>
>>> On Sep 27, 2006, at 5:20 PM, Garrett Rooney wrote:
>>>
>>>> On 9/27/06, Justin <ju...@hush.cc> wrote:
>>>>> Hey again everyone,
>>>>>
>>>>> Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
>>>>> server. So, updated the server to 1.4.0 and the clients expecting
>>>>> things to work... while the error I'm getting is now smaller, this
>>>>> part of the error still exists:
>>>>>
>>>>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>>>>> svn: REPORT of '/svn/!svn/vcc/default': Could not read response
>>>>> body:
>>>>> SSL error: decryption failed or bad record mac (https://
>>>>> my.ip.goes.here)
>>>>>
>>>>> I'm seriously running into a lack of information on this error,
>>>>> despite people reporting it. Does anyone have any ideas? =
>>>>> ( I'm
>>>>> gearing up for an all-nighter here because I have to have this
>>>>> working...
>>>>
>>>> If I had to guess I'd say you should start looking for something
>>>> between the client and the server that's causing problems. Does
>>>> this
>>>> happen if you run the command right on the server, not going
>>>> over the
>>>> network at all?
>>>>
>>>> -garrett
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Justin <ju...@hush.cc>.
Hi listers,
Also FWIW, attempting to checkout another "test" project that only
has four tiny tiny text files in it, works perfectly. It's just the
main, big project that I receive the error below with.
Thanks,
*justin
On Sep 27, 2006, at 5:51 PM, Samay wrote:
> are u able to access https://ip.ad.dr.ess/pathtorepo/ through your
> web browser ... whats the error there? then try https://
> ip.ad.dr.ess/somelocal.file/ via ur web browser? do both work?
>
>
> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
> To: <us...@subversion.tigris.org>
> Cc: "Garrett Rooney" <ro...@electricjellyfish.net>
> Sent: Thursday, September 28, 2006 7:31 AM
> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>
>
>> Hi Garrett,
>>
>> Trying it locally (using https://127.0.0.1/pathToRepository)
>> results in the same error message actually! I'm thinking about
>> recreating the self-signed certificate in the meantime, while I
>> wait to see if anyone else has some input on the issue...
>>
>> Thanks a ton!
>>
>> *justin
>>
>>
>> On Sep 27, 2006, at 5:20 PM, Garrett Rooney wrote:
>>
>>> On 9/27/06, Justin <ju...@hush.cc> wrote:
>>>> Hey again everyone,
>>>>
>>>> Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
>>>> server. So, updated the server to 1.4.0 and the clients expecting
>>>> things to work... while the error I'm getting is now smaller, this
>>>> part of the error still exists:
>>>>
>>>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>>>> svn: REPORT of '/svn/!svn/vcc/default': Could not read response
>>>> body:
>>>> SSL error: decryption failed or bad record mac (https://
>>>> my.ip.goes.here)
>>>>
>>>> I'm seriously running into a lack of information on this error,
>>>> despite people reporting it. Does anyone have any ideas? =( I'm
>>>> gearing up for an all-nighter here because I have to have this
>>>> working...
>>>
>>> If I had to guess I'd say you should start looking for something
>>> between the client and the server that's causing problems. Does
>>> this
>>> happen if you run the command right on the server, not going over
>>> the
>>> network at all?
>>>
>>> -garrett
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Konrad Rosenbaum <ko...@silmor.de>.
Hi,
just out of a whim:
Is the harddisk with the repository or working copy full?
What about the one with the /tmp directory? (Or whatever the correct name
for the temporary files dir is on MacOS.)
Did you set up some kind of size limit inside Apache or for the repository?
On Thursday 28 September 2006 16:22, Justin wrote:
> Tried it, but still the same problem. I did some more testing - it
> looks like, out of 153 revisions, checkout fails STARTING at revision
> 151. This was the only checkin made by a developer that does NOT
> usually use the server - this was his first checkin. 152 and 153
> experience the same checkout problems, but everything BEFORE 151
> checks out perfectly!
Check the permissions of all files in the repository. Make sure Apache has
full read/write access to them.
Konrad
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Samay <ge...@hotmail.com>.
hv u access to repository on the server, u may try the exact checkout using
file:/// method to verify that repository is not corrupt and issue is
transport related.
BTW, any similarity to http://svn.haxx.se/users/archive-2006-09/1364.shtml
only relevant if client is 1.4.x build with neon 0.25+ and authentication is
GSSAPI based. Above problem does result in partial checkouts.
----- Original Message -----
From: "Justin" <ju...@hush.cc>
To: <us...@subversion.tigris.org>
Cc: "Samay" <ge...@hotmail.com>
Sent: Friday, September 29, 2006 12:22 AM
Subject: Re: Help! REPORT fail & SSL error... UPDATE
> Shirish,
>
> Tried it, but still the same problem. I did some more testing - it looks
> like, out of 153 revisions, checkout fails STARTING at revision 151. This
> was the only checkin made by a developer that does NOT usually use the
> server - this was his first checkin. 152 and 153 experience the same
> checkout problems, but everything BEFORE 151 checks out perfectly!
>
> What might have been the cause of this, any ideas? I'm waiting for him to
> get in to find out what (if any) GUI client he was using, but he was
> definitely using SubVersion 1.4.0 on Windows XP. Corrupt data perhaps?
> I'm really not sure, as svn READS the info about the revision fine, but
> just refuses to checkout - a checkout of this funky revision 151 checks
> out about 49 out of 68 files before failing, and always the same 49.
>
> Thanks a lot,
>
> *justin
>
> On Sep 27, 2006, at 10:56 PM, Samay wrote:
>
>> it may be worthwhile to try a fresh client with SVN 1.3.x Neon 0.25.x
>> one and see if error persists. My guess is, its the same error that has
>> been haunting me for past few days (search for thread "Possible bug in
>> win32- 1.4.0 when accessing repository via https", just a different
>> symptom! Our only way out was downgrade SVN clients to 1.3.x except
>> 1.4.x TSVN.
>>
>> BTW, Authz is for AUthorization.
>>
>> cheers
>>
>> Shirish
>>
>>
>> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
>> To: <us...@subversion.tigris.org>
>> Cc: "Samay" <ge...@hotmail.com>
>> Sent: Thursday, September 28, 2006 12:48 PM
>> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>>
>>
>>> Hi Samay,
>>>
>>> Client-side, it's nothing odd. The server is serving repositories via
>>> HTTPS over Apache2 - in fact, that's all Apache2 is doing, so the
>>> setup is very straightforward. Client-side, we're using bith built and
>>> binary installs of SubVersion, on OS X and Windows. Authentication is
>>> via Apache2 - I forget what that method is called (authz?) - it's the
>>> method recommended in the online SVN book though.
>>>
>>> And it's always worked! Until now. A few days ago I had a dev install
>>> 1.4.0 without my knowledge - and now, problems. Server and clients
>>> were always 1.3.latest-before-1.4.0. Apache/SSL logs give the errors
>>> that are consistent with this SVN error - "cannot write base64 data"
>>> or something (sorry I'm at home now, I'll e- mail the exact messages
>>> tomorrow morning).
>>>
>>> Thanks, I appreciate it. Might anyone have a SubVersion developer's e-
>>> mail? This seems like a problem that pops up once in a while with NO
>>> solution anywhere online... =\ but it's been reported a bunch of
>>> times before!
>>>
>>> *justin
>>>
>>>
>>> On Sep 27, 2006, at 9:40 PM, Samay wrote:
>>>
>>>> so its may not be a server side issue then ... could you please
>>>> describe your client side environment & ur authentication schema on
>>>> the server side? is it "Kerberos/SSPI" based, if yes, it probably
>>>> will not work with 1.4.x SVN client. It seems to be royally broken!
>>>>
>>>>
>>>> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
>>>> To: <us...@subversion.tigris.org>
>>>> Cc: "Samay" <ge...@hotmail.com>
>>>> Sent: Thursday, September 28, 2006 8:04 AM
>>>> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>>>>
>>>>
>>>>> Hi Samay,
>>>>>
>>>>> THAT works perfectly - no errors at all.
>>>>>
>>>>> On a whim, I recreated the ssl certificate - nothing has changed at
>>>>> all, so it's basically the same certificate that was already in
>>>>> place. That didn't alleviate the issue. Now, 1.4.0's release notes
>>>>> don't say a thing about changes to the way certificates are handled,
>>>>> so I think I can rule out problems with the certificates.
>>>>>
>>>>> Looks like I'll be here a _while_ so I greatly appreciate any info
>>>>> that you listers have on this. Thanks!
>>>>>
>>>>> *justin
>>>>>
>>>>>
>>>>> On Sep 27, 2006, at 5:51 PM, Samay wrote:
>>>>>
>>>>>> are u able to access https://ip.ad.dr.ess/pathtorepo/ through your
>>>>>> web browser ... whats the error there? then try https://
>>>>>> ip.ad.dr.ess/somelocal.file/ via ur web browser? do both work?
>>>>>>
>>>>>>
>>>>>> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
>>>>>> To: <us...@subversion.tigris.org>
>>>>>> Cc: "Garrett Rooney" <ro...@electricjellyfish.net>
>>>>>> Sent: Thursday, September 28, 2006 7:31 AM
>>>>>> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>>>>>>
>>>>>>
>>>>>>> Hi Garrett,
>>>>>>>
>>>>>>> Trying it locally (using https://127.0.0.1/pathToRepository)
>>>>>>> results in the same error message actually! I'm thinking about
>>>>>>> recreating the self-signed certificate in the meantime, while I
>>>>>>> wait to see if anyone else has some input on the issue...
>>>>>>>
>>>>>>> Thanks a ton!
>>>>>>>
>>>>>>> *justin
>>>>>>>
>>>>>>>
>>>>>>> On Sep 27, 2006, at 5:20 PM, Garrett Rooney wrote:
>>>>>>>
>>>>>>>> On 9/27/06, Justin <ju...@hush.cc> wrote:
>>>>>>>>> Hey again everyone,
>>>>>>>>>
>>>>>>>>> Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
>>>>>>>>> server. So, updated the server to 1.4.0 and the clients expecting
>>>>>>>>> things to work... while the error I'm getting is now smaller,
>>>>>>>>> this
>>>>>>>>> part of the error still exists:
>>>>>>>>>
>>>>>>>>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>>>>>>>>> svn: REPORT of '/svn/!svn/vcc/default': Could not read response
>>>>>>>>> body:
>>>>>>>>> SSL error: decryption failed or bad record mac (https://
>>>>>>>>> my.ip.goes.here)
>>>>>>>>>
>>>>>>>>> I'm seriously running into a lack of information on this error,
>>>>>>>>> despite people reporting it. Does anyone have any ideas? =
>>>>>>>>> ( I'm
>>>>>>>>> gearing up for an all-nighter here because I have to have this
>>>>>>>>> working...
>>>>>>>>
>>>>>>>> If I had to guess I'd say you should start looking for something
>>>>>>>> between the client and the server that's causing problems. Does
>>>>>>>> this
>>>>>>>> happen if you run the command right on the server, not going over
>>>>>>>> the
>>>>>>>> network at all?
>>>>>>>>
>>>>>>>> -garrett
>>>>>>>
>>>>>>> -----------------------------------------------------------------
>>>>>>> -- --
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>>>>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------
>>>>>> -- -
>>>>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>>>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> --
>>>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Justin <ju...@hush.cc>.
Shirish,
Tried it, but still the same problem. I did some more testing - it
looks like, out of 153 revisions, checkout fails STARTING at revision
151. This was the only checkin made by a developer that does NOT
usually use the server - this was his first checkin. 152 and 153
experience the same checkout problems, but everything BEFORE 151
checks out perfectly!
What might have been the cause of this, any ideas? I'm waiting for
him to get in to find out what (if any) GUI client he was using, but
he was definitely using SubVersion 1.4.0 on Windows XP. Corrupt data
perhaps? I'm really not sure, as svn READS the info about the
revision fine, but just refuses to checkout - a checkout of this
funky revision 151 checks out about 49 out of 68 files before
failing, and always the same 49.
Thanks a lot,
*justin
On Sep 27, 2006, at 10:56 PM, Samay wrote:
> it may be worthwhile to try a fresh client with SVN 1.3.x Neon
> 0.25.x one and see if error persists. My guess is, its the same
> error that has been haunting me for past few days (search for
> thread "Possible bug in win32- 1.4.0 when accessing repository via
> https", just a different symptom! Our only way out was downgrade
> SVN clients to 1.3.x except 1.4.x TSVN.
>
> BTW, Authz is for AUthorization.
>
> cheers
>
> Shirish
>
>
> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
> To: <us...@subversion.tigris.org>
> Cc: "Samay" <ge...@hotmail.com>
> Sent: Thursday, September 28, 2006 12:48 PM
> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>
>
>> Hi Samay,
>>
>> Client-side, it's nothing odd. The server is serving repositories
>> via HTTPS over Apache2 - in fact, that's all Apache2 is doing, so
>> the setup is very straightforward. Client-side, we're using bith
>> built and binary installs of SubVersion, on OS X and Windows.
>> Authentication is via Apache2 - I forget what that method is
>> called (authz?) - it's the method recommended in the online SVN
>> book though.
>>
>> And it's always worked! Until now. A few days ago I had a dev
>> install 1.4.0 without my knowledge - and now, problems. Server and
>> clients were always 1.3.latest-before-1.4.0. Apache/SSL logs give
>> the errors that are consistent with this SVN error - "cannot
>> write base64 data" or something (sorry I'm at home now, I'll e-
>> mail the exact messages tomorrow morning).
>>
>> Thanks, I appreciate it. Might anyone have a SubVersion
>> developer's e- mail? This seems like a problem that pops up once
>> in a while with NO solution anywhere online... =\ but it's
>> been reported a bunch of times before!
>>
>> *justin
>>
>>
>> On Sep 27, 2006, at 9:40 PM, Samay wrote:
>>
>>> so its may not be a server side issue then ... could you please
>>> describe your client side environment & ur authentication schema
>>> on the server side? is it "Kerberos/SSPI" based, if yes, it
>>> probably will not work with 1.4.x SVN client. It seems to be
>>> royally broken!
>>>
>>>
>>> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
>>> To: <us...@subversion.tigris.org>
>>> Cc: "Samay" <ge...@hotmail.com>
>>> Sent: Thursday, September 28, 2006 8:04 AM
>>> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>>>
>>>
>>>> Hi Samay,
>>>>
>>>> THAT works perfectly - no errors at all.
>>>>
>>>> On a whim, I recreated the ssl certificate - nothing has
>>>> changed at all, so it's basically the same certificate that was
>>>> already in place. That didn't alleviate the issue. Now,
>>>> 1.4.0's release notes don't say a thing about changes to the
>>>> way certificates are handled, so I think I can rule out
>>>> problems with the certificates.
>>>>
>>>> Looks like I'll be here a _while_ so I greatly appreciate any
>>>> info that you listers have on this. Thanks!
>>>>
>>>> *justin
>>>>
>>>>
>>>> On Sep 27, 2006, at 5:51 PM, Samay wrote:
>>>>
>>>>> are u able to access https://ip.ad.dr.ess/pathtorepo/ through
>>>>> your web browser ... whats the error there? then try https://
>>>>> ip.ad.dr.ess/somelocal.file/ via ur web browser? do both work?
>>>>>
>>>>>
>>>>> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
>>>>> To: <us...@subversion.tigris.org>
>>>>> Cc: "Garrett Rooney" <ro...@electricjellyfish.net>
>>>>> Sent: Thursday, September 28, 2006 7:31 AM
>>>>> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>>>>>
>>>>>
>>>>>> Hi Garrett,
>>>>>>
>>>>>> Trying it locally (using https://127.0.0.1/pathToRepository)
>>>>>> results in the same error message actually! I'm thinking
>>>>>> about recreating the self-signed certificate in the
>>>>>> meantime, while I wait to see if anyone else has some input
>>>>>> on the issue...
>>>>>>
>>>>>> Thanks a ton!
>>>>>>
>>>>>> *justin
>>>>>>
>>>>>>
>>>>>> On Sep 27, 2006, at 5:20 PM, Garrett Rooney wrote:
>>>>>>
>>>>>>> On 9/27/06, Justin <ju...@hush.cc> wrote:
>>>>>>>> Hey again everyone,
>>>>>>>>
>>>>>>>> Turns out one of our devs used SubVersion 1.4.0 on our
>>>>>>>> 1.3.latest
>>>>>>>> server. So, updated the server to 1.4.0 and the clients
>>>>>>>> expecting
>>>>>>>> things to work... while the error I'm getting is now
>>>>>>>> smaller, this
>>>>>>>> part of the error still exists:
>>>>>>>>
>>>>>>>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>>>>>>>> svn: REPORT of '/svn/!svn/vcc/default': Could not read
>>>>>>>> response body:
>>>>>>>> SSL error: decryption failed or bad record mac (https://
>>>>>>>> my.ip.goes.here)
>>>>>>>>
>>>>>>>> I'm seriously running into a lack of information on this error,
>>>>>>>> despite people reporting it. Does anyone have any ideas? =
>>>>>>>> ( I'm
>>>>>>>> gearing up for an all-nighter here because I have to have this
>>>>>>>> working...
>>>>>>>
>>>>>>> If I had to guess I'd say you should start looking for something
>>>>>>> between the client and the server that's causing problems.
>>>>>>> Does this
>>>>>>> happen if you run the command right on the server, not going
>>>>>>> over the
>>>>>>> network at all?
>>>>>>>
>>>>>>> -garrett
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> -- --
>>>>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>>>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -- -
>>>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Samay <ge...@hotmail.com>.
it may be worthwhile to try a fresh client with SVN 1.3.x Neon 0.25.x one
and see if error persists. My guess is, its the same error that has been
haunting me for past few days (search for thread "Possible bug in win32-
1.4.0 when accessing repository via https", just a different symptom! Our
only way out was downgrade SVN clients to 1.3.x except 1.4.x TSVN.
BTW, Authz is for AUthorization.
cheers
Shirish
----- Original Message -----
From: "Justin" <ju...@hush.cc>
To: <us...@subversion.tigris.org>
Cc: "Samay" <ge...@hotmail.com>
Sent: Thursday, September 28, 2006 12:48 PM
Subject: Re: Help! REPORT fail & SSL error... UPDATE
> Hi Samay,
>
> Client-side, it's nothing odd. The server is serving repositories via
> HTTPS over Apache2 - in fact, that's all Apache2 is doing, so the setup
> is very straightforward. Client-side, we're using bith built and binary
> installs of SubVersion, on OS X and Windows. Authentication is via
> Apache2 - I forget what that method is called (authz?) - it's the method
> recommended in the online SVN book though.
>
> And it's always worked! Until now. A few days ago I had a dev install
> 1.4.0 without my knowledge - and now, problems. Server and clients were
> always 1.3.latest-before-1.4.0. Apache/SSL logs give the errors that are
> consistent with this SVN error - "cannot write base64 data" or something
> (sorry I'm at home now, I'll e-mail the exact messages tomorrow morning).
>
> Thanks, I appreciate it. Might anyone have a SubVersion developer's e-
> mail? This seems like a problem that pops up once in a while with NO
> solution anywhere online... =\ but it's been reported a bunch of
> times before!
>
> *justin
>
>
> On Sep 27, 2006, at 9:40 PM, Samay wrote:
>
>> so its may not be a server side issue then ... could you please describe
>> your client side environment & ur authentication schema on the server
>> side? is it "Kerberos/SSPI" based, if yes, it probably will not work
>> with 1.4.x SVN client. It seems to be royally broken!
>>
>>
>> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
>> To: <us...@subversion.tigris.org>
>> Cc: "Samay" <ge...@hotmail.com>
>> Sent: Thursday, September 28, 2006 8:04 AM
>> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>>
>>
>>> Hi Samay,
>>>
>>> THAT works perfectly - no errors at all.
>>>
>>> On a whim, I recreated the ssl certificate - nothing has changed at
>>> all, so it's basically the same certificate that was already in place.
>>> That didn't alleviate the issue. Now, 1.4.0's release notes don't say
>>> a thing about changes to the way certificates are handled, so I think
>>> I can rule out problems with the certificates.
>>>
>>> Looks like I'll be here a _while_ so I greatly appreciate any info
>>> that you listers have on this. Thanks!
>>>
>>> *justin
>>>
>>>
>>> On Sep 27, 2006, at 5:51 PM, Samay wrote:
>>>
>>>> are u able to access https://ip.ad.dr.ess/pathtorepo/ through your
>>>> web browser ... whats the error there? then try https://
>>>> ip.ad.dr.ess/somelocal.file/ via ur web browser? do both work?
>>>>
>>>>
>>>> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
>>>> To: <us...@subversion.tigris.org>
>>>> Cc: "Garrett Rooney" <ro...@electricjellyfish.net>
>>>> Sent: Thursday, September 28, 2006 7:31 AM
>>>> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>>>>
>>>>
>>>>> Hi Garrett,
>>>>>
>>>>> Trying it locally (using https://127.0.0.1/pathToRepository) results
>>>>> in the same error message actually! I'm thinking about recreating
>>>>> the self-signed certificate in the meantime, while I wait to see if
>>>>> anyone else has some input on the issue...
>>>>>
>>>>> Thanks a ton!
>>>>>
>>>>> *justin
>>>>>
>>>>>
>>>>> On Sep 27, 2006, at 5:20 PM, Garrett Rooney wrote:
>>>>>
>>>>>> On 9/27/06, Justin <ju...@hush.cc> wrote:
>>>>>>> Hey again everyone,
>>>>>>>
>>>>>>> Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
>>>>>>> server. So, updated the server to 1.4.0 and the clients expecting
>>>>>>> things to work... while the error I'm getting is now smaller, this
>>>>>>> part of the error still exists:
>>>>>>>
>>>>>>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>>>>>>> svn: REPORT of '/svn/!svn/vcc/default': Could not read response
>>>>>>> body:
>>>>>>> SSL error: decryption failed or bad record mac (https://
>>>>>>> my.ip.goes.here)
>>>>>>>
>>>>>>> I'm seriously running into a lack of information on this error,
>>>>>>> despite people reporting it. Does anyone have any ideas? = ( I'm
>>>>>>> gearing up for an all-nighter here because I have to have this
>>>>>>> working...
>>>>>>
>>>>>> If I had to guess I'd say you should start looking for something
>>>>>> between the client and the server that's causing problems. Does
>>>>>> this
>>>>>> happen if you run the command right on the server, not going over
>>>>>> the
>>>>>> network at all?
>>>>>>
>>>>>> -garrett
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> --
>>>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Justin <ju...@hush.cc>.
Hi Samay,
Client-side, it's nothing odd. The server is serving repositories via
HTTPS over Apache2 - in fact, that's all Apache2 is doing, so the
setup is very straightforward. Client-side, we're using bith built
and binary installs of SubVersion, on OS X and Windows.
Authentication is via Apache2 - I forget what that method is called
(authz?) - it's the method recommended in the online SVN book though.
And it's always worked! Until now. A few days ago I had a dev install
1.4.0 without my knowledge - and now, problems. Server and clients
were always 1.3.latest-before-1.4.0. Apache/SSL logs give the errors
that are consistent with this SVN error - "cannot write base64 data"
or something (sorry I'm at home now, I'll e-mail the exact messages
tomorrow morning).
Thanks, I appreciate it. Might anyone have a SubVersion developer's e-
mail? This seems like a problem that pops up once in a while with NO
solution anywhere online... =\ but it's been reported a bunch of
times before!
*justin
On Sep 27, 2006, at 9:40 PM, Samay wrote:
> so its may not be a server side issue then ... could you please
> describe your client side environment & ur authentication schema on
> the server side? is it "Kerberos/SSPI" based, if yes, it probably
> will not work with 1.4.x SVN client. It seems to be royally broken!
>
>
> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
> To: <us...@subversion.tigris.org>
> Cc: "Samay" <ge...@hotmail.com>
> Sent: Thursday, September 28, 2006 8:04 AM
> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>
>
>> Hi Samay,
>>
>> THAT works perfectly - no errors at all.
>>
>> On a whim, I recreated the ssl certificate - nothing has changed
>> at all, so it's basically the same certificate that was already
>> in place. That didn't alleviate the issue. Now, 1.4.0's release
>> notes don't say a thing about changes to the way certificates are
>> handled, so I think I can rule out problems with the certificates.
>>
>> Looks like I'll be here a _while_ so I greatly appreciate any
>> info that you listers have on this. Thanks!
>>
>> *justin
>>
>>
>> On Sep 27, 2006, at 5:51 PM, Samay wrote:
>>
>>> are u able to access https://ip.ad.dr.ess/pathtorepo/ through
>>> your web browser ... whats the error there? then try https://
>>> ip.ad.dr.ess/somelocal.file/ via ur web browser? do both work?
>>>
>>>
>>> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
>>> To: <us...@subversion.tigris.org>
>>> Cc: "Garrett Rooney" <ro...@electricjellyfish.net>
>>> Sent: Thursday, September 28, 2006 7:31 AM
>>> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>>>
>>>
>>>> Hi Garrett,
>>>>
>>>> Trying it locally (using https://127.0.0.1/pathToRepository)
>>>> results in the same error message actually! I'm thinking about
>>>> recreating the self-signed certificate in the meantime, while I
>>>> wait to see if anyone else has some input on the issue...
>>>>
>>>> Thanks a ton!
>>>>
>>>> *justin
>>>>
>>>>
>>>> On Sep 27, 2006, at 5:20 PM, Garrett Rooney wrote:
>>>>
>>>>> On 9/27/06, Justin <ju...@hush.cc> wrote:
>>>>>> Hey again everyone,
>>>>>>
>>>>>> Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
>>>>>> server. So, updated the server to 1.4.0 and the clients expecting
>>>>>> things to work... while the error I'm getting is now smaller,
>>>>>> this
>>>>>> part of the error still exists:
>>>>>>
>>>>>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>>>>>> svn: REPORT of '/svn/!svn/vcc/default': Could not read
>>>>>> response body:
>>>>>> SSL error: decryption failed or bad record mac (https://
>>>>>> my.ip.goes.here)
>>>>>>
>>>>>> I'm seriously running into a lack of information on this error,
>>>>>> despite people reporting it. Does anyone have any ideas? =
>>>>>> ( I'm
>>>>>> gearing up for an all-nighter here because I have to have this
>>>>>> working...
>>>>>
>>>>> If I had to guess I'd say you should start looking for something
>>>>> between the client and the server that's causing problems.
>>>>> Does this
>>>>> happen if you run the command right on the server, not going
>>>>> over the
>>>>> network at all?
>>>>>
>>>>> -garrett
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Samay <ge...@hotmail.com>.
so its may not be a server side issue then ... could you please describe
your client side environment & ur authentication schema on the server side?
is it "Kerberos/SSPI" based, if yes, it probably will not work with 1.4.x
SVN client. It seems to be royally broken!
----- Original Message -----
From: "Justin" <ju...@hush.cc>
To: <us...@subversion.tigris.org>
Cc: "Samay" <ge...@hotmail.com>
Sent: Thursday, September 28, 2006 8:04 AM
Subject: Re: Help! REPORT fail & SSL error... UPDATE
> Hi Samay,
>
> THAT works perfectly - no errors at all.
>
> On a whim, I recreated the ssl certificate - nothing has changed at all,
> so it's basically the same certificate that was already in place. That
> didn't alleviate the issue. Now, 1.4.0's release notes don't say a thing
> about changes to the way certificates are handled, so I think I can rule
> out problems with the certificates.
>
> Looks like I'll be here a _while_ so I greatly appreciate any info that
> you listers have on this. Thanks!
>
> *justin
>
>
> On Sep 27, 2006, at 5:51 PM, Samay wrote:
>
>> are u able to access https://ip.ad.dr.ess/pathtorepo/ through your web
>> browser ... whats the error there? then try https://
>> ip.ad.dr.ess/somelocal.file/ via ur web browser? do both work?
>>
>>
>> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
>> To: <us...@subversion.tigris.org>
>> Cc: "Garrett Rooney" <ro...@electricjellyfish.net>
>> Sent: Thursday, September 28, 2006 7:31 AM
>> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>>
>>
>>> Hi Garrett,
>>>
>>> Trying it locally (using https://127.0.0.1/pathToRepository) results
>>> in the same error message actually! I'm thinking about recreating the
>>> self-signed certificate in the meantime, while I wait to see if anyone
>>> else has some input on the issue...
>>>
>>> Thanks a ton!
>>>
>>> *justin
>>>
>>>
>>> On Sep 27, 2006, at 5:20 PM, Garrett Rooney wrote:
>>>
>>>> On 9/27/06, Justin <ju...@hush.cc> wrote:
>>>>> Hey again everyone,
>>>>>
>>>>> Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
>>>>> server. So, updated the server to 1.4.0 and the clients expecting
>>>>> things to work... while the error I'm getting is now smaller, this
>>>>> part of the error still exists:
>>>>>
>>>>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>>>>> svn: REPORT of '/svn/!svn/vcc/default': Could not read response body:
>>>>> SSL error: decryption failed or bad record mac (https://
>>>>> my.ip.goes.here)
>>>>>
>>>>> I'm seriously running into a lack of information on this error,
>>>>> despite people reporting it. Does anyone have any ideas? =( I'm
>>>>> gearing up for an all-nighter here because I have to have this
>>>>> working...
>>>>
>>>> If I had to guess I'd say you should start looking for something
>>>> between the client and the server that's causing problems. Does this
>>>> happen if you run the command right on the server, not going over the
>>>> network at all?
>>>>
>>>> -garrett
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Justin <ju...@hush.cc>.
Hi Samay,
THAT works perfectly - no errors at all.
On a whim, I recreated the ssl certificate - nothing has changed at
all, so it's basically the same certificate that was already in
place. That didn't alleviate the issue. Now, 1.4.0's release notes
don't say a thing about changes to the way certificates are handled,
so I think I can rule out problems with the certificates.
Looks like I'll be here a _while_ so I greatly appreciate any info
that you listers have on this. Thanks!
*justin
On Sep 27, 2006, at 5:51 PM, Samay wrote:
> are u able to access https://ip.ad.dr.ess/pathtorepo/ through your
> web browser ... whats the error there? then try https://
> ip.ad.dr.ess/somelocal.file/ via ur web browser? do both work?
>
>
> ----- Original Message ----- From: "Justin" <ju...@hush.cc>
> To: <us...@subversion.tigris.org>
> Cc: "Garrett Rooney" <ro...@electricjellyfish.net>
> Sent: Thursday, September 28, 2006 7:31 AM
> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>
>
>> Hi Garrett,
>>
>> Trying it locally (using https://127.0.0.1/pathToRepository)
>> results in the same error message actually! I'm thinking about
>> recreating the self-signed certificate in the meantime, while I
>> wait to see if anyone else has some input on the issue...
>>
>> Thanks a ton!
>>
>> *justin
>>
>>
>> On Sep 27, 2006, at 5:20 PM, Garrett Rooney wrote:
>>
>>> On 9/27/06, Justin <ju...@hush.cc> wrote:
>>>> Hey again everyone,
>>>>
>>>> Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
>>>> server. So, updated the server to 1.4.0 and the clients expecting
>>>> things to work... while the error I'm getting is now smaller, this
>>>> part of the error still exists:
>>>>
>>>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>>>> svn: REPORT of '/svn/!svn/vcc/default': Could not read response
>>>> body:
>>>> SSL error: decryption failed or bad record mac (https://
>>>> my.ip.goes.here)
>>>>
>>>> I'm seriously running into a lack of information on this error,
>>>> despite people reporting it. Does anyone have any ideas? =( I'm
>>>> gearing up for an all-nighter here because I have to have this
>>>> working...
>>>
>>> If I had to guess I'd say you should start looking for something
>>> between the client and the server that's causing problems. Does
>>> this
>>> happen if you run the command right on the server, not going over
>>> the
>>> network at all?
>>>
>>> -garrett
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Samay <ge...@hotmail.com>.
are u able to access https://ip.ad.dr.ess/pathtorepo/ through your web
browser ... whats the error there? then try
https://ip.ad.dr.ess/somelocal.file/ via ur web browser? do both work?
----- Original Message -----
From: "Justin" <ju...@hush.cc>
To: <us...@subversion.tigris.org>
Cc: "Garrett Rooney" <ro...@electricjellyfish.net>
Sent: Thursday, September 28, 2006 7:31 AM
Subject: Re: Help! REPORT fail & SSL error... UPDATE
> Hi Garrett,
>
> Trying it locally (using https://127.0.0.1/pathToRepository) results in
> the same error message actually! I'm thinking about recreating the
> self-signed certificate in the meantime, while I wait to see if anyone
> else has some input on the issue...
>
> Thanks a ton!
>
> *justin
>
>
> On Sep 27, 2006, at 5:20 PM, Garrett Rooney wrote:
>
>> On 9/27/06, Justin <ju...@hush.cc> wrote:
>>> Hey again everyone,
>>>
>>> Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
>>> server. So, updated the server to 1.4.0 and the clients expecting
>>> things to work... while the error I'm getting is now smaller, this
>>> part of the error still exists:
>>>
>>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>>> svn: REPORT of '/svn/!svn/vcc/default': Could not read response body:
>>> SSL error: decryption failed or bad record mac (https://
>>> my.ip.goes.here)
>>>
>>> I'm seriously running into a lack of information on this error,
>>> despite people reporting it. Does anyone have any ideas? =( I'm
>>> gearing up for an all-nighter here because I have to have this
>>> working...
>>
>> If I had to guess I'd say you should start looking for something
>> between the client and the server that's causing problems. Does this
>> happen if you run the command right on the server, not going over the
>> network at all?
>>
>> -garrett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Justin <ju...@hush.cc>.
Hi Garrett,
Trying it locally (using https://127.0.0.1/pathToRepository) results
in the same error message actually! I'm thinking about recreating the
self-signed certificate in the meantime, while I wait to see if
anyone else has some input on the issue...
Thanks a ton!
*justin
On Sep 27, 2006, at 5:20 PM, Garrett Rooney wrote:
> On 9/27/06, Justin <ju...@hush.cc> wrote:
>> Hey again everyone,
>>
>> Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
>> server. So, updated the server to 1.4.0 and the clients expecting
>> things to work... while the error I'm getting is now smaller, this
>> part of the error still exists:
>>
>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>> svn: REPORT of '/svn/!svn/vcc/default': Could not read response body:
>> SSL error: decryption failed or bad record mac (https://
>> my.ip.goes.here)
>>
>> I'm seriously running into a lack of information on this error,
>> despite people reporting it. Does anyone have any ideas? =( I'm
>> gearing up for an all-nighter here because I have to have this
>> working...
>
> If I had to guess I'd say you should start looking for something
> between the client and the server that's causing problems. Does this
> happen if you run the command right on the server, not going over the
> network at all?
>
> -garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Help! REPORT fail & SSL error... UPDATE
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 9/27/06, Justin <ju...@hush.cc> wrote:
> Hey again everyone,
>
> Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
> server. So, updated the server to 1.4.0 and the clients expecting
> things to work... while the error I'm getting is now smaller, this
> part of the error still exists:
>
> svn: REPORT request failed on '/svn/!svn/vcc/default'
> svn: REPORT of '/svn/!svn/vcc/default': Could not read response body:
> SSL error: decryption failed or bad record mac (https://my.ip.goes.here)
>
> I'm seriously running into a lack of information on this error,
> despite people reporting it. Does anyone have any ideas? =( I'm
> gearing up for an all-nighter here because I have to have this
> working...
If I had to guess I'd say you should start looking for something
between the client and the server that's causing problems. Does this
happen if you run the command right on the server, not going over the
network at all?
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Help! REPORT fail & SSL error... UPDATE
Posted by Justin <ju...@hush.cc>.
Hey again everyone,
Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
server. So, updated the server to 1.4.0 and the clients expecting
things to work... while the error I'm getting is now smaller, this
part of the error still exists:
svn: REPORT request failed on '/svn/!svn/vcc/default'
svn: REPORT of '/svn/!svn/vcc/default': Could not read response body:
SSL error: decryption failed or bad record mac (https://my.ip.goes.here)
I'm seriously running into a lack of information on this error,
despite people reporting it. Does anyone have any ideas? =( I'm
gearing up for an all-nighter here because I have to have this
working...
Thanks again in advance,
*justin
On Sep 27, 2006, at 4:08 PM, Justin wrote:
> Hi everyone,
>
> Out of the blue, after over 150 revisions in our repository, we ran
> into this error trying to checkout a revision:
>
> subversion/libsvn_ra_dav/util.c:826: (apr_err=175002)
> svn: REPORT request failed on '/svn/!svn/vcc/default'
> subversion/libsvn_ra_dav/util.c:296: (apr_err=175002)
> svn: REPORT of '/svn/!svn/vcc/default': Could not read response
> body: SSL error: decryption failed or bad record mac (https://
> my.ip.goes.here)
>
> Checkout start grabbing a handful of parts of the revision, but
> then fails with this error. In the log itself, this error is FIRST
> before the list of "A /Path/to/the/bitsAndPieces", FWIW.
>
> Nothing changed on the server, other than one of our devs grabbing
> our whole repository folder for the purposes of an off-site backup,
> which they've done before. This is on OS X Server running Apache2
> and SSL, with a self-signed certificate. Googled the parts of the
> error but nothing seems too helpful.
>
> We're coming up on milestones, so I need to get this fixed ASAP.
> Any help would be so greatly appreciated, as I'm very new at
> SubVersion.
>
> Thanks so much!
>
> *justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org