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-Replicating-ADS-for-Failover.html > > > 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? ............. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.fedoraproject.org/pipermail/389-users/attachments/20080222/345b7b41/attachment.html
