Sorry no idea why this is happening based on the information you told
me. I've never heard of this happening with a completely fresh
install. Are you sure there is no pre-existing directory server you are
installing on top of? If you look under /etc/dirsrv/ are there any
"slapd-INSTANCE" directories?
So remove the old instance using remove-ds-admin.pl. Then try running
it with the debugger enabled:
# setup-ds-admin.pl -ddddd
If it still fails, then please provide the access log
(/var/log/dirsrv/slapd-INSTANCE/access), and the debug output from
setup-ds-admin.pl
Mark
On 5/1/20 8:44 AM, Crocker, Deborah wrote:
I'm using the option 2 install [typical] interactive and take the defaults. The
only thing I end up typing in is passwords.
Deborah Crocker, PhD
Systems Engineer III
Office of Information Technology
The University of Alabama
Box 870346
Tuscaloosa, AL 36587
Office 205-348-3758 | Fax 205-348-9393
deborah.croc...@ua.edu
-----Original Message-----
From: Mark Reynolds <mreyno...@redhat.com>
Sent: Friday, May 1, 2020 7:17 AM
To: General discussion list for the 389 Directory server project.
<389-users@lists.fedoraproject.org>; Crocker, Deborah <cr...@ua.edu>
Subject: [EXTERNAL] Re: [389-users] setup-ds-admin fails to install admin server
On 4/30/20 5:23 PM, Crocker, Deborah wrote:
Why do I get this error on a setup-ds-admin.pl This was a fresh install.
-----------------------
The suffix 'o=NetscapeRoot' already exists. Config entry DN
'cn=o\3Dnetscaperoot,cn=mapping tree,cn=config'.
And what options are you using when you install? Are you using a silent
install file or interactive mode?
Are "you" setting o=netscaperoot during the install? If so, do not do that, as
the server is already going to create this suffix.
Mark
Failed to create the configuration directory server
-----------------------
The setup has
Centos 7.8
Epel install
389-ds-base: 1.3.10.1
389-admin: 1.1.46
TIA
Deborah Crocker, PhD
Systems Engineer III
Office of Information Technology
The University of Alabama
Box 870346
Tuscaloosa, AL 36587
Office 205-348-3758 | Fax 205-348-9393 deborah.croc...@ua.edu
-----Original Message-----
From: Mark Reynolds <mreyno...@redhat.com>
Sent: Thursday, April 30, 2020 2:06 PM
To: General discussion list for the 389 Directory server project.
<389-users@lists.fedoraproject.org>; CHAMBERLAIN James
<james.chamberl...@3ds.com>
Subject: [EXTERNAL] [389-users] Re: [389-announce] Notice of Legacy Tool
removal for 389 Directory Server
On 4/30/20 2:34 PM, CHAMBERLAIN James wrote:
Hi Mark,
On Apr 29, 2020, at 5:10 PM, Mark Reynolds <mreyno...@redhat.com> wrote:
On 4/29/20 5:07 PM, Mark Reynolds wrote:
We've been talking about this for quite some time...
A majority of all the old legacy perl and shell scripts have now been ported to
the new CLI tools. Starting sometime in Fedora 33 we will stop shipping the
legacy tools sub-package as part of 389 Directory Server.
To be more specific the 389-ds-base-1.4.4 version is where the removal of the
legacy tools subpackage will occur.
Does this includes tools like db2ldif.pl?
Correct, all of those scripts will be removed. So all the shell and perl
scripts (except for logconv.pl) will no longer be available starting at some
point in 1.4.4. The new CLI tools (dscreate, dsctl, and dsconf) can do
everything all those other scripts could do plus more.
If you need help porting something to the new CLI I'd be glad to help.
Mark
Anything that matches anything that matches "rpm -ql 389-ds-base | grep pl$
| grep sbin”, plus any shell scripts?
Thanks,
James
This email and any attachments are intended solely for the use of the
individual or entity to whom it is addressed and may be confidential and/or
privileged.
If you are not one of the named recipients or have received this email
in error,
(i) you should not read, disclose, or copy it,
(ii) please notify sender of your receipt by reply email and delete
this email and all attachments,
(iii) Dassault Systèmes does not accept or assume any liability or
responsibility for any use of or reliance on this email.
Please be informed that your personal data are processed according to
our data privacy policy as described on our website. Should you have
any questions related to personal data protection, please contact 3DS
Data Protection Officer at
3ds.compliance-priv...@3ds.com<mailto:3ds.compliance-priv...@3ds.com>
For other languages, go to https://www.3ds.com/terms/email-disclaimer
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org To
unsubscribe send an email to 389-users-le...@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.fedorapr
oject.org
--
389 Directory Server Development Team
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@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
