Hi all. It's been a while since I posted this. Still seems to be an issue. Can anyone give some pointers?

On Jun 17, 2016 4:33 PM, "PenguinWhispererThe" < th3penguinwhisperer@gmail.com> wrote:

Hi all,

I've been trying to update a schema with new olcAttributeTypes and modified an existing objectClass (X) so these attributesTypes may be used with it.

However after adding these attributes to objectClass X I did a "rollback" (replacing the current olcObjectClasses (replace: olcObjectClasses) with the old definition and the same for the olcAttributes (replace: olcAttributeTypes).

I think somewhere along the way something wasn't cleaned up properly. Now when I start slapd service I get: slapd[21335]: UNKNOWN attributeDescription "ATTRIBUTE1 " inserted. slapd[21335]: UNKNOWN attributeDescription "ATTRIBUTE2" inserted. slapd[21335]: [66B blob data]

With slapschema: UNKNOWN attributeDescription "ATTRIBUTE1 " inserted. UNKNOWN attributeDescription "ATTRIBUTE2" inserted. UNKNOWN attributeDescription "ATTRIBUTE3

With slapcat I can't find anything that's matching these names.

When I grep in the mdb file grep says the binary file is matching. However when I ldapsearch for the attribute I can't find it. Neither with slapcat.

Note that I replaced the actual attribute names in the posted output.

So I think I might have some data in that mdb that's not linked to anything anymore. So my question is: how can I clean this up? And/or what did/went wrong?

Thanks in advance for your help.

Thanks for your response Michael. That is indeed what happened. So I'm looking to get those invalid entries removed. The question is: how can I fix my data? Is there some documentation about this? Some specific tools?

As mentioned I can't see those entries using slapcat it seems. So not sure how to locate/remove them.

Thanks in advance!

2016-08-19 19:54 GMT+02:00 Michael Ströder michael@stroeder.com:

PenguinWhispererThe . wrote:

...

Hi all. It's been a while since I posted this. Still seems to be an

issue.

...

Can anyone give some pointers?

Probably you had old attribute type descriptions with that names in your subschema which were removed. But the attributes are still there. Fix your data. Only you can know what those attributes were used for.

Ciao, Michael.

...

On Jun 17, 2016 4:33 PM, "PenguinWhispererThe" < th3penguinwhisperer@gmail.com> wrote:

...

Hi all,

I've been trying to update a schema with new olcAttributeTypes and modified an existing objectClass (X) so these attributesTypes may be

used

...

...

with it.

However after adding these attributes to objectClass X I did a

"rollback"

...

...

(replacing the current olcObjectClasses (replace: olcObjectClasses) with the old definition and the same for the olcAttributes (replace: olcAttributeTypes).

I think somewhere along the way something wasn't cleaned up properly. Now when I start slapd service I get: slapd[21335]: UNKNOWN attributeDescription "ATTRIBUTE1 "

inserted.

...

...

slapd[21335]: UNKNOWN attributeDescription "ATTRIBUTE2" inserted. slapd[21335]: [66B blob data]

With slapschema: UNKNOWN attributeDescription "ATTRIBUTE1 " inserted. UNKNOWN attributeDescription "ATTRIBUTE2" inserted. UNKNOWN attributeDescription "ATTRIBUTE3

With slapcat I can't find anything that's matching these names.

When I grep in the mdb file grep says the binary file is matching. However when I ldapsearch for the attribute I can't find it. Neither with slapcat.

Note that I replaced the actual attribute names in the posted output.

So I think I might have some data in that mdb that's not linked to anything anymore. So my question is: how can I clean this up? And/or what did/went wrong?

Thanks in advance for your help.

PenguinWhispererThe . wrote:

Thanks for your response Michael. That is indeed what happened. So I'm looking to get those invalid entries removed. The question is: how can I fix my data? Is there some documentation about this? Some specific tools?

stop all slapd replicas slapcat sanitize LDIF (grep, sed, python etc.) slapadd start slapd replicas

Ciao, Michael.

Once again thanks for taking your time to followup on this.

I've tried slapcat before to dump to a file and couldn't find the attributes that were mentioned. So today I did it again (just to make sure) and the dump doesn't seem to hold the attributes.

What I did get is : The first database does not allow slapcat; using the first available one (2).

So then I went to the directory and just grepped for the attribute name and it seems that it's matching on a binary file: cn=accesslog/log.000000123123 (changed the number to post).

This seems a good and a bad thing: good as in the actual data has no issues. Bad as in when I restart the service we get the message about the attributes. Is there something slapd does with those log files when it starts that explains it being printed on the screen/syslog?

I only have some "spare" time once in a while to further investigate this as it's not a high priority but I'd like to get rid of it.

2016-09-04 14:07 GMT+02:00 Michael Ströder michael@stroeder.com:

PenguinWhispererThe . wrote:

...

Is "cleaning" my data somewhere like a slapcat and slapadd? This is a replicated environment. Will those changes be propagated? I'd think not

as

...

the import probably keeps the same timestamps.

You have to start from scratch like after a full restore (cleaning the databases before slapadd-ing the sanitized data).

Ciao, Michael.