[Fedora-directory-users] Setting up Multiple Directory Servers - in a multi-master mesh. Having problems with admin server.

[Howard Wilkinson]

We are configuring a new site which has a pair of Master servers and 2 
"slave" servers. We have followed the following sequence of steps but 
have fallen at the last fence in getting all of the servers registered 
with admin servers.

    Install fresh copies of fedora-ds* 1.1 packages.
    Run setup-ds-admin.pl on the primary master (primary because it is
    the first one)
    Setup SSL access to server
    Create ROOTDNs.
    Populate server with initial data.

    Run setup-ds.pl on the secondary master and the 2 slaves.
    Setup SSL access on these servers
    Create ROOTDNs
    Initiate multi-master replication for all roots from primary master
    to secondary master.
    Initiate ordinary replication from the primary master to each slave.
    Initiate ordinary replication from the secondary master to each slave.


We are replicating o=NetscapeRoot as well as all of our Roots.

The servers are setup using this inf file.

    [General]

    FullMachineName=${HOSTNAMEFQDN}

    SuiteSpotUserID=${LDAPUID}

    SuiteSpotGroup=${LDAPGID}

    ServerRoot=/usr/lib/fedora-ds

    AdminDomain=${MASTERDOMAIN}

    ConfigDirectoryAdminID=admin

    ConfigDirectoryAdminPwd=${ADMINPASSWD}

    ConfigDirectoryLdapURL=ldap://${MASTERHOSTFQDN}:${LDAPPORT}/o=NetscapeRoot

    UserDirectoryAdminID=admin

    UserDirectoryAdminPwd=${ADMINPASSWD}

    UserDirectoryLdapURL=ldap://${HOSTNAMEFQDN}:${LDAPPORT}/${MASTERDN}

    #CACertificateURL=

    [slapd]

    SlapdConfigForMC=${SlapdConfigForMC} # Set to 1 on Master, 0 on all others

    SecurityOn=No

    UseExistingMC=${UseExistingMC} # Set to 0 on Master, 1 on all others

    UseExistingUG=0

    ServerPort=${LDAPPORT}

    ServerIdentifier=${HOSTNAME}

    Suffix=dc=${MASTERDN}

    RootDN=cn=Directory Manager

    AddSampleEntries=No

    InstallLdifFile=none

    AddOrgEntries=No

    DisableSchemaChecking=No

    RootDNPwd=${DIRMANPASSWD}

    start_server=1

    install_full_schema=1

    [admin]

    SysUser=${LDAPUID}

    Port=${ADMINPORT}

    ServerIpAddress=*

    ServerAdminID=admin

    ServerAdminPwd=${ADMINPASSWD}

    ApacheDir=/usr/sbin/

    ApacheRoot=/etc/httpd


I then run up fedora-idm-console on the master. We can see the master 
server in the console but cannot see any of the others!

What have we missed? What do we need to do to get this running and then 
switch each server over to using its local admin server (with replicated 
data from the master)

Note we cannot get "register-ds-admin.pl" to do anything in this 
environment a sit just keeps asking for the server name and any input 
results in it asking again for the server name.

Regards, Howard.

[Rich Megginson]

