I would suggest adding something above the screenshot which shows the properly configured
2 server 1 admin console scenario. Perhaps simply a walkthrough of register-ds-admin.pl
when invoked interactively, for the relatively simple use case I was trying to execute.
What tripped me up was the point, highlighted in red. I was expecting to be able to enter
an LDAP URI: ldap://host.domain:389/o=NetscapeRoot since I was looking to register a
The reality is that the script is basically asking what Configuration Directory Server are
you going to Register INTO, before what remote server do you want to register. Since the
script probably can’t tell you that the local instance has/has not already been registered
in the local Configuration Directory Server (which is what I thought this script would
ONLY accomplish, initially), some more details in the documentation at the URL you mention
would have helped me.
Beginning registration of the Directory Server
The Directory Server locates its configuration file (dse.ldif) at /etc/dirsrv/slapd-ID, by
default. If you have Directory Server(s) which configuration file is put at the other
location, you need to input it to register the server.
If you have such Directory Server, type the full path that stores the configuration
If you don't, type return.
[configuration directory path or return]:
Do you want to use this server as Configuration Directory Server?
Directory server identifier [XXXX]:
Registering new Config DS: XXXX
Input the Directory Manager password on the server ldap1:
Please input the password for the Administrator User
Beginning Admin Server reconfiguration . . .
Creating Admin Server files and directories . . .
Updating adm.conf . . .
Updating admpw . . .
Registering admin server with the configuration directory server . . .
Updating adm.conf with information from configuration directory server . . .
Updating the configuration for the httpd engine . . .
Restarting admin server . . .
The admin server was successfully started.
Admin server was successfully reconfigured and started.
Do you want to register a remote server with the local configuration server (y/n)? y
From: Mark Reynolds [mailto:email@example.com]
Sent: Thursday, August 24, 2017 4:04 PM
To: Kirk MacDonald <Kirk.MacDonald(a)corp.eastlink.ca>; General discussion list for
the 389 Directory server project. <389-users(a)lists.fedoraproject.org>
Subject: Re: [389-users] Re: Registering remote 389-DS instances in Console
On 08/24/2017 02:31 PM, Kirk MacDonald wrote:
OK scratch that – it of course does work interactively. I was just being thrown off by the
fact one has to (re)config/specify the local Admin instance each time. Later on in the
interactive it asks for the remote hosts. Silly me.
Glad you got it working.
can improved here? Better docs on the "interactive" mode, or INF file mode?
From: Kirk MacDonald [mailto:Kirk.MacDonald@corp.eastlink.ca]
Sent: Thursday, August 24, 2017 1:36 PM
To: Mark Reynolds <firstname.lastname@example.org><mailto:email@example.com>; General
discussion list for the 389 Directory server project.
Subject: [389-users] Re: Registering remote 389-DS instances in Console
Thanks for the reply. I am struggling with the script because it only seems to see local
instances, when running the script interactively.
From: Mark Reynolds
Sent: Thursday, August 24, 2017 1:30 PM
To: General discussion list for the 389 Directory server project.; Kirk MacDonald
Subject: Re: [389-users] Registering remote 389-DS instances in Console
On 08/24/2017 11:30 AM, Kirk MacDonald wrote:
I have built 3 new 389-DS instances (389-Directory/184.108.40.206 B2017.145.2037) on different
services. Each has local Admin console. They are all in the same Administrative Domain.
Is the method to register the remote instances in each local Admin console what is
described here: http://www.port389.org/docs/389ds/design/console-remote-reg-design.html
Are you planning on using one central Admin/Config server? If so, you just need to
registers the other 3 remote servers with your local one. Done.
If want to goto any admin server and see all the other servers then you have to do the
same thing on each host: Goto Server A, and register B, C, D, goto Server B - register A,
C, D, etc, etc.
Or, is there a more “simplistic” approach that can be done via each Admin console UI?
Using the script is the easiest. There is no way to do it via the console ui.
389-users mailing list --
To unsubscribe send an email to