Fedora Info

Saturday, February 7, 2026

Re: Sign in problem at translate.fedoraproject.org

On 6/2/2026 12:48 am, jean-baptiste--- via trans wrote:
> I've reached weblate support, they said it is fixed, somehow your account switched to password mode instead of using FAS auth, please try again
> Jean-Baptiste
>
>

Thank you very much, Jean-Baptiste. I can log in now.

However I don't know how was my account switched to password mode.

[SOLVED]
--
Regards,

Tian
Fedora Project Contributor
--
_______________________________________________
trans mailing list -- trans@lists.fedoraproject.org
To unsubscribe send an email to trans-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/trans@lists.fedoraproject.org
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

Friday, February 6, 2026

[389-users] Re: [EXTERNAL\EXTERNE:] Re: memberof entries not displayed in uid ( version 3.1)

On 2/6/26 2:38 PM, Ghiurea, Isabella via 389-users wrote:

Thank you Viktor , here are more details:

ldapsearch -D "cn=directory manager" -w xxxx-b "ou=Groups,ou=ds,dc=xxxxxxx '(memberOf=*)'

no entries been returned.

That is not exactly what Viktor meant. First, unless its a nested group it will not have a memberOf attribute. So that filter is basically breaking the intended search. Use "cn=*" as the filter instead.

In your groups the memberOf plugin will only check if "member" attribute is set. If your groups use "uniquemember" then you will need to update the memberOf plugin configuration (memberofgroupattr) and restart the server. Then run the fixup task.

Secondly, in your "users" you need an objectclass that allows the "memberOf" attribute. The plugin "should" auto-add an appropriate objectclass if one is not present, but that could be an issue.

I suspect you are using uniquemember as your membership attribute in your groups, so you just need to update the plugin config, restart the server, and run the fixup task.

Regards,

Mark

dsconf -D "cn=Directory Manager" -W slapd-testldap backend index list userroot | grep member*

dn: cn=member,cn=index,cn=userroot,cn=ldbm database,cn=plugins,cn=config
cn: member
dn: cn=memberOf,cn=index,cn=userroot,cn=ldbm database,cn=plugins,cn=config
cn: memberOf
dn: cn=memberuid,cn=index,cn=userroot,cn=ldbm database,cn=plugins,cn=config
cn: memberuid
dn: cn=uniquemember,cn=index,cn=userroot,cn=ldbm database,cn=plugins,cn=config
cn: uniquemember

####### See the memberof difference in version 1.2 with version 3.1 for memberofgroupattr is this the case ?

dn: cn=MemberOf Plugin,cn=plugins,cn=config
objectClass: top
objectClass: nsSlapdPlugin
objectClass: extensibleObject
cn: MemberOf Plugin
nsslapd-pluginPath: libmemberof-plugin
nsslapd-pluginInitfunc: memberof_postop_init
nsslapd-pluginType: betxnpostoperation
nsslapd-pluginEnabled: on
nsslapd-plugin-depends-on-type: database
memberofgroupattr: member
memberofattr: memberOf
nsslapd-pluginId: memberof
nsslapd-pluginVersion: 3.1.3
nsslapd-pluginVendor: 389 Project
################

dn: cn=MemberOf Plugin,cn=plugins,cn=config
objectClass: top
objectClass: nsSlapdPlugin
objectClass: extensibleObject
cn: MemberOf Plugin
nsslapd-pluginPath: libmemberof-plugin
nsslapd-pluginInitfunc: memberof_postop_init
nsslapd-pluginType: betxnpostoperation
nsslapd-pluginEnabled: on
nsslapd-plugin-depends-on-type: database
memberofgroupattr: uniquemember
memberofattr: memberOf
nsslapd-pluginId: memberof
nsslapd-pluginVersion: 1.3.10.2

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

And last question the memberof fixup scripts runs to fast /or not at all but no errors.

dsconf --verbose testldap plugin memberof fixup-status

Task: cn=memberOf_fixup_2026-02-06T11:19:50.854371,cn=memberOf task,cn=tasks,cn=config
INFO: --------------------------------------------------------------------------------
INFO: - Base DN:       dc=xxxx
INFO: - Status:        Memberof task finished (processed 45844 entries in 6 seconds)
INFO: - Started:       Fri Feb 6 19:19:50 2026 (20260206191950Z)
INFO: - Ended:         Fri Feb 6 19:19:57 2026 (20260206191957Z)
INFO: - Elapsed Time: 0:00:07
INFO: - Exit Code:     0

