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

Re: Is SVN-1.6.12 compatible with Rhel6u2?

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Tue, 26 Feb 2013 17:23:58 -0500

On Tue, Feb 26, 2013 at 11:35 AM, Kriparam Faraday <kriparam_at_gmail.com> wrote:
> Hi,
> I just stood up an exact replica of a collabnet subversion
> server(version=1.6.12 and configured to run as apache subversion). I have
> enabled ssl(using an existing ssl cert from the production box).
>
> I am able to access the server using my browsers or svn clients like
> smartSVN or TortoiseSVN. But, when I hit refresh(F5) on the repo-browser of
> TortoiseSVN client, I see an error like this:
> "Server sent unexpected return value (400 Bad Request) in response to
> OPTIONS request for https://xx.xx.xx.xx/xx/ad/test-repo1/branches/newname"
>
> I am not able to reproduce this error on the production server. The only
> difference between the production and this backup is:
> (1) Production is on a Rhel5u6 and the backup is on Rhel6u2. I was not able
> to find any OS compatibility document for svn-1.6.12

RedHat's copy of subversion is out of date on RHEL. You're quite
welcome to my updated versions published at repoforge in the "extras"
repositories, or my tools for building Subversoin 1.6.20 and 1.7.8
RPM's available at:

            https://github.com/nkadel/subversion-1.6.20-srpm/
            https://github.com/nkadel/subversion-1.7.8-srpm/

> (2) Production has a valid ssl certificate. Backup is using the ssl
> certificate from production.
>
> These are the logs I see:
> ssl_request_log
> [25/Feb/2013:07:53:42 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "OPTIONS
> /xx/ad/test-repo1/branches/newname HTTP/1.1" 300
>
> ssl_access_log
> xx.xx.xx.xx - - [25/Feb/2013:07:53:42 -0500] "OPTIONS
> /xx/ad/test-repo1/branches/newname HTTP/1.1" 400 300
>
> ssl_error_log
> [Mon Feb 25 07:53:42 2013] [error] [client xx.xx.xx.xx] request failed:
> error reading the headers
>
> after this failure, I get subsequent failure log like the following until I
> restart the client:
>
> ssl_request_log
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "OPTIONS
> /xx/ad/test-repo1/trunk HTTP/1.1" 401
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "OPTIONS
> /xx/ad/test-repo1/trunk HTTP/1.1" 196
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/trunk HTTP/1.1" 702
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/!svn/vcc/default HTTP/1.1" 414
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/!svn/bln/4 HTTP/1.1" 465
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/trunk HTTP/1.1" 702
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/!svn/vcc/default HTTP/1.1" 414
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/!svn/bln/4 HTTP/1.1" 465
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/trunk HTTP/1.1" 702
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/!svn/vcc/default HTTP/1.1" 465
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/!svn/bc/4/trunk HTTP/1.1" 1329
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "REPORT
> /xx/ad/test-repo1/trunk HTTP/1.1" 112
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/trunk HTTP/1.1" 702
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/!svn/vcc/default HTTP/1.1" 465
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/!svn/bc/4/trunk HTTP/1.1" 430
> [25/Feb/2013:09:21:46 -0500] xx.xx.xx.xx TLSv1 DHE-RSA-AES256-SHA "PROPFIND
> /xx/ad/test-repo1/!svn/bc/4/trunk HTTP/1.1" 1298
>
> ssl_access_log
> xx.xx.xx.xx - - [25/Feb/2013:09:21:46 -0500] "OPTIONS
> /xx/ad/test-repo1/trunk HTTP/1.1" 401 401
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "OPTIONS
> /xx/ad/test-repo1/trunk HTTP/1.1" 200 196
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/trunk HTTP/1.1" 207 702
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/!svn/vcc/default HTTP/1.1" 207 414
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/!svn/bln/4 HTTP/1.1" 207 465
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/trunk HTTP/1.1" 207 702
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/!svn/vcc/default HTTP/1.1" 207 414
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/!svn/bln/4 HTTP/1.1" 207 465
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/trunk HTTP/1.1" 207 702
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/!svn/vcc/default HTTP/1.1" 207 465
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/!svn/bc/4/trunk HTTP/1.1" 207 1329
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "REPORT
> /xx/ad/test-repo1/trunk HTTP/1.1" 200 112
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/trunk HTTP/1.1" 207 702
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/!svn/vcc/default HTTP/1.1" 207 465
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/!svn/bc/4/trunk HTTP/1.1" 207 430
> xx.xx.xx.xx - username1 [25/Feb/2013:09:21:46 -0500] "PROPFIND
> /xx/ad/test-repo1/!svn/bc/4/trunk HTTP/1.1" 207 1298
>
> Any idea why this could be happening?

RHEL 5.6 is out of date, and the upstream certificate authorities
probably need updating. Update to RHEL 5.9 if at all feasible, just to
avoid confusion. Is your TortoiseSVN up-to-date? And what does the
command line say from the same client host as you're running
TortoiseSVN on.

>
> Thanks,
> Kripa
Received on 2013-02-26 23:24:32 CET

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.