Dear friends,

I am struggling to figure out what is wrong with my openldap implementation.

On a server RHEL4
openldap-clients-2.2.13-2
openldap-servers-2.2.13-2
openldap-2.2.13-2

WITH slapd.conf
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/nis.schema

database bdb
suffix "dc=sanyang,dc=com,dc=my"
rootdn "cn=root,dc=sanyang,dc=com,dc=my"
rootpw mis123

WITH initial.ldif
dn: dc=sanyang,dc=com,dc=my
objectClass: dcObject
objectClass: organization
o: sanyang
dc: sanyang

dn: cn=root,dc=sanyang,dc=com,dc=my
objectClass: organizationalRole
cn: root

It works well.
On another system with exactly the same OS and openldap version [the only difference is the hardware], ldapadd fails with:

# ldapadd -x -D "cn=root,dc=sanyang,dc=com,dc=my" -W -f initial.ldif
Enter LDAP Password:
ldap_bind: Naming violation (64)

I have googled through, no one seems to be having any solution that solves the problem. What drives me crazy is that, i have used exactly the same OS , openldap version and config files, the configuration is simple two steps:
1) edit slapd.conf
2) ldapadd

but, it just don't work on the other server, i have checked over and over again, my slapd.conf is exactly the same, initial.ldif also copied from the working server. I am really wondering if anyone has encountered the same problem like this, now i have setup another server with RHEL5 , the same problem is encountered, i really have no idea what else can i check, hope anyone who knows give me some hint on what is the problem, or any log file to check for error cause?

thanks for taking time reading my query

You can add the "-v" option in the ldapadd command to have a more verbose output, so you maybe find the reason of the problem:

Hi ,
thanks for your reply.
The only info:

ldapadd -vx -D "cn=root,dc=sanyang,dc=com,dc=my" -W -f initial.ldif
ldap_initialize( <DEFAULT> )
Enter LDAP Password:
ldap_bind: Naming violation (64)

Once again, it doesn't give me any hint on whats wrong.
thanks

Doh, it should say what naming attribute had the problem.
Anyway check carefully for typos, move the dc at the top (after the first line), add the top objectClass and see if it works. You can ditch the cn=root,... since this is used just for administration.

Hi,
It is still the same with the updated ldif.
I just tried to delete /var/lib/ldap/ ,reinstall openldap, openldap-servers, openldap-clients.

tried again with your suggestion, still no luck.

its really weird, now the only difference is the hardware, i am not sure if that makes a difference in the ldap configuration it doesnt make sense if it does.

thanks for your help

It's not a hardware problem. Could be a SELinux or something like that, but not hardware.
You can use slapadd to do the same. You have to stop slapd from running before executing slapadd.

Oh, i found one difference between the working and non working servers.

when i type ldapadd, the outcome for both respectively:

working server:
]# ldapadd
SASL/DIGEST-MD5 authentication started
Please enter your password:

Not working server:
# ldapadd
ldap_sasl_interactive_bind_s: No such attribute (16)

SO somehow it is something to do with sasl, i am googling for what am i missing, i have checked i have all
cyrus-sasl-2.1.19-5.EL4
cyrus-sasl-md5-2.1.19-5.EL4
cyrus-sasl-devel-2.1.19-5.EL4
cyrus-sasl-plain-2.1.19-5.EL4

installed.

Anyhow, if anyone knows an answer or jhint, pls help to drop one here, thanks
thanks bathory for your kind assistance

Hi Bathory,

Thanks a lot for your kind assistance.
I think i know why already,
i have another ldap installed on that server, the ldap comes by default from the mail service SCALIX, thanks for your suggestion to try this command:

slapadd -l initial.ldif which says:
# slapadd -l initial.ldif
bdb_db_open: database already in use
backend_startup_one: bi_db_open failed! (-1)
slap_startup failed

Both of the servers that are failing to do ldapadd has scalix server installed in it, no wonder it has conflict...
the one working does not have scalix, it is specically for openldap.

thanks a lot for your help!
No wonder so far i have not encountered such problem eventhough i have implemented dozens of openldap servers before, really a big mistake to overlook scalix-ldap.

have a good day