Howard Wilkinson wrote:
>  We are configuring a new site which has a pair of Master servers and
> 2 
>  "slave" servers. We have followed the following sequence of steps but 
>  have fallen at the last fence in getting all of the servers registered 
>  with admin servers.
>
>      Install fresh copies of fedora-ds* 1.1 packages.
>      Run setup-ds-admin.pl on the primary master (primary because it is
>      the first one)
>      Setup SSL access to server
>      Create ROOTDNs.
>      Populate server with initial data.
>
>      Run setup-ds.pl on the secondary master and the 2 slaves.
>  
Why did you run setup-ds.pl instead of setup-ds-admin.pl?
>      Setup SSL access on these servers
>      Create ROOTDNs
>      Initiate multi-master replication for all roots from primary
>      master to secondary master.
>      Initiate ordinary replication from the primary master to each slave.
>      Initiate ordinary replication from the secondary master to each slave.
>
>
>  We are replicating o=NetscapeRoot as well as all of our Roots.
>
>  The servers are setup using this inf file.
>
>      [General]
>
>      FullMachineName=${HOSTNAMEFQDN}
>
>      SuiteSpotUserID=${LDAPUID}
>
>      SuiteSpotGroup=${LDAPGID}
>
>      ServerRoot=/usr/lib/fedora-ds
>
>      AdminDomain=${MASTERDOMAIN}
>
>      ConfigDirectoryAdminID=admin
>
>      ConfigDirectoryAdminPwd=${ADMINPASSWD}
>
>      ConfigDirectoryLdapURL=ldap://${MASTERHOSTFQDN}:${LDAPPORT}/o=NetscapeRoot
>
>      UserDirectoryAdminID=admin
>
>      UserDirectoryAdminPwd=${ADMINPASSWD}
>
>      UserDirectoryLdapURL=ldap://${HOSTNAMEFQDN}:${LDAPPORT}/${MASTERDN}
>
>      #CACertificateURL=
>
>      [slapd]
>
>      SlapdConfigForMC=${SlapdConfigForMC} # Set to 1 on Master, 0 on all others
>
>      SecurityOn=No
>
>      UseExistingMC=${UseExistingMC} # Set to 0 on Master, 1 on all others
>
>      UseExistingUG=0
>
>      ServerPort=${LDAPPORT}
>
>      ServerIdentifier=${HOSTNAME}
>
>      Suffix=dc=${MASTERDN}
>
>      RootDN=cn=Directory Manager
>
>      AddSampleEntries=No
>
>      InstallLdifFile=none
>
>      AddOrgEntries=No
>
>      DisableSchemaChecking=No
>
>      RootDNPwd=${DIRMANPASSWD}
>
>      start_server=1
>
>      install_full_schema=1
>
>      [admin]
>
>      SysUser=${LDAPUID}
>
>      Port=${ADMINPORT}
>
>      ServerIpAddress=*
>
>      ServerAdminID=admin
>
>      ServerAdminPwd=${ADMINPASSWD}
>
>      ApacheDir=/usr/sbin/
>
>      ApacheRoot=/etc/httpd
>
>
>  I then run up fedora-idm-console on the master. We can see the master 
>  server in the console but cannot see any of the others! 
Not surprising since
setup-ds.pl doesn't do any console/admin server 
registration.
>  What have we missed? What do we need to do to get this running and 
>  then switch each server over to using its local admin server (with 
>  replicated data from the master)
>
>  Note we cannot get "register-ds-admin.pl" to do anything in this 
>  environment a sit just keeps asking for the server name and any input 
>  results in it asking again for the server name. 
register-ds-admin.pl should work -
can you provide more details?  Script 
output?
>  Regards, Howard.
>  ------------------------------------------------------------------------
>
>  --
>  Fedora-directory-users mailing list
>  Fedora-directory-users(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

[Howard Wilkinson]

Rich Megginson wrote:
>  Howard Wilkinson wrote:
> > We are configuring a new site which has a pair of Master servers and 
> > 2 "slave" servers. We have followed the following sequence of steps 
> > but have fallen at the last fence in getting all of the servers 
> > registered with admin servers.
> >
> >     Install fresh copies of fedora-ds* 1.1 packages.
> >     Run setup-ds-admin.pl on the primary master (primary because it is
> >     the first one)
> >     Setup SSL access to server
> >     Create ROOTDNs.
> >     Populate server with initial data.
> >
> >     Run setup-ds.pl on the secondary master and the 2 slaves.
> >
>  Why did you run setup-ds.pl instead of setup-ds-admin.pl?
> >
> >     Setup SSL access on these servers
> >     Create ROOTDNs
> >     Initiate multi-master replication for all roots from primary
> >     master to secondary master.
> >     Initiate ordinary replication from the primary master to each slave.
> >     Initiate ordinary replication from the secondary master to each 
> > slave.
> >
> >
> > We are replicating o=NetscapeRoot as well as all of our Roots.
> >
> > The servers are setup using this inf file.
> >
> >     [General]
> >
> >     FullMachineName=${HOSTNAMEFQDN}
> >
> >     SuiteSpotUserID=${LDAPUID}
> >
> >     SuiteSpotGroup=${LDAPGID}
> >
> >     ServerRoot=/usr/lib/fedora-ds
> >
> >     AdminDomain=${MASTERDOMAIN}
> >
> >     ConfigDirectoryAdminID=admin
> >
> >     ConfigDirectoryAdminPwd=${ADMINPASSWD}
> >
> >     
> > ConfigDirectoryLdapURL=ldap://${MASTERHOSTFQDN}:${LDAPPORT}/o=NetscapeRoot 
> >
> >
> >     UserDirectoryAdminID=admin
> >
> >     UserDirectoryAdminPwd=${ADMINPASSWD}
> >
> >     UserDirectoryLdapURL=ldap://${HOSTNAMEFQDN}:${LDAPPORT}/${MASTERDN}
> >
> >     #CACertificateURL=
> >
> >     [slapd]
> >
> >     SlapdConfigForMC=${SlapdConfigForMC} # Set to 1 on Master, 0 on 
> > all others
> >
> >     SecurityOn=No
> >
> >     UseExistingMC=${UseExistingMC} # Set to 0 on Master, 1 on all others
> >
> >     UseExistingUG=0
> >
> >     ServerPort=${LDAPPORT}
> >
> >     ServerIdentifier=${HOSTNAME}
> >
> >     Suffix=dc=${MASTERDN}
> >
> >     RootDN=cn=Directory Manager
> >
> >     AddSampleEntries=No
> >
> >     InstallLdifFile=none
> >
> >     AddOrgEntries=No
> >
> >     DisableSchemaChecking=No
> >
> >     RootDNPwd=${DIRMANPASSWD}
> >
> >     start_server=1
> >
> >     install_full_schema=1
> >
> >     [admin]
> >
> >     SysUser=${LDAPUID}
> >
> >     Port=${ADMINPORT}
> >
> >     ServerIpAddress=*
> >
> >     ServerAdminID=admin
> >
> >     ServerAdminPwd=${ADMINPASSWD}
> >
> >     ApacheDir=/usr/sbin/
> >
> >     ApacheRoot=/etc/httpd
> >
> >
> > I then run up fedora-idm-console on the master. We can see the master 
> > server in the console but cannot see any of the others!
>  Not surprising since setup-ds.pl doesn't do any console/admin server 
>  registration. 
Tried with setup-ds-admin.pl instead but still not working! What 
settings do I need in the inf file for the second and subsequent servers?
> >
> > What have we missed? What do we need to do to get this running and 
> > then switch each server over to using its local admin server (with 
> > replicated data from the master)
> >
> > Note we cannot get "register-ds-admin.pl" to do anything in this 
> > environment a sit just keeps asking for the server name and any input 
> > results in it asking again for the server name.
>  register-ds-admin.pl should work - can you provide more details?  
>  Script output? 
On the master it never gets past asking for the password for the 
administrator.
On the other hosts it will not accept any directory server name i.e. 
second prompt just cycles - but this may be an artifact of the failure 
of setup-ds-admin to register the server correctly anyway as we may have 
wrong settings in the inf file!
> >
> > Regards, Howard.
> > ------------------------------------------------------------------------
> >
> > -- 
> > Fedora-directory-users mailing list
> > Fedora-directory-users(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-directory-users
> >   
>
>  ------------------------------------------------------------------------
>
>  --
>  Fedora-directory-users mailing list
>  Fedora-directory-users(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

[Rich Megginson]

Howard Wilkinson wrote:
>  Rich Megginson wrote:
> > Howard Wilkinson wrote:
> >> We are configuring a new site which has a pair of Master servers and 
> >> 2 "slave" servers. We have followed the following sequence of steps 
> >> but have fallen at the last fence in getting all of the servers 
> >> registered with admin servers.
> >>
> >>     Install fresh copies of fedora-ds* 1.1 packages.
> >>     Run setup-ds-admin.pl on the primary master (primary because it is
> >>     the first one)
> >>     Setup SSL access to server
> >>     Create ROOTDNs.
> >>     Populate server with initial data.
> >>
> >>     Run setup-ds.pl on the secondary master and the 2 slaves.
> >>
> > Why did you run setup-ds.pl instead of setup-ds-admin.pl?
> >>
> >>     Setup SSL access on these servers
> >>     Create ROOTDNs
> >>     Initiate multi-master replication for all roots from primary
> >>     master to secondary master.
> >>     Initiate ordinary replication from the primary master to each 
> >> slave.
> >>     Initiate ordinary replication from the secondary master to each 
> >> slave.
> >>
> >>
> >> We are replicating o=NetscapeRoot as well as all of our Roots.
> >>
> >> The servers are setup using this inf file.
> >>
> >>     [General]
> >>
> >>     FullMachineName=${HOSTNAMEFQDN}
> >>
> >>     SuiteSpotUserID=${LDAPUID}
> >>
> >>     SuiteSpotGroup=${LDAPGID}
> >>
> >>     ServerRoot=/usr/lib/fedora-ds
> >>
> >>     AdminDomain=${MASTERDOMAIN}
> >>
> >>     ConfigDirectoryAdminID=admin
> >>
> >>     ConfigDirectoryAdminPwd=${ADMINPASSWD}
> >>
> >>     
> >> ConfigDirectoryLdapURL=ldap://${MASTERHOSTFQDN}:${LDAPPORT}/o=NetscapeRoot 
> >>
> >>
> >>     UserDirectoryAdminID=admin
> >>
> >>     UserDirectoryAdminPwd=${ADMINPASSWD}
> >>
> >>     UserDirectoryLdapURL=ldap://${HOSTNAMEFQDN}:${LDAPPORT}/${MASTERDN}
> >>
> >>     #CACertificateURL=
> >>
> >>     [slapd]
> >>
> >>     SlapdConfigForMC=${SlapdConfigForMC} # Set to 1 on Master, 0 on 
> >> all others
> >>
> >>     SecurityOn=No
> >>
> >>     UseExistingMC=${UseExistingMC} # Set to 0 on Master, 1 on all 
> >> others
> >>
> >>     UseExistingUG=0
> >>
> >>     ServerPort=${LDAPPORT}
> >>
> >>     ServerIdentifier=${HOSTNAME}
> >>
> >>     Suffix=dc=${MASTERDN}
> >>
> >>     RootDN=cn=Directory Manager
> >>
> >>     AddSampleEntries=No
> >>
> >>     InstallLdifFile=none
> >>
> >>     AddOrgEntries=No
> >>
> >>     DisableSchemaChecking=No
> >>
> >>     RootDNPwd=${DIRMANPASSWD}
> >>
> >>     start_server=1
> >>
> >>     install_full_schema=1
> >>
> >>     [admin]
> >>
> >>     SysUser=${LDAPUID}
> >>
> >>     Port=${ADMINPORT}
> >>
> >>     ServerIpAddress=*
> >>
> >>     ServerAdminID=admin
> >>
> >>     ServerAdminPwd=${ADMINPASSWD}
> >>
> >>     ApacheDir=/usr/sbin/
> >>
> >>     ApacheRoot=/etc/httpd
> >>
> >>
> >> I then run up fedora-idm-console on the master. We can see the 
> >> master server in the console but cannot see any of the others!
> > Not surprising since setup-ds.pl doesn't do any console/admin server 
> > registration.
>  Tried with setup-ds-admin.pl instead but still not working! 
What do you mean by not
working?  Does it hang?  Give errors?  Simply 
not do what you want it to?  Note that if you ran setup-ds.pl before, it 
will have already created the directory server you wanted to create with 
setup-ds-admin.pl - setup-ds-admin.pl will only create additional 
directory server instances, not reregister/reconfigure existing ones.
>  What settings do I need in the inf file for the second and subsequent
>
>  servers? 
You at least need a new server identifier and a new port to create an 
additional instance on the same machine that already has a directory 
server instance.
> >>
> >> What have we missed? What do we need to do to get this running and 
> >> then switch each server over to using its local admin server (with 
> >> replicated data from the master)
> >>
> >> Note we cannot get "register-ds-admin.pl" to do anything in this 
> >> environment a sit just keeps asking for the server name and any 
> >> input results in it asking again for the server name.
> > register-ds-admin.pl should work - can you provide more details?  
> > Script output?
>  On the master it never gets past asking for the password for the 
>  administrator.
>  On the other hosts it will not accept any directory server name i.e. 
>  second prompt just cycles - but this may be an artifact of the failure 
>  of setup-ds-admin to register the server correctly anyway as we may 
>  have wrong settings in the inf file! 
I'm just not sure what's going on. 
You're having multiple problems that 
may be due to DNS/NIS configuration or old files left around from 
previous incomplete installs or ???  If you can, I suggest you start 
over from scratch -

yum erase svrcore idm-console-framework
then
rm -rf /etc/dirsrv /usr/lib/dirsrv
rm -rf `find /var -name dirsrv -print`

Then reinstall and use setup-ds-admin.pl for your primary machine with 
your configuration DS then subsequent installs on other machines.
> >>
> >> Regards, Howard.
> >> ------------------------------------------------------------------------ 
> >>
> >>
> >> -- 
> >> Fedora-directory-users mailing list
> >> Fedora-directory-users(a)redhat.com
> >> https://www.redhat.com/mailman/listinfo/fedora-directory-users
> >>   
> >
> > ------------------------------------------------------------------------
> >
> > --
> > Fedora-directory-users mailing list
> > Fedora-directory-users(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-directory-users
> >   
>
>  ------------------------------------------------------------------------
>
>  --
>  Fedora-directory-users mailing list
>  Fedora-directory-users(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

[Howard Wilkinson]

Richard et al,

I have obviously confused you on this so to start again!

I have four machines on which I am installing directory server version 1.1.

I have automated the install so that I start with a virgin install every 
time - erase the packages and delete all of the files left lying around 
and then reinstall the packages.

I want to set up the four machines in a fault-tolerant fashion. So I 
have an initial master, a secondary on a separate machine, and 2 
consumers on the other machines.

I can setup the servers on each machine with their own admin server and 
can gt the SSL working and have modified the mmr script and can get all 
other server to replicate. Master and Secondary in multi-master mode, 
consumers fed from master and secondary.

What I want to achieve is to have all of the servers sharing the 
o=NetscapeRoot paritition (i.e. all having an admin server but all 
having the same configuration for the admin server). Now this means that 
they need to be in a mesh multi-master - OK I can set that up but I 
can't get the servers to register cleanly with the individual admin 
servers on each of the machines.

I understood that register-ds-admin.pl was the answer but the more I 
look at this it seems to only manage multiple instances on one machine. 
So how do I do this.

If I replicate the o=NetscapeRoot with each server registered to its own 
admin-server. Then the admin-servers only have one server registered and 
it seems to be the master (but that may be timing). If I try to register 
the secondary and consumers with the master admin-server then nothing 
happens. SO I am missing a trick.

I have the following silent set up file I use to configure each server.

    [General]
    FullMachineName=${HOSTNAMEFQDN}
    SuiteSpotUserID=${LDAPUID}
    SuiteSpotGroup=${LDAPGID}
    ServerRoot=/usr/lib/fedora-ds
    AdminDomain=${MASTERDOMAIN}
    ConfigDirectoryAdminID=admin
    ConfigDirectoryAdminPwd=${ADMINPASSWD}
    ConfigDirectoryLdapURL=${ConfigDirectoryLdapURL}
    UserDirectoryAdminID=admin
    UserDirectoryAdminPwd=${ADMINPASSWD}
    UserDirectoryLdapURL=ldap://${HOSTNAMEFQDN}:${LDAPPORT}/${MASTERDN}
    #CACertificateURL=

    [slapd]
    SlapdConfigForMC=${SlapdConfigForMC}
    SecurityOn=No
    UseExistingMC=${UseExistingMC}
    UseExistingUG=0
    ServerPort=${LDAPPORT}
    ServerIdentifier=${HOSTNAME}
    Suffix=dc=${MASTERDN}
    RootDN=cn=Directory Manager
    AddSampleEntries=No
    InstallLdifFile=none
    AddOrgEntries=No
    DisableSchemaChecking=No
    RootDNPwd=${DIRMANPASSWD}
    start_server=1
    install_full_schema=1

    [admin]
    SysUser=${LDAPUID}
    Port=${ADMINPORT}
    ServerIpAddress=*
    ServerAdminID=admin
    ServerAdminPwd=${ADMINPASSWD}
    ApacheDir=/usr/sbin/
    ApacheRoot=/etc/httpd

I set

    SlapdConfigForMC=1
    UseExistingMC=0
    ConfigDirectoryLdapURL=ldap://${HOSTNAMEFQDN}:${LDAPPORT}/o=NetscapeRoot

for the first case of installing each server locally and change to

    SlapdConfigForMC=1
    UseExistingMC=1
    ConfigDirectoryLdapURL=ldap://${MASTERHOSTFQDN}:${LDAPPORT}/o=NetscapeRoot

for the second case where I have tried to get all registered with one 
admin server. But no luck.

Help!

[Rich Megginson]

Howard Wilkinson wrote:
>  Richard et al,
>
>  I have obviously confused you on this so to start again!
>
>  I have four machines on which I am installing directory server version 
>  1.1.
>
>  I have automated the install so that I start with a virgin install 
>  every time - erase the packages and delete all of the files left lying 
>  around and then reinstall the packages.
>
>  I want to set up the four machines in a fault-tolerant fashion. So I 
>  have an initial master, a secondary on a separate machine, and 2 
>  consumers on the other machines.
>
>  I can setup the servers on each machine with their own admin server 
>  and can gt the SSL working and have modified the mmr script and can 
>  get all other server to replicate. Master and Secondary in 
>  multi-master mode, consumers fed from master and secondary.
>
>  What I want to achieve is to have all of the servers sharing the 
>  o=NetscapeRoot paritition (i.e. all having an admin server but all 
>  having the same configuration for the admin server). Now this means 
>  that they need to be in a mesh multi-master - OK I can set that up but 
>  I can't get the servers to register cleanly with the individual admin 
>  servers on each of the machines. 
Ok.  I understand.  First, you have to follow
these guidelines - 
http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Managing_Replication...

Next, it sounds like you are running into this bug - 
https://bugzilla.redhat.com/show_bug.cgi?id=431103
>  I understood that register-ds-admin.pl was the answer but the more I 
>  look at this it seems to only manage multiple instances on one 
>  machine. So how do I do this.
>
>  If I replicate the o=NetscapeRoot with each server registered to its 
>  own admin-server. Then the admin-servers only have one server 
>  registered and it seems to be the master (but that may be timing). If 
>  I try to register the secondary and consumers with the master 
>  admin-server then nothing happens. SO I am missing a trick. 
>  I have the following silent set up file I use to configure each server.
>
>      [General]
>      FullMachineName=${HOSTNAMEFQDN}
>      SuiteSpotUserID=${LDAPUID}
>      SuiteSpotGroup=${LDAPGID}
>      ServerRoot=/usr/lib/fedora-ds
>      AdminDomain=${MASTERDOMAIN}
>      ConfigDirectoryAdminID=admin
>      ConfigDirectoryAdminPwd=${ADMINPASSWD}
>      ConfigDirectoryLdapURL=${ConfigDirectoryLdapURL}
>      UserDirectoryAdminID=admin
>      UserDirectoryAdminPwd=${ADMINPASSWD}
>      UserDirectoryLdapURL=ldap://${HOSTNAMEFQDN}:${LDAPPORT}/${MASTERDN}
>      #CACertificateURL=
>
>      [slapd]
>      SlapdConfigForMC=${SlapdConfigForMC}
>      SecurityOn=No
>      UseExistingMC=${UseExistingMC}
>      UseExistingUG=0
>      ServerPort=${LDAPPORT}
>      ServerIdentifier=${HOSTNAME}
>      Suffix=dc=${MASTERDN}
>      RootDN=cn=Directory Manager
>      AddSampleEntries=No
>      InstallLdifFile=none
>      AddOrgEntries=No
>      DisableSchemaChecking=No
>      RootDNPwd=${DIRMANPASSWD}
>      start_server=1
>      install_full_schema=1
>
>      [admin]
>      SysUser=${LDAPUID}
>      Port=${ADMINPORT}
>      ServerIpAddress=*
>      ServerAdminID=admin
>      ServerAdminPwd=${ADMINPASSWD}
>      ApacheDir=/usr/sbin/
>      ApacheRoot=/etc/httpd
>
>  I set
>
>      SlapdConfigForMC=1
>      UseExistingMC=0
>      ConfigDirectoryLdapURL=ldap://${HOSTNAMEFQDN}:${LDAPPORT}/o=NetscapeRoot
>
>  for the first case of installing each server locally and change to
>
>      SlapdConfigForMC=1
>      UseExistingMC=1
>      ConfigDirectoryLdapURL=ldap://${MASTERHOSTFQDN}:${LDAPPORT}/o=NetscapeRoot
>
>  for the second case where I have tried to get all registered with one 
>  admin server. But no luck.
>
>  Help!
>  ------------------------------------------------------------------------
>
>  --
>  Fedora-directory-users mailing list
>  Fedora-directory-users(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

[Howard Wilkinson]

Rich Megginson wrote:
>  Howard Wilkinson wrote:
> > Richard et al,
> >
> > I have obviously confused you on this so to start again!
> >
> > I have four machines on which I am installing directory server 
> > version 1.1.
> >
> > I have automated the install so that I start with a virgin install 
> > every time - erase the packages and delete all of the files left 
> > lying around and then reinstall the packages.
> >
> > I want to set up the four machines in a fault-tolerant fashion. So I 
> > have an initial master, a secondary on a separate machine, and 2 
> > consumers on the other machines.
> >
> > I can setup the servers on each machine with their own admin server 
> > and can gt the SSL working and have modified the mmr script and can 
> > get all other server to replicate. Master and Secondary in 
> > multi-master mode, consumers fed from master and secondary.
> >
> > What I want to achieve is to have all of the servers sharing the 
> > o=NetscapeRoot paritition (i.e. all having an admin server but all 
> > having the same configuration for the admin server). Now this means 
> > that they need to be in a mesh multi-master - OK I can set that up 
> > but I can't get the servers to register cleanly with the individual 
> > admin servers on each of the machines.
>  Ok.  I understand.  First, you have to follow these guidelines - 
>
> http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Managing_Replication...
>
>
>
>  Next, it sounds like you are running into this bug - 
>  https://bugzilla.redhat.com/show_bug.cgi?id=431103 
Have followed these
instructions, with the fixes from the patch and we 
are further along! I now have all servers registered on the master 
server and can see them from there as expected.

I now face an issue with "register-ds-admin.pl" when I run it in the 
secondary server I get the following output.

    If you have such Directory Server, type the full path that stores
    the configuration file.

    If you don't, type return.
    [configuration directory path or return]:


    ==============================================================================
    Candidate servers to register:
        /etc/dirsrv/slapd-backus

    ==============================================================================
    Do you want to use this server as Configuration Directory Server?

    Directory server identifier: backus

    ==============================================================================
    Do you want to use this server as Configuration Directory Server?

    Directory server identifier:

and this justs keeps cycling asking the same question.

If I run on one of the consumers the behaviour is different but still no 
very useful. I get a bit further but it refuses to recognise the admin 
password.

    Do you want to use this server as Configuration Directory Server?

    Directory server identifier: barnacle

    ==============================================================================
    Cleaning up old Config DS:

    ==============================================================================
    Please input the password for the Administrator User uid=admin,
    ou=Administrators, ou=TopologyManagement, o=NetscapeRoot:
    Error: failed to clean up the configuration info from the old
    Configuration
    Directory Server .

    ==============================================================================
    Please input the password for the Administrator User uid=admin,
    ou=Administrators, ou=TopologyManagement, o=NetscapeRoot:

I get the same behaviour if I run on the Master server.

Any suggestions?

.............