Thank you!!!

From: Viktor Ashirov <vashirov@redhat.com>
Sent: Friday, February 6, 2026 3:21:43 AM
To: General discussion list for the 389 Directory server project.
Cc: Ghiurea, Isabella
Subject: [EXTERNAL\EXTERNE:] Re: [389-users] memberof entries not displayed in uid ( version 3.1)

***Attention*** This email originated from outside of the NRC. ***Attention*** Ce courriel provient de l'extérieur du CNRC.

Hi,

On Fri, Feb 6, 2026 at 4:33 AM Ghiurea, Isabella via 389-users <389-users@lists.fedoraproject.org> wrote:

Hi List,

I 'm testing DS migration from 389-DS 1.2.3 to 389-DS 3.1 RH9 with memberof plugin been enable when checking for users the entries for memberof are missing. for each uid.

Are any cfg params in dse.ldif which may stop from displaying the memberof entries ?

See details :

# 8211065Users, ds, xxxx

dn: uid=8211065,ou=Users,ou=ds,dc=xxxxx

userPassword:: e1NTSEF9K25kcXZ

= Missing memberOf entries

In old 389-DS version 1.2.3 I have for same uid

dn: uid=8211065ou=Users,ou=ds,dc=xxxx

****memberOf: cn=xxxx,ou=Groups,ou=ds,dc=xxxxxxx >>> mssing for each uid in 389-DS version 3.1

****memberOf: cn=xxxx-users,ou=Groups,ou=ds,dc=cxxxx >>>same

#######################################

DS version 3.1 errorlog

dsconf slapd-testldap plugin memberof fixup "dc=xxx,dc=xxx"

dsconf slapd-testldap plugin memberof fixup-status

INFO - memberof-plugin - memberof_fixup_task_thread - Memberof task starts (filter: "(|(objectclass=inetuser)(objectclass=inetadmin)(objectclass=nsmemberof))") ...

[05/Feb/2026:18:44:51.265924012 -0800] - INFO - memberof-plugin - memberof_fixup_task_thread - Memberof task finished (processed 45844 entries in 5 seconds)

######################################################

dsconf slapd-testldap plugin memberof show

dn: cn=MemberOf Plugin,cn=plugins,cn=config

cn: MemberOf Plugin

memberofattr: memberOf

memberofgroupattr: member

What does your group entry look like? Do you have objectclass that supports the `member` attribute?

Thanks.

nsslapd-plugin-depends-on-type: database

nsslapd-pluginDescription: memberof plugin

nsslapd-pluginEnabled: on

nsslapd-pluginId: memberof

nsslapd-pluginInitfunc: memberof_postop_init

nsslapd-pluginPath: libmemberof-plugin

nsslapd-pluginType: betxnpostoperation

nsslapd-pluginVendor: 389 Project

nsslapd-pluginVersion: 3.1.3

objectClass: top

objectClass: nsSlapdPlugin

objectClass: extensibleObject

Thank you

Isabella

--
_______________________________________________
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://forge.fedoraproject.org/infra/tickets/issues/new

--

Viktor

--   Identity Management Development Team

[389-users] Re: [EXTERNAL\EXTERNE:] Re: Re: 3.1 version where i are ndexes ?

On 2/6/26 12:28 PM, Ghiurea, Isabella via 389-users wrote:

Thank you for replies , still some confusing see bellow :

dsconf -D "cn=Directory Manager" -W slapd-testldap backend index add --attr nsaccountlock --index-type eq userroot

Error: Already exists(68)>>

So index is already there but this dbscan says :
dbscan -D mdb -s -f /var/lib/dirsrv/slapd-testldap/db/userroot/nsaccountlock
Empty database!

You need to index the attribute after adding the index configuration. You can add "--reindex" option to your command. This is also how it worked with BDB.

HTH,
Mark

Thank you
Isabella

From: Pierre Rogier <progier@redhat.com>
Sent: Friday, February 6, 2026 3:49:42 AM
To: General discussion list for the 389 Directory server project.
Cc: Ghiurea, Isabella; Viktor Ashirov
Subject: [EXTERNAL\EXTERNE:] Re: [389-users] Re: 3.1 version where i are ndexes ?

***Attention*** This email originated from outside of the NRC. ***Attention*** Ce courriel provient de l'extérieur du CNRC.

Hello,
The above dbstat commands are for RH 10 but when using lmdb on RH 9 you have to specify you want to use lmdb:

dbscan -D mdb -L /var/lib/dirsrv/slapd-localhost/db

