RE: Invalid rootDN on OpenLDAP for z/OS

["Thomas Broeker" <BROEKER@de.ibm.com>]

The schema file is included because i can see the entries in the debug
trace (not listed in the sniped). But anyhow I changed nothing and now it
works. I even replaced the configs with the backup from yesterday and it
works too. I have no idea why it works now, but it does.

Mit freundlichen Grüßen / best regards

               Thomas Bröker

-------------------------------------------------------------
IBM Deutschland Entwicklung GmbH
Phone: +49-(0)7031-16-2401
eMail: broeker@de.ibm.com


It sounds like the schema files are not being included so the dc and cn
attrs are not defined.  Check to see that the relative path is correct.

Mitch


-----Original Message-----
From: Thomas Broeker [mailto:BROEKER@de.ibm.com]
Sent: Friday, August 01, 2003 4:21 AM
To: Greg Matthews
Cc: openldap-software@OpenLDAP.org
Subject: Re: Invalid rootDN on OpenLDAP for z/OS


I don't think an empty suffix causes a problem, because with the OpenLDAP
we build for windows it works without problems.
Anyway when we set a suffix like "dc=msys, dc=com" , we get a similar
problem:

>slapd -f slapd.conf -t -d -1
 init: initiated .
reading config file
line 0 (pidfile      /u/star/tools/openldap/bin/slapd.pid)
line 0 (argsfile     /u/star/tools/openldap/bin/slapd.args)
line 0 (database    ldbm)
line 0 (suffix      "dc=msys, dc=com")
>>> dnPrettyNormal: <>
=> ldap_bv2dn(Î4&Î5¬,84)
<= ldap_bv2dn(,0)=2
: line 477790252: suffix DN is invalid
config check failed
 shutdown: freeing system resources.
slapd stopped.
connections_destroy: nothing to destroy.

The directory db exists and has rwx for anyone, so that should be no
problem. We also tried using absolute paths in the config file without an
effect.
We think this problem occures because of the EBCDIC encoding on the host,
but without a suffix and a root dn the config check succeeded and slapd can
be started.