On Fri, Nov 13, 2015 at 5:25 PM, Alexandros Karypidis <[email protected]> wrote:
> Hi all, > > I am running a 2.0.0-M20 version server and came across an issue. > > There is a 'ghost' entry in the database, which is there, but also isn't > there. What I mean is: > > 1) If I try to create an entry with that DN (ldapmodify with changetype > add) the server complains that the entry already exists > (ERR_250_ENTRY_ALREADY_EXISTS) > > > 2) If I try to update/delete the entry with that DN (ldapmodify with > changetype replace/replace) the server says that there's no such entry > present (NO_SUCH_OBJECT) > > > When I navigate using apache directory studio to the DN, the entry does > not appear on the tree view, as if it doesn't exist... > > QUESTIONS: > > - is there some "fix database" tool I can use to scan the backend storage > and identify issues? > - since the DB seems to be readable otherwise, what is the best way to > "dump" contents of the entire paritition, recreate it and try to re-import > the contents? > take a look at this mail thread http://markmail.org/message/huaqvbqi7djc4swb and see if the tool mentioned in it can recover he partition Please take a regular backup cause the existing backend is prone to data corruption. > > > At the moment I've taken a backup of all Root DSEs using Apache Directory > Studio (export to LDIF) which includes the system/config/schema. However, I > am really using the standard schema that ships by default and only have > some config changes. I also stoppped the server and took a .tar.gz backup > of the instance root (complete with logs, config, etc). > > > BACKGROUND: > > Some information on what happened before this: > > - I was running a script to import some entries (including the offending > one) with ldapmodify > > - I ran an ldapsearch to check the import, and it got stuck > - Repeated attempts to connect with ldapsearch seemed to get stuck forever > (minutes with no output) > > - since the server seemed to be frozen and I did a stop followed by a start > - everything was back to normal, with the exception of this recently added > entry > > > Now, in the logs I see the following errors: > > [14:21:10] ERROR [org.apache.directory.api.asn1.ber.Asn1Decoder] - > ERR_00009_MORE_TLV_EXPECTED The PDU is decoded, but we should have had more > TLVs > > [14:21:10] WARN [org.apache.directory.server.ldap.LdapProtocolHandler] - > Unexpected exception forcing session to close: sending disconnect notice to > client. > org.apache.mina.filter.codec.ProtocolDecoderException: > org.apache.directory.api.ldap.codec.api.ResponseCarryingException: > ERR_00010_TRUNCATED_PDU Truncated > PDU. Some elements are lacking, accordingly to the grammar (Hexdump: [huge > dump of byte values truncated]) > -- Kiran Ayyagari http://keydap.com
