Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 881E6105EA for ; Thu, 5 Dec 2013 06:14:35 +0000 (UTC) Received: (qmail 25156 invoked by uid 500); 5 Dec 2013 06:11:43 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 25047 invoked by uid 500); 5 Dec 2013 06:11:35 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Delivered-To: moderator for users@subversion.apache.org Received: (qmail 39766 invoked by uid 99); 4 Dec 2013 23:02:43 -0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of john@etailz.com designates 207.46.163.154 as permitted sender) Message-ID: <529FB472.5000700@etailz.com> Date: Wed, 4 Dec 2013 15:02:10 -0800 From: John User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Subject: Issue - SVN cannot create SASL context Content-Type: multipart/alternative; boundary="------------050601000006080200070604" X-Originating-IP: [173.160.206.241] X-ClientProxiedBy: BY2PR03CA030.namprd03.prod.outlook.com (10.242.234.151) To BLUPR04MB323.namprd04.prod.outlook.com (10.141.24.23) X-Forefront-PRVS: 0050CEFE70 X-Forefront-Antispam-Report: SFV:NSPM;SFS:(189002)(199002)(76482001)(79102001)(36756003)(59896001)(81542001)(76176001)(81342001)(47736001)(47976001)(50986001)(71186001)(83506001)(80022001)(65806001)(65956001)(69226001)(15202345003)(63696002)(74876001)(46102001)(74366001)(19580395003)(80976001)(51856001)(66066001)(4396001)(53806001)(42186004)(15975445006)(49866001)(54356001)(80316001)(83322001)(81686001)(81816001)(74706001)(90146001)(54316002)(47446002)(56776001)(74502001)(56816005)(74662001)(83072001)(85306002)(85852002)(31966008)(33656001)(87976001)(512934002)(77982001)(64126003)(84326002)(76786001)(76796001)(16236675002)(59766001)(77096001);DIR:OUT;SFP:;SCL:1;SRVR:BLUPR04MB323;H:[172.16.144.28];CLIP:173.160.206.241;FPR:;RD:InfoNoRecords;MX:1;A:1;LANG:en; X-OriginatorOrg: etailz.com X-Virus-Checked: Checked by ClamAV on apache.org --------------050601000006080200070604 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit After many hours of apparently pointless googling, I hope to get an answer here. I asked a question on unix.stackexchange.com which essentially outlines my problem: http://unix.stackexchange.com/questions/103714/svn-failing-to-create-sasl-context Here is the text of that question: -------------- Trying to execute the command |svn log svn://[my server address]/path/to/repository | nets me the following: |svn: E170001: Unable to connect to a repository at URL 'svn://[my server address]/path/to/repository' svn: E170001: Could not create SASL context: generic failure | Some quick googling reveals a possiblesolution : |sudo port activate cyrus-sasl2 @2.1.23_3+kerberos | However, before I attempt this, I would like to know a couple things. 1. What exactly is going on? 2. What does this command do? How does it fix the problem? ------------------------ As some additional info, I am not using SASL on my server- as far as I am aware, anyway. The output of "svnserve --version" on the server shows this: _________________ svnserve, version 1.6.17 (r1128011) compiled Jun 26 2013, 20:44:36 Copyright (C) 2000-2009 CollabNet. Subversion is open source software, see http://subversion.apache.org/ This product includes software developed by CollabNet (http://www.Collab.Net/). The following repository back-end (FS) modules are available: * fs_base : Module for working with a Berkeley DB repository. * fs_fs : Module for working with a plain file (FSFS) repository. Cyrus SASL authentication is available. ____________________ The output of running "svn --version" on my client gets this: ____________________ svn, version 1.7.9 (r1462340) compiled Apr 6 2013, 21:23:46 Copyright (C) 2013 The Apache Software Foundation. This software consists of contributions made by many people; see the NOTICE file for more information. Subversion is open source software, see http://subversion.apache.org/ The following repository access (RA) modules are available: * ra_neon : Module for accessing a repository via WebDAV protocol using Neon. - handles 'http' scheme - handles 'https' scheme * ra_svn : Module for accessing a repository using the svn network protocol. - with Cyrus SASL authentication - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk. - handles 'file' scheme * ra_serf : Module for accessing a repository via WebDAV protocol using serf. - handles 'http' scheme - handles 'https' scheme __________________________ Oddly, I can successfully use that command ("svn log svn://[my server address]/path/to/repository") on another client computer without any trouble. I have no idea where exactly to look to find the source of this problem, or what precisely is causing it. Help is greatly appreciated. -Cheers, John --------------050601000006080200070604 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable After many hours of apparently pointless googling, I hope to get an answer here.

I asked a question on unix.stackexchange.com which essentially outlines my problem: http://unix.stackexchange.com/questions/103714/svn-failing-= to-create-sasl-context

Here is the text of that question:

--------------

Trying to execute the command

svn log svn://[my =
server address]/path/to/repo
sitory

nets me the following:

svn: E170001: Unab=
le to connect to a repositor
y at URL 'svn://[my server address]/path/to/repository'
svn: E170001: Could not create SASL context: generic failure

Some quick googling reveals a possible solution:

sudo port activate=
 cyrus-sasl2 @2.1.23_3+kerbe
ros

However, before I attempt this, I would like to know a couple things.

  1. What exactly is going on?
  2. What does this command do? How does it fix the problem?

------------------------

As some additional info, I am not using SASL on my server- as far as I am aware, anyway. The output of "svnserve --version" on the server shows this:
_________________

svnserve, version 1.6.17 (r1128011)
   compiled Jun 26 2013, 20:44:36

Copyright (C) 2000-2009 CollabNet.
Subversion is open source software, see http://subversion.apache.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).

The following repository back-end (FS) modules are available:

* fs_base : Module for working with a Berkeley DB repository.
* fs_fs : Module for working with a plain file (FSFS) repository.

Cyrus SASL authentication is available.
____________________

The output of running "svn --version" on my client gets this:

____________________

svn, version 1.7.9 (r1462340)
   compiled Apr  6 2013, 21:23:46

Copyright (C) 2013 The Apache Software Foundation.
This software consists of contributions made by many people; see the NOTICE
file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
  - handles 'http' scheme
  - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - handles 'http' scheme
  - handles 'https' scheme
__________________________

Oddly, I can successfully use that command ("svn log svn://[my server address]/path/to/repository") on another client computer without any trouble.

I have no idea where exactly to look to find the source of this problem, or what precisely is causing it. Help is greatly appreciated.

-Cheers,
John
--------------050601000006080200070604--