389-users August 2017

389-users@lists.fedoraproject.org

9 participants
16 discussions

Announcing Directory Server 1.3.7.2-1
by Mark Reynolds 22 Aug '17

22 Aug '17

*389 Directory Server **1.3.7.2* The 389 Directory Server team is proud to announce 389-ds-base version 1.3.7.2 Fedora packages are available on Fedora 27 and 28(Rawhide). https://koji.fedoraproject.org/koji/taskinfo?taskID=21401020 - Fedora 28 https://koji.fedoraproject.org/koji/taskinfo?taskID=21401182 - Fedora 27 The new packages and versions are: * 389-ds-base-1.3.7.2-1 Source tarballs are available for download at Download 389-ds-base Source <http://www.port389.org/binaries/389-ds-base-1.3.7.2.tar.bz2> Highlights in 1.3.7.2 * Security fix, bug fixes, and enhancements Installation and Upgrade See Download <http://www.port389.org/docs/389ds/download.html> for information about setting up your yum repositories. To install, use *yum install 389-ds* yum install 389-ds After install completes, run *setup-ds-admin.pl* if you have 389-admin installed, otherwise please run *setup-ds.pl* to set up your directory server. To upgrade, use *yum upgrade* yum upgrade After upgrade completes, run *setup-ds-admin.pl -u* if you have 389-admin installed, otherwise please run *setup-ds.pl* to update your directory server/admin server/console information. See Install_Guide <http://www.port389.org/docs/389ds/legacy/install-guide.html> for more information about the initial installation, setup, and upgrade See Source <http://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.3.7.2 * Ticket 49038 - Fix regression from legacy code cleanup * Ticket 49295 - Fix CI tests * Ticket 48067 - Add bugzilla tests for ds_logs * Ticket 49356 - mapping tree crash can occur during tot init * Ticket 49275 - fix compiler warns for gcc 7 * Ticket 49248 - Add a docstring to account locking test case * Ticket 49445 - remove dead code * Ticket 48081 - Add regression tests for pwpolicy * Ticket 48056 - Add docstrings to basic test suite * Ticket 49349 - global name ‘imap’ is not defined * Ticket 83 - lib389 - Fix tests and create_test.py * Ticket 48185 - Remove referint-logchanges attr from referint’s config * Ticket 48081 - Add regression tests for pwpolicy * Ticket 83 - lib389 - Replace topology agmt objects * Ticket 49331 - change autoscaling defaults * Ticket 49330 - Improve ndn cache performance. * Ticket 49347 - reproducable build numbers * Ticket 39344 - changelog ldif import fails * Ticket 49337 - Add regression tests for import tests * Ticket 49309 - syntax checking on referint’s delay attr * Ticket 49336 - SECURITY: Locked account provides different return code * Ticket 49332 - Event queue is not working * Ticket 49313 - Change the retrochangelog default cache size * Ticket 49329 - Descriptive error msg for USN cleanup task * Ticket 49328 - Cleanup source code * Ticket 49299 - Add normalized dn cache stats to dbmon.sh * Ticket 49290 - improve idl handling in complex searches * Ticket 49328 - Update clang-format config file * Ticket 49091 - remove usage of changelog semaphore * Ticket 49275 - shadow warnings for gcc7 - pass 1 * Ticket 49316 - fix missing not condition in clock cleanu * Ticket 49038 - Remove legacy replication * Ticket 49287 - v3 extend csnpl handling to multiple backends * Ticket 49310 - remove sds logging in debug builds * Ticket 49031 - Improve memberof with a cache of group parents * Ticket 49316 - Fix clock unsafety in DS * Ticket 48210 - Add IP addr and connid to monitor output * Ticket 49295 - Fix CI tests and compiler warnings * Ticket 49295 - Fix CI tests * Ticket 49305 - Improve atomic behaviours in 389-ds * Ticket 49298 - fix missing header * Ticket 49314 - Add untracked files to the .gitignore * Ticket 49303 - Fix error in CI test * Ticket 49302 - fix dirsrv importst due to lib389 change * Ticket 49303 - Add option to disable TLS client-initiated renegotiation * Ticket 49298 - force sync() on shutdown * Ticket 49306 - make -f rpm.mk rpms produces build without tcmalloc enabled * Ticket 49297 - improve search perf in bpt by removing a deref * Ticket 49284 - resolve crash in memberof when deleting attrs * Ticket 49290 - unindexed range searches don’t provide notes=U * Ticket 49301 - Add one logpipe test case

1 0

Problem adding users to group.
by Lucas Diedrich 20 Aug '17

20 Aug '17

Hello guys, i have a *Freeipa 4.4.1* with 389 (389-ds-base-1.3.5.18-1.fc25.x86_64), my problem is, i have a huge group with 5400 users, but i've to add more 800 to it, when i try to add more than 10 my dirsrv goes unresponsive. When the system starts to replicate all my Freeipa's goes unresponsive, asking over #389 some guys susgest that could be a bug with the *memberof plugin*, is there anything i can do to fix this? Thanks.

3 11

CentOS-Directory/8.1.0 B2009.134.1334 ldapsearch problem
by Kirk MacDonald 18 Aug '17

18 Aug '17

