svn: E215004: Authentication failed
Linux環(huán)境配置安裝好SVN服務(wù)器后,輸入命令:
svn co svn:// IP : PORT
結(jié)果返回Authentication failed
[root]@iZ23whn33Z conf]#svn co svn://115.29.250.111:3690
svn:E215004:Unable to connect to a repository at URL 'svn://115.29.250.111'
svn:E215004:Authentication failed
可能出現(xiàn)這種問題的原因:
(1)配置文件中出現(xiàn)前綴空格符
(2)配置文件中配置參數(shù)異常
(3)后續(xù)再補充
針對第一種問題,解決辦法如下:把需要配置的參數(shù)前綴空格都去除
[root@iZ23whn33jnZ ~]# cd /usr/local/svn/mbk/conf/
[root@iZ23whn33jnZ conf]# ll
total 16
-rw-r--r-- 1 root root 1114 Jan 26 11:27 authz
-rw-r--r-- 1 root root ?331 Jan 26 11:27 passwd
-rw-r--r-- 1 root root 3058 Jan 26 11:32 svnserve.conf
[root@iZ23whn33jnZ conf]# vi svnserve.conf
### This file controls the configuration of the svnserve daemon, if you
### use it to allow access to this repository. ?(If you only allow
### access through http: and/or file: URLs, then this file is
### irrelevant.)
### Visit http://subversion.apache.org/ for more information.
[general]
### The anon-access and auth-access options control access to the
### repository for unauthenticated (a.k.a. anonymous) users and
### authenticated users, respectively.
### Valid values are "write", "read", and "none".
### Setting the value to "none" prohibits both reading and writing;
### "read" allows read-only access, and "write" allows complete
### read/write access to the repository.
### The sample settings below are the defaults and specify that anonymous
### users have read-only access to the repository, while authenticated
### users have read and write access to the repository.
anon-access = none
auth-access = write
### The password-db option controls the location of the password
### database file. ?Unless you specify a path starting with a /,
### the file's location is relative to the directory containing
### this configuration file.
### If SASL is enabled (see below), this file will NOT be used.
### Uncomment the line below to use the default password file.
password-db = passwd
### The authz-db option controls the location of the authorization
### rules for path-based access control. ?Unless you specify a path
### starting with a /, the file's location is relative to the the
### directory containing this file. ?If you don't specify an
### authz-db, no path-based access control is done.
### Uncomment the line below to use the default authorization file.
authz-db=authz
### This option specifies the authentication realm of the repository.
### If two repositories have the same authentication realm, they should
### have the same password database, and vice versa. ?The default realm
### is repository's uuid.
realm=mbk
### The force-username-case option causes svnserve to case-normalize
### usernames before comparing them against the authorization rules in the
### authz-db file configured above. ?Valid values are "upper" (to upper-
### case the usernames), "lower" (to lowercase the usernames), and
### "none" (to compare usernames as-is without case conversion, which
### is the default behavior).
force-username-case = none
[sasl]
### This option specifies whether you want to use the Cyrus SASL
### library for authentication. Default is false.
### This section will be ignored if svnserve is not built with Cyrus
### SASL support; to check, run 'svnserve --version' and look for a line
### reading 'Cyrus SASL authentication is available.'
# use-sasl = true
### These options specify the desired strength of the security layer
### that you want SASL to provide. 0 means no encryption, 1 means
### integrity-checking only, values larger than 1 are correlated
### to the effective key length for encryption (e.g. 128 means 128-bit
### encryption). The values below are the defaults.
# min-encryption = 0
# max-encryption = 256
PS : conf下面的幾個配置文件都要去除前綴空格。
針對第二種問題,解決辦法如下:檢查配置的參數(shù)是否正確
1.這個參數(shù)值表示認證的配置文件名稱,如conf下的 authz 文件。 authz-db=authz
2.這個參數(shù)值表示密碼數(shù)據(jù)庫的文件名稱,如conf下的 passwd 文件。
password-db = passwd
使用conf下的配置文件時,這些參數(shù)值要和conf下的配置文件名稱相同。
總結(jié)
以上是生活随笔為你收集整理的svn: E215004: Authentication failed的全部內(nèi)容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: ------ 比较二位数组大小----
- 下一篇: SQLServer数据库如何收缩日志空间