Friday, February 3, 2023

[389-users] Re: Importing Indexes via LDIF

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 <paul.whitney@chesapeake-it.com> 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: 
paul.whitney@chesapeake-it.com
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 <progier@redhat.com>
Sent: Friday, February 3, 2023 9:44 AM
To: General discussion list for the 389 Directory server project. <389-users@lists.fedoraproject.org>
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 <paul.whitney@chesapeake-it.com> 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
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 -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
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/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


--
--

389 Directory Server Development Team
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
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/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


--
--

389 Directory Server Development Team

[389-users] 389-DS Cockpit

Is it possible to manage more than one 389-ds HOST through the Cockpit if I import the host descriptions into the slapd-config instance?

In older version with the Java Console, there was a way to merger all of the LDAPS instances into a single view, and could manage them from a single console.

Kudos by the way on making the new Cockpit FIPS friendly!

If I cannot manage the LDAP hosts through a single cockpit, do I really need to create a slapd-config instance anymore?

Paul M. Whitney, CISSP
Chesapeake IT Consulting, Inc.

890 Hudson Road
Cambridge, MD 21613

Cell:   410.493.9448

Email: 
paul.whitney@chesapeake-it.com
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] Re: Importing Indexes via LDIF

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: 
paul.whitney@chesapeake-it.com
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 <progier@redhat.com>
Sent: Friday, February 3, 2023 9:44 AM
To: General discussion list for the 389 Directory server project. <389-users@lists.fedoraproject.org>
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 <paul.whitney@chesapeake-it.com> 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
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 -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
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/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


--
--

389 Directory Server Development Team

[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 <paul.whitney@chesapeake-it.com> 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
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 -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
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/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


--
--

389 Directory Server Development Team

[389-users] Importing Indexes via LDIF

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
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.

Thursday, February 2, 2023

[Test-Announce] Fedora 38 Rawhide 20230202.n.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event
for Fedora 38 Rawhide 20230202.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
anaconda - 20230126.n.0: anaconda-38.18-1.fc38.src, 20230202.n.0: anaconda-38.19-1.fc38.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/38

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230202.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230202.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230202.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230202.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230202.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230202.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230202.n.0_Security_Lab

Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
_______________________________________________
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org
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/test-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Wednesday, February 1, 2023

[fedora-arm] Re: Fedora Minimal 36 installation on raspberry pi 2B

Hello Ben,

I've been using microdnf since then and it works as expected, haven't
had an issue, thanks!

Irene

On Fri, 20 Jan 2023 at 23:47, Ben Herrick <intrep@tauran.net> wrote:
>
> Irene,
>
> You may need to give microdnf a try, as DNF will use all of your 1GB of RAM and get killed by the out-of-memory routines.
>
> <code>
> # rpm -ivh http://mirrors.kernel.org/fedora/updates/36/Everything/armhfp/Packages/m/microdnf-3.9.0-1.fc36.armv7hl.rpm
> # sudo microdnf upgrade --refresh -y
> </code>
>
> There will be a move to DNF5, which will remove some of the memory pressure and improve speed, but it's not scheduled until Fedora 39.
>
> Please note that Fedora 36 is also the last release for ARMHFP (RPI 2B), if I recall correctly.
>
> I hope this helps!
>
> -Ben
>
> On Fri, 2023-01-20 at 22:39 +0000, Irene Diez wrote:
>
> Hello there,
>
> I'm trying to install Fedora-Minimal-36-1.5.armhfp.raw on my raspberry pi 2B. Installation was a success but the device runs out of memory when trying to install anything via dnf and I get kicked out of the shell.
>
> I've followed the installation instructions in https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Manual, which specify that this model is supported since Fedora 29; so, is it there anything that I'm missing for Fedora to work?
>
> Thanks,
>
> Irene
> _______________________________________________
> arm mailing list -- arm@lists.fedoraproject.org
> To unsubscribe send an email to arm-leave@lists.fedoraproject.org
> 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/arm@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
>
> _______________________________________________
> arm mailing list -- arm@lists.fedoraproject.org
> To unsubscribe send an email to arm-leave@lists.fedoraproject.org
> 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/arm@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
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/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue