389-users July 2019

389-users@lists.fedoraproject.org

12 participants
25 discussions

Announcing 389 Directory Server 1.4.0.25
by Mark Reynolds 08 Jul '19

08 Jul '19

389 Directory Server 1.4.0.25 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.0.25 Fedora packages are available on Fedora 29 Fedora 29 https://koji.fedoraproject.org/koji/taskinfo?taskID=36138415 <https://koji.fedoraproject.org/koji/taskinfo?taskID=36138415> Bodhi F29 https://bodhi.fedoraproject.org/updates/FEDORA-2019-1bfca53248 <https://bodhi.fedoraproject.org/updates/FEDORA-2019-1bfca53248> The new packages and versions are: * 389-ds-base-1.4.0.25-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.25.tar.bz2> Highlights in 1.4.0.25 Bug fix 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*. To install the 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. New UI Progress (Cockpit plugin) The new UI is broken up into a series of configuration tabs. Here is a table showing the current progress Configuration Tab Finished Written in ReachJS Server Tab Yes No Security Tab No (coming soon) No Database Tab Yes Yes Replication Tab Yes No Schema Tab Yes No Plugin Tab Yes Yes Monitor Tab Yes Yes 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.25 * Issue 50431 - Fix regression from coverity fix (memberOf plugin crash) -- 389 Directory Server Development Team

1 0

Latest Version of 389-ds-base for CentOS 7
by Paul Whitney 08 Jul '19

08 Jul '19

I was looking up the latest version of 389-ds and noticed that an update has not been released since March 2019. Has there not been anymore updates to this bundle? 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.

1 0

Admin server and Slapd server will not start
by John.Berger＠us.fujitsu.com 08 Jul '19

08 Jul '19

FYI, Our server team patch my Test 389 ldap server the other night and now both my Admin Server and Slapd server will not start up. Below is the errors we are getting. Admin Server [root@rtxldslt01 slapd-rtxldslt01-4]# systemctl status dirsrv@admin-serv -l ● dirsrv(a)admin-serv.service<mailto:dirsrv@admin-serv.service> - 389 Directory Server admin-serv. Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service<mailto:/usr/lib/systemd/system/dirsrv@.service>; enabled; vendor preset: disabled) Active: failed (Result: resources) Jul 08 11:34:32 rtxldslt01.fnc.net.local systemd[1]: Failed to load environment files: No such file or directory Jul 08 11:34:32 rtxldslt01.fnc.net.local systemd[1]: dirsrv(a)admin-serv.service<mailto:dirsrv@admin-serv.service> failed to run 'start-pre' task: No such file or directory Jul 08 11:34:32 rtxldslt01.fnc.net.local systemd[1]: Failed to start 389 Directory Server admin-serv.. Jul 08 11:34:32 rtxldslt01.fnc.net.local systemd[1]: Unit dirsrv(a)admin-serv.service<mailto:dirsrv@admin-serv.service> entered failed state. Jul 08 11:34:32 rtxldslt01.fnc.net.local systemd[1]: dirsrv(a)admin-serv.service<mailto:dirsrv@admin-serv.service> failed. Slapd Server [root@rtxldslt01 slapd-rtxldslt01-4]# systemctl status dirsrv@slapd-rtxldslt01-4 -l ● dirsrv(a)slapd-rtxldslt01-4.service<mailto:dirsrv@slapd-rtxldslt01-4.service> - 389 Directory Server slapd-rtxldslt01-4. Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service<mailto:/usr/lib/systemd/system/dirsrv@.service>; enabled; vendor preset: disabled) Active: failed (Result: resources) Jul 08 11:33:05 rtxldslt01.fnc.net.local systemd[1]: Failed to load environment files: No such file or directory Jul 08 11:33:05 rtxldslt01.fnc.net.local systemd[1]: dirsrv(a)slapd-rtxldslt01-4.service<mailto:dirsrv@slapd-rtxldslt01-4.service> failed to run 'start-pre' task: No such file or directory Jul 08 11:33:05 rtxldslt01.fnc.net.local systemd[1]: Failed to start 389 Directory Server slapd-rtxldslt01-4.. Jul 08 11:33:05 rtxldslt01.fnc.net.local systemd[1]: Unit dirsrv(a)slapd-rtxldslt01-4.service<mailto:dirsrv@slapd-rtxldslt01-4.service> entered failed state. Jul 08 11:33:05 rtxldslt01.fnc.net.local systemd[1]: dirsrv(a)slapd-rtxldslt01-4.service<mailto:dirsrv@slapd-rtxldslt01-4.service> failed. Unfortunately I am not a Linux persons and I do not have the access to do thing on the server myself so I have to work between you guys and our server guys. Hope someone can help. Thanks, John

2 1

LDAPCon 2019 CFP
by William Brown 03 Jul '19

03 Jul '19

Hi all, The LDAPCon 2019 CFP is now open - if you are in the EU and able to attend this event, it would be amazing to see some 389 user presentations, and to be able to hear about how you use this software in your environments. It's also a great chance to meet many people in the community and to discuss future ideas and progress. For those of us who are far away (not the EU), I'm hoping the sessions are recorded and shared online. Good luck with your submissions! https://cfp.ldapcon.org/ldapcon2019/cfp — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs

1 0

Windows Sync Agreement not copying all objects
by Abhisheyk Deb 02 Jul '19

02 Jul '19

Hi, We have the following setup. Active Directory Server in US. 389 DS Server in Italy. We are able to access the Active Directory Server from 389 DS. We installed the sync agreement. No body is touching the AD, the number of objects that should copied is 21. But every time we are running the replication agreement, the number of objects being copied is always different. How can that be if there is no change happening at the AD Server. Is the replication done over UDP or TCP. Also is it because of distance and delay that is causing the synchronization issues. If some can elaborate in this issue, it would be really helpful. Thank you Abhishek Deb

3 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users July 2019