Issue 8439 - returned unspecified error while trying to start ldap server
Summary: returned unspecified error while trying to start ldap server
Status: VERIFIED INVALID
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-09 14:33 UTC by sudha243p@gmail.com
Modified: 2020-03-22 23:03 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description sudha243p@gmail.com 2016-06-09 14:33:31 UTC
Full_Name: Sudhakar Pittala
Version: openldap 2.8
OS: SUSE11.4
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (192.176.1.87)


Hi,

We are using a OPEN SUSE 11.4 LINUX OS machine. 

Initially ldap process was running fine. 
Recently we have restarted this machine and after restart we have found that
ldap service was not running.

So I have tried to start/restart ldap server using Yast and command line but
couldn't succeed.

Output from Yast:

/etc/init.d/ldap start returned 1 (unspecified error): 

Output from command line:

SLS001:/etc/init.d # ./ldap restart
redirecting to systemctl
redirecting to systemctl
Shutting down ldap-server                                                       
                                                                     done
redirecting to systemctl
Starting ldap-server                                                            
                                                                     failed

File /var/log/localmessages shows below entries.

Jun  9 15:24:28 SLS001 slapd[3502]:     1.2.36.79672281.1.13.3 (rdnMatch): 
Jun  9 15:24:28 SLS001 slapd[3502]:     2.5.13.1 (distinguishedNameMatch): 
Jun  9 15:24:28 SLS001 slapd[3502]: matchingRuleUse: ( 2.5.13.1 NAME
'distinguishedNameMatch' APPLIES ( creatorsName $ modifiersName $
subschemaSubentry $ entryDN $ namingContexts $ aliasedObjectName $
dynamicSubtrees $ distinguishedName $ seeAlso $ olcDefaultSearchBase $ olcRootDN
$ olcSchemaDN $ olcSuffix $ olcUpdateDN $ olcDbACLAuthcDn $ olcDbIDAssertAuthcDn
$ olcRelay $ pwdPolicySubentry $ olcPPolicyDefault $ member $ owner $
roleOccupant $ manager $ documentAuthor $ secretary $ associatedName $
dITRedirect $ suseDefaultBase $ suseDefaultTemplate $ suseSecondaryGroup ) )
Jun  9 15:24:28 SLS001 slapd[3502]:     2.5.13.0 (objectIdentifierMatch): 
Jun  9 15:24:28 SLS001 slapd[3502]: matchingRuleUse: ( 2.5.13.0 NAME
'objectIdentifierMatch' APPLIES ( supportedControl $ supportedExtension $
supportedFeatures $ supportedApplicationContext ) )
Jun  9 15:24:28 SLS001 slapd[3505]: slapd startup: initiated.
Jun  9 15:24:28 SLS001 slapd[3505]: backend_startup_one: starting "cn=config"
Jun  9 15:24:28 SLS001 slapd[3505]: config_back_db_open
Jun  9 15:24:28 SLS001 slapd[3505]: config_back_db_open: line 0: warning: cannot
assess the validity of the ACL scope within backend naming context
Jun  9 15:24:28 SLS001 slapd[3505]: config_build_entry: "cn=config"
Jun  9 15:24:28 SLS001 slapd[3505]: config_build_entry: "cn=schema"
Jun  9 15:24:28 SLS001 slapd[3505]: >>> dnNormalize: <cn={0}core>
Jun  9 15:24:28 SLS001 slapd[3505]: <<< dnNormalize: <cn={0}core>
Jun  9 15:24:28 SLS001 slapd[3505]: config_build_entry: "cn={0}core"
Jun  9 15:24:28 SLS001 slapd[3505]: >>> dnNormalize: <cn={1}cosine>
Jun  9 15:24:28 SLS001 slapd[3505]: <<< dnNormalize: <cn={1}cosine>
Jun  9 15:24:28 SLS001 slapd[3505]: config_build_entry: "cn={1}cosine"
Jun  9 15:24:28 SLS001 slapd[3505]: >>> dnNormalize: <cn={2}inetorgperson>
Jun  9 15:24:28 SLS001 slapd[3505]: <<< dnNormalize: <cn={2}inetorgperson>
Jun  9 15:24:28 SLS001 slapd[3505]: config_build_entry: "cn={2}inetorgperson"
Jun  9 15:24:28 SLS001 slapd[3505]: >>> dnNormalize: <cn={3}rfc2307bis>
Jun  9 15:24:28 SLS001 slapd[3505]: <<< dnNormalize: <cn={3}rfc2307bis>
Jun  9 15:24:28 SLS001 slapd[3505]: config_build_entry: "cn={3}rfc2307bis"
Jun  9 15:24:28 SLS001 slapd[3505]: >>> dnNormalize: <cn={4}yast>
Jun  9 15:24:28 SLS001 slapd[3505]: <<< dnNormalize: <cn={4}yast>
Jun  9 15:24:28 SLS001 slapd[3505]: config_build_entry: "cn={4}yast"
Jun  9 15:24:28 SLS001 slapd[3505]: config_build_entry:
"olcDatabase={-1}frontend"D%D
Jun  9 15:24:28 SLS001 slapd[3505]: config_build_entry: "olcDatabase={0}config"
Jun  9 15:24:28 SLS001 slapd[3505]: config_build_entry: "olcDatabase={1}bdb"
Jun  9 15:24:28 SLS001 slapd[3505]: backend_startup_one: starting
"ou=slsusers,o=ericssonOAM"D%D
Jun  9 15:24:28 SLS001 slapd[3505]: bdb_db_open: "ou=slsusers,o=ericssonOAM"
Jun  9 15:24:28 SLS001 slapd[3505]: bdb_db_open: database
"ou=slsusers,o=ericssonOAM": alock package is unstable.
Jun  9 15:24:28 SLS001 slapd[3505]: backend_startup_one (type=bdb,
suffix="ou=slsusers,o=ericssonOAM"): bi_db_open failed! (-1)
Jun  9 15:24:28 SLS001 slapd[3505]: slapd shutdown: initiated
Jun  9 15:24:28 SLS001 slapd[3505]: ====> bdb_cache_release_all
Jun  9 15:24:28 SLS001 slapd[3505]: bdb_db_close: database
"ou=slsusers,o=ericssonOAM": alock_close failed
Jun  9 15:24:28 SLS001 slapd[3505]: slapd destroy: freeing system resources.
Jun  9 15:24:28 SLS001 slapd[3505]: slapd stopped.
Jun  9 15:24:28 SLS001 slapd[3505]: daemon: SLPDereg(service:ldap://SLS001.site)
failed with -20, cookie = 0
Jun  9 15:24:28 SLS001 slapd[3505]: daemon:
SLPDereg(service:ldaps://SLS001.site) failed with -20, cookie = 0

Could you please let us know what went wrong in this scenario ?

BR,
Sudhakar
Comment 1 Quanah Gibson-Mount 2016-06-09 14:54:14 UTC
--On Thursday, June 09, 2016 3:33 PM +0000 sudha243p@gmail.com wrote:

> Could you please let us know what went wrong in this scenario ?

The ITS system is for filing bug reports, not usage questions.  Your logs 
clearly show your database is corrupt:

Jun  9 15:24:28 SLS001 slapd[3505]: bdb_db_open: "ou=slsusers,o=ericssonOAM"
Jun  9 15:24:28 SLS001 slapd[3505]: bdb_db_open: database
"ou=slsusers,o=ericssonOAM": alock package is unstable.
Jun  9 15:24:28 SLS001 slapd[3505]: backend_startup_one (type=bdb,
suffix="ou=slsusers,o=ericssonOAM"): bi_db_open failed! (-1)
Jun  9 15:24:28 SLS001 slapd[3505]: slapd shutdown: initiated

This ITS will be closed.

--Quanah



--

Quanah Gibson-Mount
Platform Architect
Manager, Systems Team
Zimbra, Inc.
--------------------
Zimbra ::  the leader in open source messaging and collaboration
A division of Synacor, Inc