dbscan -D mdb -s -f /var/lib/dirsrv/slapd-localhost/db/userroot/parentid.db

Regards
--
Pierre

On Fri, Feb 6, 2026 at 12:35 PM Viktor Ashirov via 389-users <389-users@lists.fedoraproject.org> wrote:

Hi,

with LMDB backend data.mdb contains all data: backends, indexes, entries. You don't need to create anything yourself.

dbscan can display all sub-dbs:

dbscan -L /var/lib/dirsrv/slapd-localhost/db

or you can access individual indexes:

dbscan -s -f /var/lib/dirsrv/slapd-localhost/db/userroot/parentid.db

HTH
Equality index keys: 13

On Thu, Feb 5, 2026 at 8:33 PM Ghiurea, Isabella via 389-users <389-users@lists.fedoraproject.org> wrote:

HI List

I 'm testing a new 389-DS version 3.1 i RH 9 installation, I followed the RH Doc for migration from version 1.2.3 copy only content and user.ldif , I re-create my indexes with dsconf but I can not find where are this new LMDB indexes files? ( Iin old 1.2.3 I used the default userroot , but I can not find such userroot db in latest veersion ?)

Do I need to create userroot directory before or after indexes creation ?

sslapd-db-home-directory: /var/lib/dirsrv/slapd-test/db

/var/lib/dirsrv/slapd-testl/db/

w-r--r--. 1 dirsrv dirsrv 75 Feb 5 09:27 INFO.mdb

-rw-------. 1 dirsrv dirsrv 15899 Feb 5 09:27 data.mdb

-rw-------. 1 dirsrv dirsrv 8192 Feb 5 11:16 lock.mdb

Thank you

Isabella

--
_______________________________________________
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://forge.fedoraproject.org/infra/tickets/issues/new

--

Viktor

--
_______________________________________________
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://forge.fedoraproject.org/infra/tickets/issues/new

--

--

389 Directory Server Development Team

--   Identity Management Development Team

[389-users] Re: [EXTERNAL\EXTERNE:] Re: memberof entries not displayed in uid ( version 3.1)

Thank you Viktor , here are more details:

ldapsearch -D "cn=directory manager" -w xxxx-b "ou=Groups,ou=ds,dc=xxxxxxx '(memberOf=*)'

no entries been returned.

dsconf -D "cn=Directory Manager" -W slapd-testldap backend index list userroot | grep member*

dn: cn=member,cn=index,cn=userroot,cn=ldbm database,cn=plugins,cn=config
cn: member
dn: cn=memberOf,cn=index,cn=userroot,cn=ldbm database,cn=plugins,cn=config
cn: memberOf
dn: cn=memberuid,cn=index,cn=userroot,cn=ldbm database,cn=plugins,cn=config
cn: memberuid
dn: cn=uniquemember,cn=index,cn=userroot,cn=ldbm database,cn=plugins,cn=config
cn: uniquemember

####### See the memberof difference in version 1.2 with version 3.1 for memberofgroupattr is this the case ?

dn: cn=MemberOf Plugin,cn=plugins,cn=config
objectClass: top
objectClass: nsSlapdPlugin
objectClass: extensibleObject
cn: MemberOf Plugin
nsslapd-pluginPath: libmemberof-plugin
nsslapd-pluginInitfunc: memberof_postop_init
nsslapd-pluginType: betxnpostoperation
nsslapd-pluginEnabled: on
nsslapd-plugin-depends-on-type: database
memberofgroupattr: member
memberofattr: memberOf
nsslapd-pluginId: memberof
nsslapd-pluginVersion: 3.1.3
nsslapd-pluginVendor: 389 Project
################

dn: cn=MemberOf Plugin,cn=plugins,cn=config
objectClass: top
objectClass: nsSlapdPlugin
objectClass: extensibleObject
cn: MemberOf Plugin
nsslapd-pluginPath: libmemberof-plugin
nsslapd-pluginInitfunc: memberof_postop_init
nsslapd-pluginType: betxnpostoperation
nsslapd-pluginEnabled: on
nsslapd-plugin-depends-on-type: database
memberofgroupattr: uniquemember
memberofattr: memberOf
nsslapd-pluginId: memberof
nsslapd-pluginVersion: 1.3.10.2

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

And last question the memberof fixup scripts runs to fast /or not at all but no errors.

dsconf --verbose testldap plugin memberof fixup-status

