Thanks for your response. I am trying out with slapacl, in the
mean time can you advice
1) I have master-master mode ldap but all the requests are sent to only one
of the master. The other one is a mere replica. In this case will
objectClass: glue get set?
2) I m sure that in our application if we are deleting anything we delete
all the children nodes,
I mean, if web have a subtree like this one
ou=a --> ou=b --> ou=c
If we delete ou=b, then ou=c also gets deleted. So there shouldnt be
any glued objects.
I assumed that ou=b becoming unavailble may be due to replication I mean
... ou=>b may be in ldap1 and unavailable in ldap2 but tyring to update
ou=>c in ldap2.
In that case will the original objectClass: (in ldap1) gets replaced by
objectClass: glue ?
3) Can you advice how did you ultimately removed all the glued objects and
did you tweek anything in ACL so that it never happened again ?
On Wed, Sep 29, 2010 at 10:49 PM, Marco Pizzoli <marco.pizzoli(a)gmail.com>wrote:
I had the same problem some times ago.
I could be corrected by someone, but the glue is the way by which the OL
system revert to represent entries that are accessible directly.
I mean, if you have a subtree like this one
ou=a --> ou=b --> ou=c
Assume that your ou=b entry is not available anymore for any reason. The
system represent it wuth an entry ou=b of objectClass=glue.
The cause of my problem was related to bad ACLs. So when my n-way
multi-master systems tried to replicate them selves reverted to represent
the entry in that way.
Suggestion: check with slapacl if your entry is accessible by clients
(modifiers, master replicas, ecc...).
On Wed, Sep 29, 2010 at 7:06 PM, karthik kumar <kumarkarthikn(a)gmail.com>wrote:
> Hi ..
> Few of my ldap entries got changed like this
> objectClass: glue
> objectClass: top
> structuralObjectClass: glue
> Those glued entries are not showing up in the ldapsearch. I took a dump
> and from the ldif file, realized the objectClass/ structuralObjectClass got
> I wanted to recover my ldap. So removed all those entries ( including the
> childnodes ). ldapadd them back from a previous dump ( which wasnt glued).
> But after some time when I access those entries from application, they get
> Can you please advice how do I recover my ldap from this.
Non è forte chi non cade, ma chi cadendo ha la forza di rialzarsi.