Hello, I'm working on migrating from CentOS-Directory/8.1.0 B2009.134.1334 to 389-Directory/1.3.5.10 B2017.145.2037. What I'm finding is that the Database Export functions in the CentOS-Directory/8.1.0 B2009.134.1334 Console as well as ldapsearches aren't returning all entries. Specifically an objectclass=* search filter for a given ou fails to output all entries. However if the search filter is for an attribute which exists, all applicable entries are returned. The Console also does not show entries that might otherwise be found with a ldapsearch and a specific search filter. Based on some experience I have with another LDAP system this feels like an ancestorid problem. Can anyone offer any tips/thoughts or questions to clarify my problem? Thank you Kirk MacDonald

2 1

Announcing 389 Directory Server version 1.3.5.19
by Mark Reynolds 14 Aug '17

14 Aug '17

389 Directory Server 1.3.5.19 The 389 Directory Server team is proud to announce 389-ds-base version 1.3.5.19. Fedora packages are available from the Fedora 25. The new packages and versions are: * 389-ds-base-1.3.5.19-1 Source tarballs are available for download at Download 389-ds-base Source <http://www.port389.org/binaries/389-ds-base-1.3.5.19.tar.bz2> and Download nunc-stans Source <http://www.port389.org/binaries/nunc-stans-0.1.8.tar.bz2>. Highlights in 1.3.5.19 * Bugand security fixes Installation and Upgrade See Download <http://www.port389.org/docs/389ds/download.html> for information about setting up your yum repositories. To install, use *yum install 389-ds* yum install 389-ds After install completes, run *setup-ds-admin.pl* if you have an Admin Server installed (389-admin), otherwise just run *setup-ds.pl* to set up your directory server. To upgrade, use *yum upgrade* yum upgrade After upgrade completes, run *setup-ds-admin.pl -u* if you have an Admin Server installed (389-admin), otherwise just run *setup-ds.pl -u* to update your directory server/admin server/console information. See Install_Guide <http://www.port389.org/docs/389ds/legacy/install-guide.html> for more information about the initial installation, setup, and upgrade See Source <http://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… as well as: F25 https://bodhi.fedoraproject.org/updates/FEDORA-2017-4333359de8 <https://bodhi.fedoraproject.org/updates/FEDORA-2017-4333359de8> If you find a bug, or would like to see a new feature, file it in our Trac instance: https://pagure.io/389-ds-base/new_issue * Bump verison to 1.3.5.19 * Ticket 49336 - SECURITY 1.3.5.x: Locked account provides different return code * Ticket 49330 - Improve ndn cache performance 1.3.5

1 0

Announcing 389 Directory Server version 1.3.6.7
by Mark Reynolds 14 Aug '17

14 Aug '17

389 Directory Server 1.3.6.7 The 389 Directory Server team is proud to announce 389-ds-base version 1.3.6.7 Fedora packages are available from the Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-431f07f52a The new packages and versions are: * 389-ds-base-1.3.6.7-1 Fedora 26 Source tarballs are available for download at Download 389-ds-base Source <http://www.port389.org/binaries/389-ds-base-1.3.6.7.tar.bz2> Highlights in 1.3.6.7 * Security fix, bug fixes, and enhancements Installation and Upgrade See Download <http://www.port389.org/docs/389ds/download.html> for information about setting up your yum repositories. To install, use *yum install 389-ds* yum install 389-ds After install completes, run *setup-ds-admin.pl* if you have 389-admin installed, otherwise please run *setup-ds.pl* to set up your directory server. To upgrade, use *yum upgrade* yum upgrade After upgrade completes, run *setup-ds-admin.pl -u* if you have 389-admin installed, otherwise please run *setup-ds.pl* to update your directory server/admin server/console information. See Install_Guide <http://www.port389.org/docs/389ds/legacy/install-guide.html> for more information about the initial installation, setup, and upgrade See Source <http://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.3.6.7-1 * Ticket 49330 - Improve ndn cache performance * Ticket 49298 - fix missing header * Ticket 49298 - force sync() on shutdown * Ticket 49336 - SECURITY: Locked account provides different return code * Ticket 49334 - fix backup restore if changelog exists * Ticket 49313 - Change the retrochangelog default cache size * Fix error log format in add.c * Ticket 49287 - fix compiler warning for patch 49287 * Ticket 49287 - v3 extend csnpl handling to multiple backends * Ticket 49288 - RootDN Access wrong plugin path in template-dse.ldif.in * Ticket 49291 - slapi_search_internal_callback_pb may SIGSEV if related pblock has not operation set * Ticket 49008 - Fix MO plugin betxn test * Ticket 49227 - ldapsearch does not return the expected Error log level * Ticket 49028 - Add autotuning test suite * Ticket 49273 - bak2db doesn’t operate with dbversion * Ticket 49184 - adjust logging level in MO plugin * Ticket 49257 - only register modify callbacks * Ticket 49257 - Update CI script * Ticket 49008 - Adjust CI test for new memberOf behavior * Ticket 49273 - crash when DBVERSION is corrupt. * Ticket 49268 - master branch fails on big endian systems * Ticket 49241 - add symblic link location to db2bak.pl output * Ticket 49257 - Reject nsslapd-cachememsize & nsslapd-cachesize when nsslapd-cache-autosize is set * Ticket 48538 - Failed to delete old semaphore * Ticket 49231 - force EXTERNAL always * Ticket 49267 - autosize split of 0 results in dbcache of 0

1 0

No NetscapeRoot under Replication
by Alberto Viana 10 Aug '17

10 Aug '17

Hi, I'm testing version 1.3.7.1: ~# ns-slapd -v 389 Project 389-Directory/1.3.7.1.20170714gitecd2588 B2017.195.1935 And using 389 console there is no NetscapeRoot option under Replication (ony userRoot), is it an expected behavior? Thanks

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users August 2017