On 05/27/11 06:01 PM, Bjørn Ruberg wrote:

On 27. mai 2011 07:36, Ian Collins wrote:

...

I am trying to import data from another server into OpenLDAP and I've hit a snag with some dns which contain multiple cn entries:

cn=Services_PM_Champions,cn=Services_PM_Team,ou=groups,o=staff,dc=client

ADD is failing with error 32 (No such object):

conn=1005 op=1236 ADD dn="cn=Service.Admin,ou=groups,o=staff,dc=client" conn=1005 op=1236 RESULT tag=105 err=0 text= conn=1005 op=1237 ADD dn="cn=Services_PM_Champions,cn=Services_PM_Team,ou=groups,o=staff,dc=client"

conn=1005 op=1237 RESULT tag=105 err=32 text=

Should this be accepted?

There's no built-in or RFC constraints saying that a CN can't be a branch node (or parent node). Multiple CNs in a DN is valid. This should not be the reason it's failing.

If your log extract is an attempt to illustrate the problem, it obviously fails:

1. you create "cn=Service.Admin" supposedly as a parent object

No, that was just the order (looks alphabetical) I was receiving the entries.

2. you create "cn=Services_PM_Champions" as a child object under

"cn=Services_PM_Team".

However, "cn=Services_PM_Team" is not "cn=Service.Admin".

You should make sure "cn=Services_PM_Team,ou=groups,o=staff,dc=client" exists.

Yes, I realise that now. I'll have to re-sort the entries prior to insertion.

Thanks.

On 05/27/11 06:07 PM, Philip Guenther wrote:

On Fri, 27 May 2011, Ian Collins wrote:

...

I am trying to import data from another server into OpenLDAP and I've hit a snag with some dns which contain multiple cn entries:

cn=Services_PM_Champions,cn=Services_PM_Team,ou=groups,o=staff,dc=client

ADD is failing with error 32 (No such object):

Well, does the parent DN: cn=Services_PM_Team,ou=groups,o=staff,dc=client

exist?

That's a good point. Looking at the source server, no yes it does. It looks like the entries are being inserted in alphabetical order, rather than parent first.

Thanks.