https://bugzilla.redhat.com/show_bug.cgi?id=517413
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.11) Gecko/2009061212 Iceweasel/3.0.6 (Debian-3.0.6-1) When setting up more then 2+ MMR servers with both userroot and netscaperoot replicated, you should be able to use any of those servers as a config server for other slave servers automatically. As it stands now, the only server the slave will contact is the original server you've registered it to. If that server ever fails you need to manually edit adm.conf and probably some settings in dse.ldif aswell. Reproducible: Always I suppose in in theory I could add a servers.conf file in /etc/dirsrv/admin-serv with all my config servers. Then hack up /etc/init.d/dirsrv-admin to try and bind to any of those servers, then take that server and "sed it" into adm.conf to get around this for now.
batch update to FUTURE milestone
set default ticket origin to Community
Added initial screened field value.
Metadata Update from @nkinder: - Issue set to the milestone: 389-admin,console FUTURE
Admin server/Console is deprecated, closing ticket...
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None (was: Needs Review) - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/102
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.