On Fri, Jun 19, 2015 at 5:03 AM, Jeremy Page <[email protected]> wrote:

> Hello all, I am running into what I suspect is a corrupted db. I'm
>
yes, as Emmanuel said the problem is with the db files.

> running M17 and the system had an unexpected power outage & now I'm
> unable to dump the system OU. This was working previously, any
> suggestions on what to do to determine what the problem is? I can dump
> the children OUs but not the base.
>
> however most of the time (read 99%) this only affects the index files and
rebuilding
them can fix this issue,

I have created a tool[1] to make this easier, you may give it a try by
following the steps
mentioned in the HOWTO.txt file present inside that repo

Let me know if you run into any issues.

[1]
https://svn.apache.org/repos/asf/directory/sandbox/kayyagari/partition-plumber/

box#ldapsearch -v -h localhost  -p 10389 -D uid=admin,ou=system -w
> secret  -b ou=system  -LLL
> <snip returned data, should be 100's of entries, actually returns  17>
> Other (e.g., implementation specific) error (80)
> Additional information: OTHER: failed for MessageType : SEARCH_REQUEST
> Message ID : 2
>     SearchRequest
>         baseDn : 'ou=system'
>         filter : '(objectClass=*)'
>         scope : whole subtree
>         typesOnly : false
>         Size Limit : no limit
>         Time Limit : no limit
>         Deref Aliases : never Deref Aliases
>         attributes :
> org.apache.directory.api.ldap.model.message.SearchRequestImpl@edfbb118:
> null
>
> Please be advised that this email may contain confidential information. If
> you are not the intended recipient, please notify us by email by replying
> to the sender and delete this message. The sender disclaims that the
> content of this email constitutes an offer to enter into, or the acceptance
> of, any agreement; provided that the foregoing does not invalidate the
> binding effect of any digital or other electronic reproduction of a manual
> signature that is included in any attachment.
>



-- 
Kiran Ayyagari
http://keydap.com

Reply via email to