BIND 10 #615: custom configurations, ports,

BIND 10 Development do-not-reply at isc.org
Wed Mar 9 21:53:37 UTC 2011


#615: custom configurations, ports,
-------------------------------------+-------------------------------------
                 Reporter:  jreed    |                Owner:  UnAssigned
                     Type:  task     |               Status:  reviewing
                 Priority:  major    |            Milestone:  A-Team-
                Component:           |  Sprint-20110316
  Unclassified                       |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  0.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------

Comment (by jreed):

 My next problem is:

 {{{

 > config commit
 Error: Module 'ConfigManager' not responding
 Configuration not committed

 }}}

 That only happens when the other bind10 is running using alternative
 cmdctl port, configuration, datapath, and msgq. The bindctl has no options
 and is connected using the bind10 that was started with no options. Once I
 stopped the custom bind10 and stopped and started the bind10, I could do
 the commit (I didn't even have to restart bindctl -- it relogged in and
 already had the commit ready).

-- 
Ticket URL: <https://bind10.isc.org/ticket/615#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list