Editing directly the dse.ldif is a solution as far as the instance is stopped but fyi: your ldapmodify command was missing the -a option (or you should have directly used the ldapadd command)
Without -a option, ldapmodify expect data like: dn: cn=... changetype: ... then the modifier But since your file contains plain entries without changetype you must explicitly tell ldapmodify to add them ! On Fri, Feb 3, 2023 at 4:23 PM Paul Whitney <[email protected]> wrote: > Hi Pierre, > > Thank you so much for the quick response. I tried: > > ldapmodify -f my_groupRoot_of_indexes.ldif -D 'cn=Directory Manager' -w > password -x -H ldap://127.0.0.1:3389 > > But that did not seem to populate the dse.ldif file as I expected. > However, the format of the entries in the index file was the same so I > stopped the service and just appended the file to the dse.ldif (cat > my_groupRoot_of_indexes >> dse.ldif). Service started right back up. > > Now to kick of a reindex. > > Paul M. Whitney, CISSP > Chesapeake IT Consulting, Inc. > 890 Hudson Road > Cambridge, MD 21613 > > Work: 443-492-2872 > Cell: 410.493.9448 > Email: [email protected] > *CONFIDENTIALITY NOTICE* > The information contained in this facsimile or electronic message is > confidential information intended for the use of the individual or entity > named above. If the reader of this message is not the intended recipient, > or an employee or agent responsible for delivering this facsimile message > to the intended recipient, you are hereby notified that any dissemination, > or copying of this communication is strictly prohibited. If this message > contains non-public personal information about any consumer or customer of > the sender or intended recipient, you are further prohibited under penalty > of law from using or disclosing the information to any third party by > provisions of the federal Gramm-Leach-Bliley Act. If you have received this > facsimile or electronic message in error, please immediately notify us by > telephone and return or destroy the original message to assure that it is > not read, copied, or distributed by others. > > ------------------------------ > *From:* Pierre Rogier <[email protected]> > *Sent:* Friday, February 3, 2023 9:44 AM > *To:* General discussion list for the 389 Directory server project. < > [email protected]> > *Subject:* [389-users] Re: Importing Indexes via LDIF > > Hi Paul, > Not using dsconf. > But you could easily do it with ldapsearch and ldapadd > > Regards > Pierre > > On Fri, Feb 3, 2023 at 3:34 PM Paul Whitney < > [email protected]> wrote: > > Greetings, been a while. > > I am looking to migrate to RHEL 9 and 389-DS. In lab stood up a > "supplier" and a "consumer". I have index files for userRoot and > groupRoot. However, indexes appeared to be stored in dse.ldif. Is there a > way using the dsconf command to import an ldif of indexes? > > Thanks, > > Paul M. Whitney, CISSP > Chesapeake IT Consulting, Inc. > 890 Hudson Road > Cambridge, MD 21613 > > Cell: 410.493.9448 > Email: [email protected] > *CONFIDENTIALITY NOTICE* > The information contained in this facsimile or electronic message is > confidential information intended for the use of the individual or entity > named above. If the reader of this message is not the intended recipient, > or an employee or agent responsible for delivering this facsimile message > to the intended recipient, you are hereby notified that any dissemination, > or copying of this communication is strictly prohibited. If this message > contains non-public personal information about any consumer or customer of > the sender or intended recipient, you are further prohibited under penalty > of law from using or disclosing the information to any third party by > provisions of the federal Gramm-Leach-Bliley Act. If you have received this > facsimile or electronic message in error, please immediately notify us by > telephone and return or destroy the original message to assure that it is > not read, copied, or distributed by others. > > _______________________________________________ > 389-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > > > > -- > -- > > 389 Directory Server Development Team > _______________________________________________ > 389-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- -- 389 Directory Server Development Team
_______________________________________________ 389-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
