BIND 10 #2616: existing msgq has confusing error if another bind10 tries to start

[BIND 10 Development]

#2616: existing msgq has confusing error if another bind10 tries to start
-------------------------------+----------------------------------------
            Reporter:  jreed   |                        Owner:  jreed
                Type:  defect  |                       Status:  assigned
            Priority:  low     |                    Milestone:
           Component:  msgq    |                   Resolution:
            Keywords:          |                 CVSS Scoring:
           Sensitive:  0       |              Defect Severity:  N/A
         Sub-Project:  Core    |  Feature Depending on Ticket:
Estimated Difficulty:  0       |          Add Hours to Ticket:  0
         Total Hours:  0       |                    Internal?:  0
-------------------------------+----------------------------------------
Changes (by shane):

 * owner:   => jreed
 * status:  new => assigned
 * milestone:  New Tasks =>


Comment:

 This should not happen, as we have code to check for an already-running
 msgq when we start up:

 {{{
 #!python
         # Try to connect to the c-channel daemon, to see if it is already
         # running
         c_channel_env = {}
         if self.msgq_socket_file is not None:
              c_channel_env["BIND10_MSGQ_SOCKET_FILE"] =
 self.msgq_socket_file
         logger.debug(DBG_PROCESS, BIND10_CHECK_MSGQ_ALREADY_RUNNING)
         try:
             self.cc_session = isc.cc.Session(self.msgq_socket_file)
             logger.fatal(BIND10_MSGQ_ALREADY_RUNNING)
             return "b10-msgq already running, or socket file not cleaned ,
 cannot start"
         except isc.cc.session.SessionError:
             # this is the case we want, where the msgq is not running
             pass
 }}}

 If this didn't work, that is the bug.

 How exactly did you get this condition?

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