Task: cn=memberOf_fixup_2026-02-06T11:19:50.854371,cn=memberOf task,cn=tasks,cn=config
INFO: --------------------------------------------------------------------------------
INFO: - Base DN:       dc=xxxx
INFO: - Status:        Memberof task finished (processed 45844 entries in 6 seconds)
INFO: - Started:       Fri Feb 6 19:19:50 2026 (20260206191950Z)
INFO: - Ended:         Fri Feb 6 19:19:57 2026 (20260206191957Z)
INFO: - Elapsed Time: 0:00:07
INFO: - Exit Code:     0

Thank you!!!

From: Viktor Ashirov <vashirov@redhat.com>
Sent: Friday, February 6, 2026 3:21:43 AM
To: General discussion list for the 389 Directory server project.
Cc: Ghiurea, Isabella
Subject: [EXTERNAL\EXTERNE:] Re: [389-users] memberof entries not displayed in uid ( version 3.1)

***Attention*** This email originated from outside of the NRC. ***Attention*** Ce courriel provient de l'extérieur du CNRC.

Hi,

On Fri, Feb 6, 2026 at 4:33 AM Ghiurea, Isabella via 389-users <389-users@lists.fedoraproject.org> wrote:

Hi List,

I 'm testing DS migration from 389-DS 1.2.3 to 389-DS 3.1 RH9 with memberof plugin been enable when checking for users the entries for memberof are missing. for each uid.

Are any cfg params in dse.ldif which may stop from displaying the memberof entries ?

See details :

# 8211065Users, ds, xxxx

dn: uid=8211065,ou=Users,ou=ds,dc=xxxxx

userPassword:: e1NTSEF9K25kcXZ

= Missing memberOf entries

In old 389-DS version 1.2.3 I have for same uid

dn: uid=8211065ou=Users,ou=ds,dc=xxxx

****memberOf: cn=xxxx,ou=Groups,ou=ds,dc=xxxxxxx >>> mssing for each uid in 389-DS version 3.1

****memberOf: cn=xxxx-users,ou=Groups,ou=ds,dc=cxxxx >>>same

#######################################

DS version 3.1 errorlog

dsconf slapd-testldap plugin memberof fixup "dc=xxx,dc=xxx"

dsconf slapd-testldap plugin memberof fixup-status

INFO - memberof-plugin - memberof_fixup_task_thread - Memberof task starts (filter: "(|(objectclass=inetuser)(objectclass=inetadmin)(objectclass=nsmemberof))") ...

[05/Feb/2026:18:44:51.265924012 -0800] - INFO - memberof-plugin - memberof_fixup_task_thread - Memberof task finished (processed 45844 entries in 5 seconds)

######################################################

dsconf slapd-testldap plugin memberof show

dn: cn=MemberOf Plugin,cn=plugins,cn=config

cn: MemberOf Plugin

memberofattr: memberOf

memberofgroupattr: member

What does your group entry look like? Do you have objectclass that supports the `member` attribute?

Thanks.

nsslapd-plugin-depends-on-type: database

nsslapd-pluginDescription: memberof plugin

nsslapd-pluginEnabled: on

nsslapd-pluginId: memberof

nsslapd-pluginInitfunc: memberof_postop_init

nsslapd-pluginPath: libmemberof-plugin

nsslapd-pluginType: betxnpostoperation

nsslapd-pluginVendor: 389 Project

nsslapd-pluginVersion: 3.1.3

objectClass: top

objectClass: nsSlapdPlugin

objectClass: extensibleObject

Thank you

Isabella

--
_______________________________________________
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://forge.fedoraproject.org/infra/tickets/issues/new

Viktor

[389-users] Re: [EXTERNAL\EXTERNE:] Re: Re: 3.1 version where i are ndexes ?

Thank you for replies , still some confusing see bellow :

dsconf -D "cn=Directory Manager" -W slapd-testldap backend index add --attr nsaccountlock --index-type eq userroot

Error: Already exists(68)>>

So index is already there but this dbscan says :
dbscan -D mdb -s -f /var/lib/dirsrv/slapd-testldap/db/userroot/nsaccountlock
Empty database!

Thank you

Isabella

From: Pierre Rogier <progier@redhat.com>
Sent: Friday, February 6, 2026 3:49:42 AM
To: General discussion list for the 389 Directory server project.
Cc: Ghiurea, Isabella; Viktor Ashirov
Subject: [EXTERNAL\EXTERNE:] Re: [389-users] Re: 3.1 version where i are ndexes ?

***Attention*** This email originated from outside of the NRC. ***Attention*** Ce courriel provient de l'extérieur du CNRC.

