BIND 10 #1624: Unable to start b10-msgq, but it is started and running

[BIND 10 Development]

#1624: Unable to start b10-msgq, but it is started and running
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 I started bind10 --verbose:

 {{{
 2012-01-24 08:15:22.099 INFO  [b10-boss.boss] BIND10_STARTING starting
 BIND10: bind10 20110223 (BIND 10 20111129)
 2012-01-24 08:15:22.119 DEBUG [b10-boss.boss]
 BIND10_CHECK_MSGQ_ALREADY_RUNNING checking if msgq is already running
 2012-01-24 08:15:22.138 INFO  [b10-boss.boss] BIND10_CONFIGURATOR_START
 bind10 component configurator is starting up
 2012-01-24 08:15:22.158 DEBUG [b10-boss.boss] BIND10_CONFIGURATOR_BUILD
 building plan '{}' -> '{'sockcreator': {'priority': 200, 'kind': 'core',
 'special': 'sockcreator'}, 'msgq': {'priority': 199, 'kind': 'core',
 'special': 'msgq'}, 'cfgmgr': {'priority': 198, 'kind': 'core', 'special':
 'cfgmgr'}}'
 2012-01-24 08:15:22.176 DEBUG [b10-boss.boss] BIND10_CONFIGURATOR_RUN
 running plan of 3 tasks
 2012-01-24 08:15:22.192 DEBUG [b10-boss.boss] BIND10_CONFIGURATOR_TASK
 performing task start on Socket creator
 2012-01-24 08:15:22.214 INFO  [b10-boss.boss] BIND10_COMPONENT_START
 component Socket creator is starting
 2012-01-24 08:15:22.294 INFO  [b10-boss.boss] BIND10_SOCKCREATOR_INIT
 initializing socket creator parser
 2012-01-24 08:15:22.314 DEBUG [b10-boss.boss] BIND10_STARTED_PROCESS_PID
 started b10-sockcreator (PID 8761)
 2012-01-24 08:15:22.334 DEBUG [b10-boss.boss] BIND10_CONFIGURATOR_TASK
 performing task start on msgq
 2012-01-24 08:15:22.354 INFO  [b10-boss.boss] BIND10_COMPONENT_START
 component msgq is starting
 2012-01-24 08:15:22.371 INFO  [b10-boss.boss] BIND10_STARTING_PROCESS
 starting process b10-msgq
 2012-01-24 08:15:22.619 DEBUG [b10-boss.boss] BIND10_STARTED_PROCESS_PID
 started b10-msgq (PID 6349)
 2012-01-24 08:15:27.753 ERROR [b10-boss.boss]
 BIND10_COMPONENT_START_EXCEPTION component msgq failed to start: Unable to
 connect to c-channel after 5 seconds
 2012-01-24 08:15:27.757 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
 component msgq (pid None) failed with unknown exit status
 2012-01-24 08:15:27.758 FATAL [b10-boss.boss] BIND10_COMPONENT_UNSATISFIED
 component msgq is required to run and failed
 2012-01-24 08:15:27.759 ERROR [b10-boss.boss]
 BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only 1
 of 3 done
 2012-01-24 08:15:27.760 INFO  [b10-boss.boss] BIND10_KILLING_ALL_PROCESSES
 killing all started processes
 2012-01-24 08:15:27.760 INFO  [b10-boss.boss] BIND10_KILL_PROCESS killing
 process Socket creator
 2012-01-24 08:15:27.761 WARN  [b10-boss.boss] BIND10_SOCKCREATOR_KILL
 killing the socket creator
 2012-01-24 08:15:27.769 FATAL [b10-boss.boss] BIND10_STARTUP_ERROR error
 during startup: Unable to start b10-msgq: Component failed during startup

 }}}

 Now it has been a few minutes b10-msgq hasn't exited yet. I sent a term
 signal to it and it exited.

 I could repeat this.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1624>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development