View Single Post
  #4 (permalink)  
Old 09-29-2005, 02:18 PM
largenumber largenumber is offline
Starter Member
 
Posts: 2
Default

Looks like the bad config line was caused by a blank line in the file... removed it.

The second error appears to be from an improper config value somewhere. I set the value in conf/slapd.conf to the right directory.

After finding the command that is actually being sent to start slapd (A pity that their initialization script doesn't produce a log file like the last one):

/opt/zimbra/openldap/libexec/slapd -4 -u`whoami` -h "ldap://:389" -f /opt/zimbra/conf/slapd.conf

I changed it to (so I could get some error messages):

sudo /opt/zimbra/openldap/libexec/slapd -4 -h "ldap://:389" -f /opt/zimbra/conf/slapd.conf -d 5001

Which gets me the output:

@(#) $OpenLDAP: slapd 2.2.26 (Aug 17 2005 00:15:16) $
marcmac@depot.liquidsys.com:/space/home/marcmac/p4/main/ThirdParty/openldap/openldap-2.2.26/servers/slapd
daemon_init: listen on ldap://:389
daemon_init: 1 listeners to open...
ldap_url_parse_ext(ldap://:389)
daemon: initialized ldap://:389
daemon_init: 1 listeners opened
slapd init: initiated server.
slap_sasl_init: initialized!
bdb_back_initialize: initialize BDB backend
bdb_back_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003)
>>> dnNormalize:
=> ldap_bv2dn(cn=Subschema,0)
ldap_err2string
<= ldap_bv2dn(cn=Subschema)=0 Success
=> ldap_dn2bv(272)
ldap_err2string

....

slapd startup: initiated.
backend_startup: starting ""
bdb_db_open: dbenv_open(/opt/zimbra/openldap/var/openldap-data)
bdb(): unable to initialize mutex: Function not implemented
bdb(): /opt/zimbra/openldap/var/openldap-data/__db.001: unable to initialize environment lock: Function not implemented
bdb_db_open: dbenv_open failed: Function not implemented (38)
backend_startup: bi_db_open failed! (38)
slapd shutdown: initiated
====> bdb_cache_release_all
bdb(): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem
slapd shutdown: freeing system resources.
bdb(): txn_checkpoint interface requires an environment configured for the transaction subsystem
bdb_db_destroy: txn_checkpoint failed: Invalid argument (22)
slapd stopped.
connections_destroy: nothing to destroy.

At which point I notice I'm getting this statement "ldap_err2string" and I suspect an error, but it doesn't really say more than that. Also more at the end of the output there are clearly some functions missing "bdb(): unable to initialize mutex: Function not implemented"...

Unfortunately that is all I know for now
Reply With Quote