On 25 May 2013, at 10:00 PM, Graham Leggett minfrin@sharp.fm wrote:
I have indexed the associatedDomain attribute as follows:
dn: cn=associatedDomain,cn=default indexes,cn=config,cn=ldbm database,cn=plu gins,cn=config objectClass: nsIndex objectClass: top cn: associatedDomain nsSystemIndex: false nsIndexType: eq
It just gets weirder and weirder.
We start with no index on the associatedDomain attribute:
[root@monica slapd-monica]# ls -al /var/lib/dirsrv/slapd-monica/db/userRoot/associatedDomain.db4 ls: cannot access /var/lib/dirsrv/slapd-monica/db/userRoot/associatedDomain.db4: No such file or directory
I ask 389ds to create the index on associatedDomain:
[root@monica slapd-monica]# ./db2index.pl -D "cn=Directory Manager" -w - -n userRoot -t associatedDomain Bind Password: adding new entry "cn=db2index_2013_5_25_21_21_43, cn=index, cn=tasks, cn=config"
I watch the log file, 389ds goes through the motions of creating an index on associatedDomain:
[25/May/2013:21:21:42 +0100] - userRoot: Indexing attribute: associatedDomain [snip] [25/May/2013:21:22:11 +0100] - userRoot: Finished indexing.
We end with no index on the associatedDomain attribute, no error message, no nothing:
[root@monica slapd-monica]# ls -al /var/lib/dirsrv/slapd-monica/db/userRoot/associatedDomain.db4 ls: cannot access /var/lib/dirsrv/slapd-monica/db/userRoot/associatedDomain.db4: No such file or directory
This is RHEL6 with 389-ds-base-1.2.11.15-14.el6_4.x86_64.
I am completely stuck, has anybody experienced weirdness like this before? Am I doing the right thing to create the index? Is there some way of coaxing an error of any kind out of 389ds?
Regards, Graham --