Bug 517413 - Feature Request: Automatic failover to other configuration servers
Summary: Feature Request: Automatic failover to other configuration servers
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: 389
Classification: Retired
Component: Directory Server
Version: 1.2.6
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-13 19:26 UTC by Ryan Braun
Modified: 2015-11-19 22:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 22:19:00 UTC
Embargoed:


Attachments (Terms of Use)

Description Ryan Braun 2009-08-13 19:26:20 UTC
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.

Comment 1 Bug Zapper 2009-11-16 11:26:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Martin Kosek 2012-01-04 13:42:12 UTC
Upstream ticket:
https://fedorahosted.org/389/ticket/102

Comment 4 Noriko Hosoi 2015-11-19 22:17:04 UTC
Closing this bug since we moved to the ticket system:
https://fedorahosted.org/389/ticket/102


Note You need to log in before you can comment on or make changes to this bug.