BIND 10 #530: [kean] msgq error message for unable to create socket

[BIND 10 Development]

#530: [kean] msgq error message for unable to create socket
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:  kean
                Type:  defect        |                       Status:
            Priority:  medium        |  closed
           Component:  msgq          |                    Milestone:
            Keywords:                |  Sprint-20131015
           Sensitive:  0             |                   Resolution:  fixed
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  0.0           |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by kean):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 No it no longer generates a traceback. The bug is over 3 years old and
 obviously things have changed a lot in that time.

 The SIGKILL is deliberate because it is a "forceful" shutdown. See
 src/bin/init.py.in round about line 848. Here is what the output looks
 like:

 {{{
 ./bind10 -m /tmp/sock/msgq -v
 DEBUG [b10-msgq.msgq]: MSGQ_START Msgq version b10-msgq 20110127 (BIND 10
 20130529) starting
 DEBUG [b10-msgq.msgq]: MSGQ_LISTENER_SETUP Starting to listen on socket
 file '/tmp/sock/msgq'
 FATAL [b10-msgq.msgq]: MSGQ_LISTENER_FAILED Failed to initialize listener
 on socket file '/tmp/sock/msgq': [Errno 13] Permission denied
 FATAL [b10-msgq.msgq]: MSGQ_START_FAIL Error during startup: [Errno 13]
 Permission denied
 INFO [b10-init.init]: BIND10_STARTING starting BIND10: bind10 20110223
 (BIND 10 20130529)
 DEBUG [b10-init.init]: BIND10_CHECK_MSGQ_ALREADY_RUNNING checking if msgq
 is already running
 INFO [b10-init.init]: BIND10_CONFIGURATOR_START bind10 component
 configurator is starting up
 DEBUG [b10-init.init]: 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'}}'
 DEBUG [b10-init.init]: BIND10_CONFIGURATOR_RUN running plan of 3 tasks
 DEBUG [b10-init.init]: BIND10_CONFIGURATOR_TASK performing task start on
 Socket creator
 INFO [b10-init.init]: BIND10_COMPONENT_START component Socket creator is
 starting
 INFO [b10-init.init]: BIND10_SOCKCREATOR_INIT initializing socket creator
 parser
 DEBUG [b10-init.init]: BIND10_STARTED_PROCESS_PID started b10-sockcreator
 (PID 4763)
 DEBUG [b10-init.init]: BIND10_CONFIGURATOR_TASK performing task start on
 msgq
 INFO [b10-init.init]: BIND10_COMPONENT_START component msgq is starting
 INFO [b10-init.init]: BIND10_STARTING_PROCESS starting process b10-msgq
 DEBUG [b10-init.init]: BIND10_STARTED_PROCESS_PID started b10-msgq (PID
 4764)
 ERROR [b10-init.init]: BIND10_CONNECTING_TO_CC_FAIL failed to connect to
 configuration/command channel; try -v to see output from msgq
 ERROR [b10-init.init]: BIND10_COMPONENT_START_EXCEPTION component msgq
 failed to start: Unable to connect to c-channel after 5 seconds
 ERROR [b10-init.init]: BIND10_COMPONENT_FAILED component msgq (pid None)
 failed: unknown condition
 FATAL [b10-init.init]: BIND10_COMPONENT_UNSATISFIED component msgq is
 required to run and failed
 ERROR [b10-init.init]: BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator
 plan interrupted, only 1 of 3 done
 INFO [b10-init.init]: BIND10_KILLING_ALL_PROCESSES killing all started
 processes
 INFO [b10-init.init]: BIND10_SEND_SIGKILL sending SIGKILL to Socket
 creator (PID 4763)
 WARN [b10-init.init]: BIND10_SOCKCREATOR_KILL killing the socket creator
 FATAL [b10-init.init]: BIND10_STARTUP_ERROR error during startup: Unable
 to start b10-msgq: Unable to connect to c-channel after 5 seconds
 }}}

-- 
Ticket URL: <http://bind10.isc.org/ticket/530#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development