389-users January 2019

389-users@lists.fedoraproject.org

11 participants
17 discussions

Problem browsing LDAP with Outlook
by Chris Bryant 26 Aug '20

26 Aug '20

When configuring Microsoft Outlook (not Outlook Express) to access an LDAP directory, there is an option to 'Enable Browsing (requires server support)'. If this option is chosen and the directory server supports it, then you should be able to open the LDAP address book and page up and down through the results. I have been unable to get this working properly with 389 DS. When I try to browse from Outlook against the 389 DS directory, I am able to see the first page of results perfectly. However, if I move to the next page, only the first object returned will have any attributes included, and all of the rest of the objects in the page will have no attributes. I have a test perl script that duplicates this functionality as well. I can get this to work properly with an older version of Netscape Directory Server, and I can get it working with OpenDS. Since 389 DS advertises support for the controls that are required for this to work, just like the other two servers, then I would expect it to work there also. Has anyone out there gotten this to work with 389 DS? If so, can you share if there was anything special that you needed to do to get this to work? I'm trying to determine if this is a bug in the server, or if I'm just missing something in the configuration. Thanks, Chris USA.NET You Run Your Business. We'll Run Your Email. This message is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information of USA.NET, Inc. Any unauthorized review, use, copying, disclosure, or distribution is prohibited. If you are not the intended recipient, please immediately contact the sender by reply email and delete all copies of the original message.

3 2

MemberOf group restrictions to a client system (server and client running CentOS 7)
by Janet Houser 06 Aug '20

06 Aug '20

