openldap启动报错，麻烦请看看什么原因

zhaohao19853 2013-04-02 10:48:59



D:\OpenLDAP>slapd -d 1

ldap_url_parse_ext(ldap://localhost/)

ldap_init: trying %SYSCONFDIR%\ldap.conf

ldap_init: HOME env is NULL

ldap_init: trying ldaprc

ldap_init: LDAPCONF env is NULL

ldap_init: LDAPRC env is NULL

515a46fe OpenLDAP 2.4.34 Standalone LDAP Server (slapd)515a46fe daemon_init: listen on ldap:///

515a46fe daemon_init: 1 listeners to open...

ldap_url_parse_ext(ldap:///)

515a46fe daemon: listener initialized ldap:///

515a46fe daemon_init: 1 listeners opened

ldap_create

515a46fe slapd init: initiated server.

515a46fe slap_sasl_init: initialized!

515a46fe bdb_back_initialize: initialize BDB backend

515a46fe bdb_back_initialize: Berkeley DB 5.3.21: (May 11, 2012)

515a46fe ==>sql_back_initialize()

515a46fe <==sql_back_initialize()

515a46fe mdb_back_initialize: initialize MDB backend

515a46fe mdb_back_initialize: MDB 0.9.6: (January 10, 2013)

515a46fe ==> translucent_initialize

515a46fe bdb_db_init: Initializing BDB database

515a46fe >>> dnPrettyNormal: <o=broadengate,dc=com>

515a46fe <<< dnPrettyNormal: <o=broadengate,dc=com>, <o=broadengate,dc=com>

515a46fe >>> dnPrettyNormal: <cn=Manager,o=broadengate,dc=com>

515a46fe <<< dnPrettyNormal: <cn=Manager,o=broadengate,dc=com>, <cn=manager,o=broadengate,dc=com>

515a46fe >>> dnNormalize: <cn=Subschema>

515a46fe <<< dnNormalize: <cn=subschema>

515a46fe matching_rule_use_init

515a46fe     1.2.840.113556.1.4.804 (integerBitOrMatch): 515a46fe matchingRuleUse: ( 1.2.840.113556.1.4.804 NAME 'integerBitOrMatch' APPLIES ( supportedLDAPVersion $ entryTtl $ uidN

515a46fe     1.2.840.113556.1.4.803 (integerBitAndMatch): 515a46fe matchingRuleUse: ( 1.2.840.113556.1.4.803 NAME 'integerBitAndMatch' APPLIES ( supportedLDAPVersion $ entryTtl $ ui

515a46fe     1.3.6.1.4.1.1466.109.114.2 (caseIgnoreIA5Match): 515a46fe matchingRuleUse: ( 1.3.6.1.4.1.1466.109.114.2 NAME 'caseIgnoreIA5Match' APPLIES ( altServer $ olcDbConfig $ c

515a46fe     1.3.6.1.4.1.1466.109.114.1 (caseExactIA5Match): 515a46fe matchingRuleUse: ( 1.3.6.1.4.1.1466.109.114.1 NAME 'caseExactIA5Match' APPLIES ( altServer $ olcDbConfig $ c $

515a46fe     2.5.13.39 (certificateListMatch): 515a46fe     2.5.13.38 (certificateListExactMatch): 515a46fe matchingRuleUse: ( 2.5.13.38 NAME 'certificateListExactMatch' APPLIES ( a

515a46fe     2.5.13.35 (certificateMatch): 515a46fe     2.5.13.34 (certificateExactMatch): 515a46fe matchingRuleUse: ( 2.5.13.34 NAME 'certificateExactMatch' APPLIES ( userCertifica

515a46fe     2.5.13.30 (objectIdentifierFirstComponentMatch): 515a46fe matchingRuleUse: ( 2.5.13.30 NAME 'objectIdentifierFirstComponentMatch' APPLIES ( supportedControl $ supported

515a46fe     2.5.13.29 (integerFirstComponentMatch): 515a46fe matchingRuleUse: ( 2.5.13.29 NAME 'integerFirstComponentMatch' APPLIES ( supportedLDAPVersion $ entryTtl $ uidNumber $

515a46fe     2.5.13.28 (generalizedTimeOrderingMatch): 515a46fe matchingRuleUse: ( 2.5.13.28 NAME 'generalizedTimeOrderingMatch' APPLIES ( createTimestamp $ modifyTimestamp $ pwdCha

515a46fe     2.5.13.27 (generalizedTimeMatch): 515a46fe matchingRuleUse: ( 2.5.13.27 NAME 'generalizedTimeMatch' APPLIES ( createTimestamp $ modifyTimestamp $ pwdChangedTime $ pwdAc

515a46fe     2.5.13.24 (protocolInformationMatch): 515a46fe matchingRuleUse: ( 2.5.13.24 NAME 'protocolInformationMatch' APPLIES protocolInformation )

515a46fe     2.5.13.23 (uniqueMemberMatch): 515a46fe matchingRuleUse: ( 2.5.13.23 NAME 'uniqueMemberMatch' APPLIES uniqueMember )

515a46fe     2.5.13.22 (presentationAddressMatch): 515a46fe matchingRuleUse: ( 2.5.13.22 NAME 'presentationAddressMatch' APPLIES presentationAddress )

515a46fe     2.5.13.20 (telephoneNumberMatch): 515a46fe matchingRuleUse: ( 2.5.13.20 NAME 'telephoneNumberMatch' APPLIES ( telephoneNumber $ homePhone $ mobile $ pager ) )

515a46fe     2.5.13.18 (octetStringOrderingMatch): 515a46fe matchingRuleUse: ( 2.5.13.18 NAME 'octetStringOrderingMatch' APPLIES ( userPassword $ olcDbCryptKey $ pwdHistory $ javaSe

515a46fe     2.5.13.17 (octetStringMatch): 515a46fe matchingRuleUse: ( 2.5.13.17 NAME 'octetStringMatch' APPLIES ( userPassword $ olcDbCryptKey $ pwdHistory $ javaSerializedData ) )

515a46fe     2.5.13.16 (bitStringMatch): 515a46fe matchingRuleUse: ( 2.5.13.16 NAME 'bitStringMatch' APPLIES x500UniqueIdentifier )

515a46fe     2.5.13.15 (integerOrderingMatch): 515a46fe matchingRuleUse: ( 2.5.13.15 NAME 'integerOrderingMatch' APPLIES ( supportedLDAPVersion $ entryTtl $ uidNumber $ gidNumber $

515a46fe     2.5.13.14 (integerMatch): 515a46fe matchingRuleUse: ( 2.5.13.14 NAME 'integerMatch' APPLIES ( supportedLDAPVersion $ entryTtl $ uidNumber $ gidNumber $ olcConcurrency $

515a46fe     2.5.13.13 (booleanMatch): 515a46fe matchingRuleUse: ( 2.5.13.13 NAME 'booleanMatch' APPLIES ( hasSubordinates $ olcAddContentAcl $ olcGentleHUP $ olcHidden $ olcLastMod

515a46fe     2.5.13.11 (caseIgnoreListMatch): 515a46fe matchingRuleUse: ( 2.5.13.11 NAME 'caseIgnoreListMatch' APPLIES ( postalAddress $ registeredAddress $ homePostalAddress ) )

515a46fe     2.5.13.9 (numericStringOrderingMatch): 515a46fe matchingRuleUse: ( 2.5.13.9 NAME 'numericStringOrderingMatch' APPLIES ( x121Address $ internationaliSDNNumber ) )

515a46fe     2.5.13.8 (numericStringMatch): 515a46fe matchingRuleUse: ( 2.5.13.8 NAME 'numericStringMatch' APPLIES ( x121Address $ internationaliSDNNumber ) )

515a46fe     2.5.13.7 (caseExactSubstringsMatch): 515a46fe matchingRuleUse: ( 2.5.13.7 NAME 'caseExactSubstringsMatch' APPLIES ( serialNumber $ destinationIndicator $ dnQualifier )

515a46fe     2.5.13.6 (caseExactOrderingMatch): 515a46fe matchingRuleUse: ( 2.5.13.6 NAME 'caseExactOrderingMatch' APPLIES ( supportedSASLMechanisms $ vendorName $ vendorVersion $ r

515a46fe     2.5.13.5 (caseExactMatch): 515a46fe matchingRuleUse: ( 2.5.13.5 NAME 'caseExactMatch' APPLIES ( supportedSASLMechanisms $ vendorName $ vendorVersion $ ref $ name $ cn $

515a46fe     2.5.13.4 (caseIgnoreSubstringsMatch): 515a46fe matchingRuleUse: ( 2.5.13.4 NAME 'caseIgnoreSubstringsMatch' APPLIES ( serialNumber $ destinationIndicator $ dnQualifier

515a46fe     2.5.13.3 (caseIgnoreOrderingMatch): 515a46fe matchingRuleUse: ( 2.5.13.3 NAME 'caseIgnoreOrderingMatch' APPLIES ( supportedSASLMechanisms $ vendorName $ vendorVersion $

515a46fe     2.5.13.2 (caseIgnoreMatch): 515a46fe matchingRuleUse: ( 2.5.13.2 NAME 'caseIgnoreMatch' APPLIES ( supportedSASLMechanisms $ vendorName $ vendorVersion $ ref $ name $ cn

515a46fe     1.2.36.79672281.1.13.3 (rdnMatch): 515a46fe     2.5.13.1 (distinguishedNameMatch): 515a46fe matchingRuleUse: ( 2.5.13.1 NAME 'distinguishedNameMatch' APPLIES ( creators

515a46fe     2.5.13.0 (objectIdentifierMatch): 515a46fe matchingRuleUse: ( 2.5.13.0 NAME 'objectIdentifierMatch' APPLIES ( supportedControl $ supportedExtension $ supportedFeatures

515a46fe slapd startup: initiated.

515a46fe backend_startup_one: starting "cn=config"

515a46fe config_back_db_open

515a46fe config_build_entry: "cn=config"

515a46fe config_build_attrs: error 21 on olcConfigFile value #0

515a46fe config_build_entry: build "cn=config" failed: ""

515a46fe backend_startup_one (type=config, suffix="cn=config"): bi_db_open failed! (-1)

515a46fe slapd shutdown: initiated

515a46fe ====> bdb_cache_release_all

515a46fe slapd destroy: freeing system resources.

515a46fe slapd stopped.

slapd.conf 配置文件如下



# BDB Backend configuration file

# See slapd.conf(5) for details on configuration options.

# This file should NOT be world readable.

ucdata-path	./ucdata

include		./schema/core.schema

include		./schema/cosine.schema

include		./schema/nis.schema

include		./schema/inetorgperson.schema

include		./schema/openldap.schema

include		./schema/dyngroup.schema

include		./schema/java.schema

include		./schema/misc.schema





pidfile		./run/slapd.pid

argsfile	./run/slapd.args





# Enable TLS if port is defined for ldaps





TLSVerifyClient never

TLSCipherSuite HIGH:MEDIUM:-SSLv2

TLSCertificateFile ./secure/certs/server.pem

TLSCertificateKeyFile ./secure/certs/server.pem

TLSCACertificateFile ./secure/certs/server.pem









#######################################################################

# bdb database definitions

#######################################################################





database	bdb

suffix		"o=broadengate,dc=com"

rootdn		"cn=Manager,o=broadengate,dc=com"

# Cleartext passwords, especially for the rootdn, should

# be avoid.  See slappasswd(8) and slapd.conf(5) for details.

# Use of strong authentication encouraged.

rootpw		{MD5}Wxtoqav00s0VXIGpIl/RWA==



# The database directory MUST exist prior to running slapd AND

# should only be accessible by the slapd and slap tools.

# Mode 700 recommended.

directory ./data

dirtyread

searchstack 20

# Indices to maintain

index mail pres,eq

index objectclass pres

index default eq,sub

index sn eq,sub,subinitial

index telephonenumber

index cn

...全文

3784 21 打赏收藏举报

写回复

21 条回复

切换为时间正序

当前发帖距今超过3年，不再开放新的回复

发表回复

ccnaguren 2015-08-12

我也碰到这个问题了，不过我解决了，一个个问题排除的。将自定义schema去掉，先用slapd -d 1 -f ./slapd.conf检查是否正常加载配置文件，正常则系统是没问题的。注释掉schema中字段，拷贝系统的字段加入，另存为utf-8编码文件，上述命令正常启动，说明可能出在schema中的字段或者编码。逐个检查shema字段，修改正常加入就没问题了。

打赏
举报

回复赞

redlz2500 2015-03-02

求问，win2003 才下载了4.0.1版本，使用bdb，未修改配置文件，按照-d 1 -f的方式启动，但是一直是 bdb_db_open:database "dc=maxcrc,dc=com": database already in use. backend_startup_one (type=bdb, suffix="dc=maxcrc,dc=com"): bi_db_open failed! (-1) 修改配置文件 suffix "o=test,c=cn" rootdn "cn=config,o=test,c=cn" 也一样的情况，只是括号内的东西变了，这个怎么搞啊？

打赏
举报

回复赞

redlz2500 2015-03-02

好嘛，原来我这个直接就已经作为服务启动起来了……所以一直in use……

打赏
举报

回复赞

jiaxiaodong999 2014-09-18

引用 10 楼 treeonhill 的回复:

从别的网上看到的方法：解决方法(一): slapd.exe -d 1 -f ./slapd.conf 加上 -f 和你的配置文件路径解决方法(二): 安装目录下面有个 run 目录, run 目录下面有个 run.cmd 直接双击运行; 这个版本的启动方式有些变动

正解问题得到解决

打赏
举报

回复赞

csnd_one 2014-06-26

大家谁解决这个问题了吗

打赏
举报

回复赞

lxfnog 2014-06-10

请问大家都解决了吗？我也遇到了这个问题

打赏
举报

回复赞

hjt_1986 2014-03-05

刚也用到LDAP这个服务器，也出了这个问题，请问楼主问题怎么解决的？能指点下么，看回贴里的方法都试过了还是不行，我是window 7的操作系统

打赏
举报

回复赞

一无所知163 2014-02-14

学习了,刚好遇到这个问题

打赏
举报

回复赞

知行合一陈 2014-01-07

大家好！ openldap现在还有谁在开发吗？

打赏
举报

回复赞

xiaoxue53shiluo 2013-10-31

引用 10 楼 treeonhill 的回复:

从别的网上看到的方法：解决方法(一): slapd.exe -d 1 -f ./slapd.conf 加上 -f 和你的配置文件路径解决方法(二): 安装目录下面有个 run 目录, run 目录下面有个 run.cmd 直接双击运行; 这个版本的启动方式有些变动

正解！！！！！！！！！！！！！！感谢！

打赏
举报

回复赞

junpengliang 2013-10-16

引用 7 楼 lixin032190 的回复:

该问题已经解决了，是文件编码问题，在含有中文时，自定义schema文件必须是UTF-8编码，把文件改为UTF-8编码即可，openldap服务只识别UTF-8编码的中文

这个文件怎么改的

打赏
举报

回复赞

treeonhill 2013-07-20

从别的网上看到的方法：解决方法(一): slapd.exe -d 1 -f ./slapd.conf 加上 -f 和你的配置文件路径解决方法(二): 安装目录下面有个 run 目录, run 目录下面有个 run.cmd 直接双击运行; 这个版本的启动方式有些变动

打赏
举报

回复赞

wintersum 2013-07-05

和LZ一样的问题，纠结中。。。

打赏
举报

回复赞

EllieJFJ 2013-07-01

C:\OpenLDAP>slapd -d 256 51d11bb1 OpenLDAP 2.4.34 Standalone LDAP Server (slapd)51d11bb1 daemon: bind(2) failed errno=10013 (WSAEACCES) 51d11bb1 slapd stopped. 51d11bb1 connections_destroy: nothing to destroy. 在windows下启动的.这个错误..求解