You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org> on 2010/06/27 23:22:49 UTC

[jira] Commented: (INFRA-2532) receiving "svn: PROPFIND of '/repos/asf/...': SSL negotiation failed: SSL error: parse tlsext (https://svn.apache.org) "

    [ https://issues.apache.org/jira/browse/INFRA-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882990#action_12882990 ] 

#asfinfra IRC Bot commented on INFRA-2532:
------------------------------------------

<pgollucc1> probably suprious, also subversion has been upgraded since, please re-open if it persists


> receiving "svn: PROPFIND of '/repos/asf/...': SSL negotiation failed: SSL error: parse tlsext (https://svn.apache.org) "
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: INFRA-2532
>                 URL: https://issues.apache.org/jira/browse/INFRA-2532
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: HTTP Server, Subversion
>            Reporter: Brett Porter
>
> Just today, I've started receiving the above error while performing an svn merge -c $REV between a branch and trunk. It's done from the root of the tree (https://svn.apache.org/repos/asf/archiva/trunk/). I'm not sure the last time I did it successfully to correlate to any changes that might have happened on the server.
> It seems we are running a combo that is known to trigger it (httpd 2.2.14 and openssl 0.9.8k), as it's been reported on other installs:
> http://mail-archives.apache.org/mod_mbox/httpd-dev/200910.mbox/%3c4ADF0D8E.1000202@collab.net%3e
> http://serverfault.com/questions/44470/ssl-error-parse-tlsext-on-large-commit-to-svn-via-apache-gentoo
> The clients I tried are Subversion 1.6.5 (Mac) and Subversion 1.6.6 (Windows)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.