Hi, I'm new to 389-ds and last week downloaded and installed the software. I have a running instance of the server, and I've added TLS/SSL. I've configured a CentOS 7 client to be able to query the server using TLS/SSL, and all appears working. I've created users and groups on the 389-ds server successfully. For each user and group, I've enabled posix attributes and my client can see the unix users and groups using the "getent password" or "getent group" commands. Now, here's where I'm getting tripped up.......... I need to limit which users have access to which systems. I've been trying to do this via memberOf group limitations. I found the following online resource (https://thornelabs.net/2013/01/28/aix-restrict-server-login-via-ldap-groups…) which is close enough to CentOS that the initial commands worked. I enabled the MemberOf plugin and changed the attributes per the link, and restarted the system. I created a test group (that I didn't enable a posix GID) and tried to add a single user via: Right click on group -- > click Properties --> then Members --> click Add --> Search for user --> click Add. When I try to go this route (which worked before enabling the memberOf plugin) it worked. Now it seems I get the error: "Cannot save to directory server. netscape.ldap.LDAPException: error resiult(65): Object class violation" And the messages file throws the error (/var/log/dirsrv/slapd-<instancename>/errors: "Entry "uid=test,ou=People,dc=int,dc=com" -- attribute "memberOf" not allowed [17/Feb/2016:11:22:58 -0700] memberof-plugin - memberof_postop_modify: failed to add dn (cn=testgroup,ou=Groups,dc=int,dc=com) to target. Error (65)" So it seems my server isn't quite using the memberOf plugin properly, but I'm not sure what else to enable. I'll have to solve this issue before I even try to filter login access via groups on my client system. I should mention that if I go under the advanced tab for one of the groups I created, I can add the the attribute "uniquemember", but I'm not sure what I should set the "value" to be. I've tried creating new users to see if I could set their "uniquemember" attributes, but no luck. It seems that I don't have the ability to set this attribute on individual users, only groups. This might not be the right road to head down when trying to restrict access to servers via groups, so I'm open to any suggestions. Any suggestions would be appreciated.

6 19

tls encryption and key changes: symmetric key failed to unwrap
by Jan Kowalsky 04 Feb '19

04 Feb '19

Hi all, we have the following situation: An 389ds with tls/ssl configured whith an certificate from letsencrypt. Since letsencrypt is short-dated we have an automated update routine for regenerating the cert8.db. Now we have this sort of errors in changelog. [01/Jun/2018:11:46:40 +0200] attrcrypt - attrcrypt_unwrap_key: failed to unwrap key for cipher AES [01/Jun/2018:11:46:40 +0200] attrcrypt - attrcrypt_cipher_init: symmetric key failed to unwrap with the private key; Cert might have been renewed since the key is wrapped. To recover the encrypted contents, keep the wrapped symmetric key value. [01/Jun/2018:11:46:40 +0200] attrcrypt - attrcrypt_unwrap_key: failed to unwrap key for cipher 3DES [01/Jun/2018:11:46:40 +0200] attrcrypt - attrcrypt_cipher_init: symmetric key failed to unwrap with the private key; Cert might have been renewed since the key is wrapped. To recover the encrypted contents, keep the wrapped symmetric key value. [01/Jun/2018:11:46:40 +0200] attrcrypt - All prepared ciphers are not available. Please disable attribute encryption. I never used attribute encryption and we don't need it at the moment. But as far as I understand, it's based on the server private key. This is the one we change every 60 days. The best idea seems to disable attribute encryption (which doesn't make much sense if the private key isn't password protected anyway). Or is there any other way to deal with key changes? Thanks and regards Jan

4 5

Announcing 389 Directory Server 1.4.0.21
by Mark Reynolds 31 Jan '19

31 Jan '19

389 Directory Server 1.4.0.21 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.0.21 Fedora packages are available on Fedora 28, and 29 Fedora 29 https://koji.fedoraproject.org/koji/taskinfo?taskID=32370360 <https://koji.fedoraproject.org/koji/taskinfo?taskID=32370360> Fedora 28 https://koji.fedoraproject.org/koji/taskinfo?taskID=32370472 <https://koji.fedoraproject.org/koji/taskinfo?taskID=32370472> Bodhi F29 https://bodhi.fedoraproject.org/updates/FEDORA-2019-dfb56cca7b <https://bodhi.fedoraproject.org/updates/FEDORA-2019-dfb56cca7b> F28 https://bodhi.fedoraproject.org/updates/FEDORA-2019-201ffffa3e <https://bodhi.fedoraproject.org/updates/FEDORA-2019-201ffffa3e> The new packages and versions are: * 389-ds-base-1.4.0.21-1 Source tarballs are available for download at Download 389-ds-base Source <https://releases.pagure.org/389-ds-base/389-ds-base-1.4.0.21.tar.bz2> Highlights in 1.4.0.21 Bug fixes Installation and Upgrade See Download <https://www.port389.org/docs/389ds/download.html> for information about setting up your yum repositories. To install, use *dnf install 389-ds-base*, then run *dscreate*. For Cockput UI plugin use “dnf install cockpit-389-ds” See Install_Guide <https://www.port389.org/docs/389ds/howto/howto-install-389.html> for more information about the initial installation, setup, and upgrade See Source <https://www.port389.org/docs/389ds/development/source.html> for information about source tarballs and SCM (git) access. Feedback We are very interested in your feedback! Please provide feedback and comments to the 389-users mailing list: https://lists.fedoraproject.org/admin/lists/389-users.lists.fedoraproject.o… If you find a bug, or would like to see a new feature, file it in our Pagure project: https://pagure.io/389-ds-base * Bump version to 1.4.0.21 * Ticket 50041 - CLI and WebUI - Add memberOf plugin functionality * Ticket 50079 - Fix for ticket 50059: If an object is nsds5replica, it must be cn=replica * Ticket 50125 - perl fix ups for tmpfiles * Ticket 50164 - Add test for dscreate * Ticket 50059 - If an object is nsds5replica, it must be cn=replica * Ticket 50169 - lib389 changed hardcoded systemctl path * Ticket 50165 - Fix dscreate issues * Ticket 50152 - Replace os.getenv(‘HOME’) with os.path.expanduser * Fix compiler warning in snmp main() * Fix compiler warning in init.c * Ticket 49540 - FIx compiler warning in ldif2ldbm * Ticket 50077 - Fix compiler warnings in automember rebuild task * Ticket 49972 - use-after-free in case of several parallel krb authentication * Ticket 50161 - Fixed some descriptions in “dsconf backend –help” * Ticket 50153 - Increase default max logs * Ticket 50123 - with_tmpfiles_d is associated to systemd * Ticket 49984 - python installer add option to create suffix entry * Ticket 50077 - RFE - improve automember plugin to work with modify ops * Ticket 50136 - Allow resetting passwords on the CLI * Ticket 49994 - Adjust dsconf backend usage * Ticket 50138 - db2bak.pl -P LDAPS does not work when nsslapd-securePort is missing * Ticket 50122 - Fix incorrect path spec * Ticket 50145 - Add a verbose option to the backup tools * Ticket 50056 - dsctl db2ldif throws an exception * Ticket 50078 - cannot add cenotaph in read only consumer * Ticket 50126 - Incorrect usage of sudo in test * Ticket 50130 - Building RPMs on RHEL8 fails * Ticket 50134 - fixup-memberof.pl does not respect protocol requested * Ticket 50122 - Selinux test for presence * Ticket 50101 - Port fourwaymmr Test TET suit to python3 * Ticket 50091 - shadowWarning is not generated if passwordWarning is lower than 86400 seconds (1 day). * Ticket 50128 - NS Stress fails without ipv6 * Ticket 49618 - Set nsslapd-cachememsize to custom value * Ticket 50117 - after certain failed import operation, impossible to replay an import operation * Ticket 49999 - rpm.mk dist-bz2 should clean cockpit_dist first * Ticket 48064 - Fix various issues in disk monitoring test suite * Ticket 49938 - lib389 - Clean up CLI logging * Ticket 49761 - Fix CI test suite issues * Ticket 50056 - Fix UI bugs (part 2) * Ticket 48064 - CI test - disk_monitoring * Ticket 50099 - extend error messages * Ticket 50099 - In FIPS mode, the server can select an unsupported password storage scheme * Ticket 50041 - Add basic plugin UI/CLI wrappers * Ticket 50082 - Port state test suite * Ticket 49574 - remove index subsystem * Ticket 49588 - Add py3 support for tickets : part-5 * Ticket 50095 - cleanup deprecated key.h includes

1 0

Re: Import an ldif
by Mark Reynolds 31 Jan '19

31 Jan '19

On 1/31/19 9:51 AM, John.Berger(a)us.fujitsu.com wrote: > > Mark, > > Thanks for the follow up. I was able to change the schema value to > off just fine. However, when we edited the dse.ldif file for the DS > that is running on port 389 (slapd-test) the nsslapd-syntaxcheck: > offvalue was not in the file so we just added it and restarted the > ldap server. The import still failed to pull in the users that had > values that were blank. > > Most likely I am missing something or edited the wrong dse.ldif file. > This is why I said to use ldapmodify. If you edit dse.ldif while the server is running those changes get overwritten. If you want to directly edit dse.ldif, then stop the server first and then make your changes. Try that and let me know how it goes. Thanks, Mark > Please bear with me because I am not a Unix person at all, so many > times things like this confuse me. > > My apologies, > > John > > *From:*Mark Reynolds <mreynolds(a)redhat.com> > *Sent:* Wednesday, January 30, 2019 3:11 PM > *To:* General discussion list for the 389 Directory server project. > <389-users(a)lists.fedoraproject.org>; Berger, John > <John.Berger(a)us.fujitsu.com> > *Subject:* Re: [389-users] Import an ldif > > On 1/30/19 3:58 PM, John.Berger(a)us.fujitsu.com > <mailto:John.Berger@us.fujitsu.com> wrote: > > We are trying to import an ldif file from our old Sun One > Directory Server 5.2. We have the 389 server set up and running. I > can initialize the database I want to import in and it seems to > work fine. However, we have a lot of users that do not get > imported in due a syntax error on certain attributes because they > are blank. Example: We have an attribute called Title which was > never required so many of the users have it blank. These error on > import. *Is there a way to get the 389 server to disregard that > and load the user anyway? Basically we want to pull everything in > even if the fields are blank.* > > Ideally you could write a script to strip those empty attributes from > the LDIF. > > Otherwise you can turn off schema checking (syntax checking might also > need to be disabled) > > cn=config > nsslapd-schemacheck: off > nsslapd-syntaxcheck: off > > Use ldapmodify to set these attributes (same as Sun DS), and stop the > server before you import. After the import completes you should turn > these settings back "on". > > HTH, > > Mark > > * > > * > > Regards, > > John > > > > _______________________________________________ > > 389-users mailing list --389-users(a)lists.fedoraproject.org <mailto:389-users@lists.fedoraproject.org> > > To unsubscribe send an email to389-users-leave(a)lists.fedoraproject.org <mailto:389-users-leave@lists.fedoraproject.org> > > Fedora Code of Conduct:https://getfedora.org/code-of-conduct.html <https://urldefense.proofpoint.com/v2/url?u=https-3A__getfedora.org_code-2Do…> > > List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines <https://urldefense.proofpoint.com/v2/url?u=https-3A__fedoraproject.org_wiki…> > > List Archives:https://lists.fedoraproject.org/archives/list/389-users@lists.fedo… <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.fedoraproject.or…> >

1 0

Announcing 389 Directory Server 1.4.1.1
by Mark Reynolds 30 Jan '19

30 Jan '19

389 Directory Server 1.4.1.1 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.1.1 Fedora packages are available on Fedora 30 (rawhide). https://koji.fedoraproject.org/koji/taskinfo?taskID=32348343 <https://koji.fedoraproject.org/koji/taskinfo?taskID=32348343> - Fedora 30 (rawhide) The new packages and versions are: * 389-ds-base-1.4.1.1-1 Source tarballs are available for download at Download 389-ds-base Source <https://releases.pagure.org/389-ds-base/389-ds-base-1.4.1.1.tar.bz2> Highlights in 1.4.1.1 * Version change Installation and Upgrade See Download <https://www.port389.org/docs/389ds/download.html> for information about setting up your yum repositories. To install, use *dnf install 389-ds-base cockpit-389-ds* After install completes, run *dscreate interactive* There are no upgrade steps besides installing the new rpms See Install_Guide <https://www.port389.org/docs/389ds/howto/howto-install-389.html> for more information about the initial installation and setup See Source <https://www.port389.org/docs/389ds/development/source.html> for information about source tarballs and SCM (git) access. Feedback We are very interested in your feedback! Please provide feedback and comments to the 389-users mailing list: https://lists.fedoraproject.org/admin/lists/389-users.lists.fedoraproject.o… If you find a bug, or would like to see a new feature, file it in our Pagure project: https://pagure.io/389-ds-base * Bump version to 1.4.1.1 * Ticket 50151 - lib389 support cli add/replace/delete on objects * Ticket 50041 - CLI and WebUI - Add memberOf plugin functionality * Rebased from 389-ds-base-1.4.0.20-1

1 0

Import an ldif
by John.Berger＠us.fujitsu.com 30 Jan '19

30 Jan '19

We are trying to import an ldif file from our old Sun One Directory Server 5.2. We have the 389 server set up and running. I can initialize the database I want to import in and it seems to work fine. However, we have a lot of users that do not get imported in due a syntax error on certain attributes because they are blank. Example: We have an attribute called Title which was never required so many of the users have it blank. These error on import. Is there a way to get the 389 server to disregard that and load the user anyway? Basically we want to pull everything in even if the fields are blank. Regards, John

2 1

Re: Replication problems
by Mark Reynolds 29 Jan '19

29 Jan '19

On 1/28/19 8:13 PM, Mitch Patenaude wrote: > > On 1/28/19, 9:20 AM, "Mark Reynolds" <mreynolds(a)redhat.com> wrote: > [...] > If that is not useful then turning on replication logging would be the > next step. > > Trying to track the CSN only yielded that the same CSN was tried *many* times without success. > > I can't seem to figure how to turn on the replication logging. ldapmodify -D "cn=directory manager" -W dn: cn=config changetype: modify replace: nsslapd-errorlog-loglevel nsslapd-errorlog-loglevel: 8192 Then reset it to zero to disable replication logging. Hopefully something will be in there to explain the error 53. Regards, Mark > > Thanks, > -- Mitch > > >

2 3

Replication problems
by Mitch Patenaude 28 Jan '19

28 Jan '19

I’ve got a somewhat complex replication arrangement. There are 6 masters total. 09-11-13 |\/ | \/| |/\ | /\| 10-12-14 So 11 and 12 replicate to all other servers, 09 and 10 replicate to each other and 11 and 12, and 13 & 14 replication between themselves and 11 and 12. I'm having a problem where 14 (also known as intdns2-02-lv) isn't getting updates from 11 and 12, and I'm seeing this in the logs: [28/Jan/2019:08:48:57 -0800] NSMMReplicationPlugin - agmt="cn=intdns2-02-lv" (intdns2-02-lv:636): Consumer failed to replay change (uniqueid bd0d6e01-b1f411e7-81a1b88c-5005cb3e, CSN 5c4c61280000000d0000): Server is unwilling to perform (53). Will retry later. They're all Centos 6.x boxes, running 1.2.11.15-34.el6_5(9 through 12) or 1.2.11.15-97.el6_10 (13 and 14). Any idea where to look? Thanks, --- Mitch Patenaude mpatenaude(a)shutterfly.com

2 1

Problem with ldapsearch and scope one in 1.4.0.20
by Mihai Carabas 28 Jan '19

28 Jan '19

Hello, Recently I've upgraded 389ds to 389ds-1.4.0.20 on a fc29. It seems that the bug https://pagure.io/389-ds-base/issue/49617 and also https://pagure.io/389-ds-base/issue/49443 [root@ldap ~]# rpm -qa | grep 389 389-ds-console-doc-1.2.16-5.fc29.noarch 389-admin-1.1.46-2.fc29.x86_64 389-ds-1.2.2-14.fc29.noarch 389-console-1.1.19-1.fc29.noarch python3-lib389-1.4.0.20-1.fc29.noarch 389-ds-base-legacy-tools-1.4.0.20-1.fc29.x86_64 389-admin-console-doc-1.1.12-5.fc29.noarch 389-admin-console-1.1.12-5.fc29.noarch 389-ds-base-1.4.0.20-1.fc29.x86_64 389-adminutil-1.1.23-11.fc29.x86_64 389-ds-base-libs-1.4.0.20-1.fc29.x86_64 389-dsgw-1.1.11-19.fc29.x86_64 389-ds-console-1.2.16-5.fc29.noarch [root@ldap ~]# [root@ldap ~]# cat /etc/redhat-release Fedora release 29 (Twenty Nine) If I do a search with a filter and scope one, all the entries in that base are returned: [root@ldap ~]# ldapsearch ... -s one -b "ou=DPPD,ou=People,dc=curs,dc=pub,dc=ro" ou=Profesori dn # Profesori, DPPD, People, curs.pub.ro dn: ou=Profesori,ou=DPPD,ou=People,dc=curs,dc=pub,dc=ro # Asistenti-Man, DPPD, People, curs.pub.ro dn: ou=Asistenti-Man,ou=DPPD,ou=People,dc=curs,dc=pub,dc=ro # Profesori-Man, DPPD, People, curs.pub.ro dn: ou=Profesori-Man,ou=DPPD,ou=People,dc=curs,dc=pub,dc=ro # Externi, DPPD, People, curs.pub.ro dn: ou=Externi,ou=DPPD,ou=People,dc=curs,dc=pub,dc=ro # Auxiliari, DPPD, People, curs.pub.ro dn: ou=Auxiliari,ou=DPPD,ou=People,dc=curs,dc=pub,dc=ro # search result search: 2 result: 0 Success # numResponses: 6 # numEntries: 5 If I replace one with sub, all is correct. Can you advise me in this issue? Thank you, Mihai

4 29

Entry has unknown object class "ldapPublicKey", WARNING: passwordPolicy modify error 65 on entry
by Jason Jenkins 16 Jan '19

16 Jan '19

Hi, One of my consumers is showing the following error: Entry "uid=XXXX,ou=People,dc=XXX" has unknown object class "ldapPublicKey" WARNING: passwordPolicy modify error 65 on entry uid=XXXX,ou=People,dc=XXX This error is coming up for anyone that tries to authenticate against this consumer. It is slowing down authentication. Nothing has change on the directory server side that I can tell and my masters aren’t having these issues. Any ideas?

2 2

Re: Problem with userRoot cache
by Mark Reynolds 16 Jan '19

16 Jan '19

Hey Paul, On 1/16/19 10:14 AM, Paul Whitney wrote: > > We were on version: 389-ds-base-1.3.7.5-24. > What OS? > > The nsslapd-cache-autosize was set to 0. We apply our own values. > > > To keep us afloat we have been forced to enable > nsslapd-cache-autosize. However, our performance has degraded in > response times and feel we are not able to better allocate/customize > the cache settings as they relate to each database. > > > System: Virtual Machine > > 8-CPU > > 64GB RAM (of which 35G is free) > > > Two databases in the slapd instance: > > userRoot = 21G > > groupRoot = 1.8G > > > When we try to allocate anything above 50% for nsslapd-cache-autosize, > the service fails to start stating values cannot exceed 100. > > > When we disable nsslapd-cache-autosize, and punch in our numbers: > > > nsslapd-cache-autosize = 0 > > nsslapd-dbcachesize = 1073741824 > > nsslapd-cachememsize = 2147483648 (groupRoot) and 23622320128 (userRoot) > > > Service overwrites our settings and sets both databases to 2147483648. > While that is ok for groupRoot, it is not for userRoot. > > > Based on this information, is there a way/recommendation to: > > 1. To force these values we enter to "stick" > Well setting autosize to zero and explicitly setting the cache attributes is all it should take for it to stick > 1. How can I better configure the auto cache sizing of these entries? > Start here: http://www.port389.org/docs/389ds/design/autotuning.html (checkout the manual tuning section) You can tune the autosizing to use more cache, but it is uniform across all backends: groupRoot and userRoot would use the same values. > > I would offer logs if I could, but we cannot get them off the system. > It is hosted in a disconnected environment. > The logs would say why the server thinks it needs to resize your caches (a bug?), but it sounds like autosizing is not the issue here since it is set to zero. I'm not sure what else I can offer up without more log information. I suspect the server is not properly detecting the 64gigs of memory, and thinks you have much less, which is why it's downsizing the cache values. This is all speculation without being able to look at the errors log (during startup). I find it very odd you can not get access to your own logs, it's such a vital part of the server, you should really get that addressed or else we can't really help you :( Regards, Mark > > Paul M. Whitney, RHCSA, CISSP > Chesapeake IT Consulting, Inc. > 2680 Tobacco Rd > Chesapeake Beach, MD 20732 > > Work: 443-492-2872 > Cell: 410.493.9448 > Email: paul.whitney(a)chesapeake-it.com > <mailto: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:* William Brown <wbrown(a)suse.de> > *Sent:* Tuesday, January 15, 2019 7:22:18 PM > *To:* 389-users(a)lists.fedoraproject.org > *Cc:* Paul Whitney > *Subject:* Re: [389-users] Problem with userRoot cache > > > > On 16 Jan 2019, at 06:49, Mark Reynolds <mreynolds(a)redhat.com> wrote: > > > > What version were you previously on? > > > > Sounds like an issue with autocache sizing. The errors log might > give more info about why its being reset. > > > > Also check if "nsslapd-cache-autosize" is set under > "cn=config,cn=ldbm database,cn=plugins,cn=config". If it is, set it > to zero to stop the autosizing. > > Certainly is sounds like autosizing is still enabled here and is just > resetting your values on you. > > > > > > > On 1/15/19 3:42 PM, Paul Whitney wrote: > >> We recently updated to 389-ds-base-1.3.8.4-18. I am not sure I can > attribute this issue to this update since we are now just discovering > it. But setting the nsslapd-cachememsize is reverting to a default > value of 2GB. I have attempted to restore the value through the > console and restarting the instance. I have also tried by stopping > instance and manually editing the dse.ldif file. In both cases, the > value is replaced with 2GB value. > >> > >> Any suggestions? > >> > >> Paul M. Whitney > >> RHCSA, VCP, CISSP, Security+ > >> Chesapeake IT Consulting, Inc. > >> 2680 Tobacco Rd > >> Chesapeake Beach, MD 20732 > >> > >> Work: 443-492-2872 > >> Cell: 410.493.9448 > >> Email: paul.whitney(a)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(a)lists.fedoraproject.org > >> > >> To unsubscribe send an email to > >> 389-users-leave(a)lists.fedoraproject.org > >> > >> Fedora Code of Conduct: > >> https://getfedora.org/code-of-conduct.html > >> > >> List Guidelines: > >> https://fedoraproject.org/wiki/Mailing_list_guidelines > >> > >> List Archives: > >> > https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject… > > _______________________________________________ > > 389-users mailing list -- 389-users(a)lists.fedoraproject.org > > To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > <https://fedoraproject.org/wiki/Mailing_list_guidelines> > > List Archives: > https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject… > > — > Sincerely, > > William Brown > Software Engineer, 389 Directory Server > SUSE Labs > > > _______________________________________________ > 389-users mailing list -- 389-users(a)lists.fedoraproject.org > To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject…

3 6

Re: Problem with userRoot cache (last one)
by Mark Reynolds 16 Jan '19

16 Jan '19

On 1/16/19 12:42 PM, Paul Whitney wrote: > > Mark, > > Thank you for figuring out the issue we are having. Question, is it > possible for us to roll back/downgrade the 389-ds to a "previously" > working version? > You'd have to go back to 389-ds-base-1.3.7, but I don't know if that's possible on CentOS 7.6, you'd probably have to go back to CentOS 7.5 as well I would think. :-( > > > Paul M. Whitney, RHCSA, CISSP > Chesapeake IT Consulting, Inc. > 2680 Tobacco Rd > Chesapeake Beach, MD 20732 > > Work: 443-492-2872 > Cell: 410.493.9448 > Email: paul.whitney(a)chesapeake-it.com > <mailto: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:* Mark Reynolds <mreynolds(a)redhat.com> > *Sent:* Wednesday, January 16, 2019 12:16:19 PM > *To:* General discussion list for the 389 Directory server project.; > Paul Whitney; William Brown > *Subject:* Re: [389-users] Re: Problem with userRoot cache (last one) > > > On 1/16/19 12:05 PM, Mark Reynolds wrote: >> >> >> On 1/16/19 12:02 PM, Mark Reynolds wrote: >>> >>> Hi Paul, >>> >>> >>> Okay I think I found the bug you are running into: >>> >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=1627512 >>> >>> >>> https://pagure.io/389-ds-base/issue/49618 >>> >>> >>> So sounds like you need to upgrade to: >>> >>> >>> 389-ds-base-1.3.8.4-21 (RHEL/Centos 7.6) >>> >>> >>> Or build the upstream 1.3.7 server yourself using the commit found >>> in the pagure ticket above. >>> >> Apologies, you are on 1.3.8, so yeah you need to get on 1.3.8.4-21 or >> higher. Might have to wait for CentOS to pick up the latest builds? > > Looks like 1.3.8.4-22 is going to be in RHEL(Centos) batch update 3. > So it's not available yet, sorry, but should be next month (not sure > how fast Centos picks up RHEL updates) > > > So in the meantime I would increase the autosize values to take > advantage of your RAM. See the wiki link I sent you earlier, and also > checkout the admin guide: > > > https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/h… > > > Good luck, > > Mark > > >>> Regards, >>> >>> Mark >>> >>> >>> On 1/16/19 11:38 AM, Mark Reynolds wrote: >>>> >>>> Hey Paul, >>>> >>>> >>>> On 1/16/19 10:14 AM, Paul Whitney wrote: >>>>> >>>>> We were on version: 389-ds-base-1.3.7.5-24. >>>>> >>>> What OS? >>>> >>>> >>>> >>>>> >>>>> The nsslapd-cache-autosize was set to 0. We apply our own values. >>>>> >>>>> >>>>> To keep us afloat we have been forced to enable >>>>> nsslapd-cache-autosize. However, our performance has degraded in >>>>> response times and feel we are not able to better >>>>> allocate/customize the cache settings as they relate to each database. >>>>> >>>>> >>>>> System: Virtual Machine >>>>> >>>>> 8-CPU >>>>> >>>>> 64GB RAM (of which 35G is free) >>>>> >>>>> >>>>> Two databases in the slapd instance: >>>>> >>>>> userRoot = 21G >>>>> >>>>> groupRoot = 1.8G >>>>> >>>>> >>>>> When we try to allocate anything above 50% for >>>>> nsslapd-cache-autosize, the service fails to start stating values >>>>> cannot exceed 100. >>>>> >>>>> >>>>> When we disable nsslapd-cache-autosize, and punch in our numbers: >>>>> >>>>> >>>>> nsslapd-cache-autosize = 0 >>>>> >>>>> nsslapd-dbcachesize = 1073741824 >>>>> >>>>> nsslapd-cachememsize = 2147483648 (groupRoot) and 23622320128 >>>>> (userRoot) >>>>> >>>>> >>>>> Service overwrites our settings and sets both databases to >>>>> 2147483648. While that is ok for groupRoot, it is not for userRoot. >>>>> >>>>> >>>>> Based on this information, is there a way/recommendation to: >>>>> >>>>> 1. To force these values we enter to "stick" >>>>> >>>> Well setting autosize to zero and explicitly setting the cache >>>> attributes is all it should take for it to stick >>>> >>>> >>>>> 1. How can I better configure the auto cache sizing of these >>>>> entries? >>>>> >>>> Start here: >>>> http://www.port389.org/docs/389ds/design/autotuning.html >>>> (checkout the manual tuning section) >>>> >>>> >>>> You can tune the autosizing to use more cache, but it is uniform >>>> across all backends: groupRoot and userRoot would use the same values. >>>> >>>> >>>> >>>>> >>>>> I would offer logs if I could, but we cannot get them off the >>>>> system. It is hosted in a disconnected environment. >>>>> >>>> The logs would say why the server thinks it needs to resize your >>>> caches (a bug?), but it sounds like autosizing is not the issue >>>> here since it is set to zero. I'm not sure what else I can offer >>>> up without more log information. I suspect the server is not >>>> properly detecting the 64gigs of memory, and thinks you have much >>>> less, which is why it's downsizing the cache values. This is all >>>> speculation without being able to look at the errors log (during >>>> startup). I find it very odd you can not get access to your own >>>> logs, it's such a vital part of the server, you should really get >>>> that addressed or else we can't really help you :( >>>> >>>> >>>> Regards, >>>> >>>> Mark >>>> >>>>> >>>>> Paul M. Whitney, RHCSA, CISSP >>>>> Chesapeake IT Consulting, Inc. >>>>> 2680 Tobacco Rd >>>>> Chesapeake Beach, MD 20732 >>>>> >>>>> Work: 443-492-2872 >>>>> Cell: 410.493.9448 >>>>> Email: paul.whitney(a)chesapeake-it.com >>>>> <mailto: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:* William Brown <wbrown(a)suse.de> <mailto:wbrown@suse.de> >>>>> *Sent:* Tuesday, January 15, 2019 7:22:18 PM >>>>> *To:* 389-users(a)lists.fedoraproject.org >>>>> <mailto:389-users@lists.fedoraproject.org> >>>>> *Cc:* Paul Whitney >>>>> *Subject:* Re: [389-users] Problem with userRoot cache >>>>> >>>>> >>>>> > On 16 Jan 2019, at 06:49, Mark Reynolds <mreynolds(a)redhat.com> >>>>> <mailto:mreynolds@redhat.com> wrote: >>>>> > >>>>> > What version were you previously on? >>>>> > >>>>> > Sounds like an issue with autocache sizing. The errors log >>>>> might give more info about why its being reset. >>>>> > >>>>> > Also check if "nsslapd-cache-autosize" is set under >>>>> "cn=config,cn=ldbm database,cn=plugins,cn=config". If it is, set >>>>> it to zero to stop the autosizing. >>>>> >>>>> Certainly is sounds like autosizing is still enabled here and is >>>>> just resetting your values on you. >>>>> >>>>> > >>>>> > >>>>> > On 1/15/19 3:42 PM, Paul Whitney wrote: >>>>> >> We recently updated to 389-ds-base-1.3.8.4-18. I am not sure I >>>>> can attribute this issue to this update since we are now just >>>>> discovering it. But setting the nsslapd-cachememsize is reverting >>>>> to a default value of 2GB. I have attempted to restore the value >>>>> through the console and restarting the instance. I have also tried >>>>> by stopping instance and manually editing the dse.ldif file. In >>>>> both cases, the value is replaced with 2GB value. >>>>> >> >>>>> >> Any suggestions? >>>>> >> >>>>> >> Paul M. Whitney >>>>> >> RHCSA, VCP, CISSP, Security+ >>>>> >> Chesapeake IT Consulting, Inc. >>>>> >> 2680 Tobacco Rd >>>>> >> Chesapeake Beach, MD 20732 >>>>> >> >>>>> >> Work: 443-492-2872 >>>>> >> Cell: 410.493.9448 >>>>> >> Email: paul.whitney(a)chesapeake-it.com >>>>> <mailto: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(a)lists.fedoraproject.org >>>>> <mailto:389-users@lists.fedoraproject.org> >>>>> >> >>>>> >> To unsubscribe send an email to >>>>> >> 389-users-leave(a)lists.fedoraproject.org >>>>> <mailto:389-users-leave@lists.fedoraproject.org> >>>>> >> >>>>> >> Fedora Code of Conduct: >>>>> >> https://getfedora.org/code-of-conduct.html >>>>> >> >>>>> >> List Guidelines: >>>>> >> https://fedoraproject.org/wiki/Mailing_list_guidelines >>>>> >> >>>>> >> List Archives: >>>>> >> >>>>> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject… >>>>> > _______________________________________________ >>>>> > 389-users mailing list -- 389-users(a)lists.fedoraproject.org >>>>> <mailto:389-users@lists.fedoraproject.org> >>>>> > To unsubscribe send an email to >>>>> 389-users-leave(a)lists.fedoraproject.org >>>>> <mailto:389-users-leave@lists.fedoraproject.org> >>>>> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >>>>> > List Guidelines: >>>>> https://fedoraproject.org/wiki/Mailing_list_guidelines >>>>> > List Archives: >>>>> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject… >>>>> >>>>> — >>>>> Sincerely, >>>>> >>>>> William Brown >>>>> Software Engineer, 389 Directory Server >>>>> SUSE Labs >>>>> >>>>> >>>>> _______________________________________________ >>>>> 389-users mailing list --389-users(a)lists.fedoraproject.org <mailto:389-users@lists.fedoraproject.org> >>>>> To unsubscribe send an email to389-users-leave(a)lists.fedoraproject.org <mailto:389-users-leave@lists.fedoraproject.org> >>>>> Fedora Code of Conduct:https://getfedora.org/code-of-conduct.html >>>>> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines >>>>> List Archives:https://lists.fedoraproject.org/archives/list/389-users@lists.fedo… >>>> >>>> _______________________________________________ >>>> 389-users mailing list --389-users(a)lists.fedoraproject.org <mailto:389-users@lists.fedoraproject.org> >>>> To unsubscribe send an email to389-users-leave(a)lists.fedoraproject.org <mailto:389-users-leave@lists.fedoraproject.org> >>>> Fedora Code of Conduct:https://getfedora.org/code-of-conduct.html >>>> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines >>>> List Archives:https://lists.fedoraproject.org/archives/list/389-users@lists.fedo… >>> >>> _______________________________________________ >>> 389-users mailing list --389-users(a)lists.fedoraproject.org <mailto:389-users@lists.fedoraproject.org> >>> To unsubscribe send an email to389-users-leave(a)lists.fedoraproject.org <mailto:389-users-leave@lists.fedoraproject.org> >>> Fedora Code of Conduct:https://getfedora.org/code-of-conduct.html >>> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines >>> List Archives:https://lists.fedoraproject.org/archives/list/389-users@lists.fedo… >> >> _______________________________________________ >> 389-users mailing list --389-users(a)lists.fedoraproject.org <mailto:389-users@lists.fedoraproject.org> >> To unsubscribe send an email to389-users-leave(a)lists.fedoraproject.org <mailto:389-users-leave@lists.fedoraproject.org> >> Fedora Code of Conduct:https://getfedora.org/code-of-conduct.html >> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives:https://lists.fedoraproject.org/archives/list/389-users@lists.fedo… > > _______________________________________________ > 389-users mailing list -- 389-users(a)lists.fedoraproject.org > To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject…

2 1

Re: Problem with userRoot cache
by Mark Reynolds 16 Jan '19

16 Jan '19

What version were you previously on? Sounds like an issue with autocache sizing. The errors log might give more info about why its being reset. Also check if "nsslapd-cache-autosize" is set under "cn=config,cn=ldbm database,cn=plugins,cn=config". If it is, set it to zero to stop the autosizing. On 1/15/19 3:42 PM, Paul Whitney wrote: > > We recently updated to 389-ds-base-1.3.8.4-18. I am not sure I can > attribute this issue to this update since we are now just discovering > it. But setting the nsslapd-cachememsize is reverting to a default > value of 2GB. I have attempted to restore the value through the > console and restarting the instance. I have also tried by stopping > instance and manually editing the dse.ldif file. In both cases, the > value is replaced with 2GB value. > > > Any suggestions? > > > Paul M. Whitney > RHCSA, VCP, CISSP, Security+ > Chesapeake IT Consulting, Inc. > 2680 Tobacco Rd > Chesapeake Beach, MD 20732 > > Work: 443-492-2872 > Cell: 410.493.9448 > Email: paul.whitney(a)chesapeake-it.com > <mailto: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(a)lists.fedoraproject.org > To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject…

3 2

Problem with userRoot cache
by Paul Whitney 15 Jan '19

15 Jan '19

We recently updated to 389-ds-base-1.3.8.4-18. I am not sure I can attribute this issue to this update since we are now just discovering it. But setting the nsslapd-cachememsize is reverting to a default value of 2GB. I have attempted to restore the value through the console and restarting the instance. I have also tried by stopping instance and manually editing the dse.ldif file. In both cases, the value is replaced with 2GB value. Any suggestions? Paul M. Whitney RHCSA, VCP, CISSP, Security+ Chesapeake IT Consulting, Inc. 2680 Tobacco Rd Chesapeake Beach, MD 20732 Work: 443-492-2872 Cell: 410.493.9448 Email: paul.whitney(a)chesapeake-it.com<mailto: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.

1 0

how to merge content and ldap structore
by Ghiurea, Isabella 13 Jan '19

13 Jan '19

Hi List, I have a request to upload/import only schema ( attributes, no data) and than upload data (only) from another DS in a new DS ( basic : merge two ldap ds into a third DS new one ) , I am not aware db2ldif can export db without data and next schema structure as separate option ? thank you

2 1

Re: Allow filters through PTA Plugin
by Olivier JUDITH 07 Jan '19

07 Jan '19

Hi William, I will be glad to help, it will just take some time to write as required for your wiki page. Will be done soon Rgds

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users January 2019