Hello,
The above dbstat commands are for RH 10 but when using lmdb on RH 9 you have to specify you want to use lmdb:

dbscan -D mdb -L /var/lib/dirsrv/slapd-localhost/db

dbscan -D mdb -s -f /var/lib/dirsrv/slapd-localhost/db/userroot/parentid.db

Regards

--
Pierre

On Fri, Feb 6, 2026 at 12:35 PM Viktor Ashirov via 389-users <389-users@lists.fedoraproject.org> wrote:

Hi,

with LMDB backend data.mdb contains all data: backends, indexes, entries. You don't need to create anything yourself.

dbscan can display all sub-dbs:

dbscan -L /var/lib/dirsrv/slapd-localhost/db

or you can access individual indexes:

dbscan -s -f /var/lib/dirsrv/slapd-localhost/db/userroot/parentid.db

HTH
Equality index keys: 13

On Thu, Feb 5, 2026 at 8:33 PM Ghiurea, Isabella via 389-users <389-users@lists.fedoraproject.org> wrote:

HI List

I 'm testing a new 389-DS version 3.1 i RH 9 installation, I followed the RH Doc for migration from version 1.2.3 copy only content and user.ldif , I re-create my indexes with dsconf but I can not find where are this new LMDB indexes files? ( Iin old 1.2.3 I used the default userroot , but I can not find such userroot db in latest veersion ?)

Do I need to create userroot directory before or after indexes creation ?

sslapd-db-home-directory: /var/lib/dirsrv/slapd-test/db

/var/lib/dirsrv/slapd-testl/db/

w-r--r--. 1 dirsrv dirsrv 75 Feb 5 09:27 INFO.mdb

-rw-------. 1 dirsrv dirsrv 15899 Feb 5 09:27 data.mdb

-rw-------. 1 dirsrv dirsrv 8192 Feb 5 11:16 lock.mdb

Thank you

Isabella

--
_______________________________________________
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://forge.fedoraproject.org/infra/tickets/issues/new

--

Viktor

--
_______________________________________________
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://forge.fedoraproject.org/infra/tickets/issues/new

--

389 Directory Server Development Team

[389-users] Re: Migration to RHEL 9 389-DS from CentOS 7

Hi Paul,

The log.0 files are the bdb transaction logs file.
You should never remove them manually. (Risk of breaking the db recovery)
In theory they are supposed to be removed by the checkpointing thread as it process the files.

Regards
Pierre

On Fri, Feb 6, 2026 at 2:57 PM Paul Whitney via 389-users <389-users@lists.fedoraproject.org> wrote:

Good morning,

We are finally migrating from 389-ds-base 1.3.7.5 to 2.7.0-7.

My scenario:

I have deployed several suppliers in a multi-replication configuration, the same as I did with the CentOS 7 deployment. I have one replication agreement from a CentOS 7 supplier to a RHEL 9 supplier. The RHEL 9 supplier then replicates to all of the other suppliers.

A couple of questions:

Should the CSN count be identical between the CentOS 7 and RHEL 9?

Regarding initializing the hosts, when I initialize a supplier, a lot of log.0 type files get created in the /var/lib/dirsrv/slapd-name/db directory. If I don't monitor the partition there is a risk of filling up to 100%.



What are these files? Does it hurt to remove them?

And when importing, after a pass restarts, would it not make sense that those files get cleaned up in the initializing process to avoid filling up the partition?

Thanks,

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.

--
_______________________________________________
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://forge.fedoraproject.org/infra/tickets/issues/new

--

389 Directory Server Development Team

[389-users] Migration to RHEL 9 389-DS from CentOS 7

Good morning,

We are finally migrating from 389-ds-base 1.3.7.5 to 2.7.0-7.

My scenario:

I have deployed several suppliers in a multi-replication configuration, the same as I did with the CentOS 7 deployment. I have one replication agreement from a CentOS 7 supplier to a RHEL 9 supplier. The RHEL 9 supplier then replicates to all of the other suppliers.

A couple of questions:

Should the CSN count be identical between the CentOS 7 and RHEL 9?

Regarding initializing the hosts, when I initialize a supplier, a lot of log.0 type files get created in the /var/lib/dirsrv/slapd-name/db directory. If I don't monitor the partition there is a risk of filling up to 100%.

What are these files? Does it hurt to remove them?
And when importing, after a pass restarts, would it not make sense that those files get cleaned up in the initializing process to avoid filling up the partition?

Thanks,

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.