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
-------------------------------+----------------------------------------

Comment (by jreed):

 I got it by running bind10 twice (maybe a second or two between). I
 reproduced:


 {{{
 INFO [b10-boss.boss]: BIND10_STARTING starting BIND10: bind10 20110223
 (BIND 10 20121219)
 DEBUG [b10-boss.boss]: BIND10_CHECK_MSGQ_ALREADY_RUNNING checking if msgq
 is already running
 FATAL [b10-boss.boss]: BIND10_MSGQ_ALREADY_RUNNING msgq daemon already
 running, cannot start
 FATAL [b10-boss.boss]: BIND10_STARTUP_ERROR error during startup: b10-msgq
 already running, or socket file not cleaned , cannot start
 2013-01-30 09:22:18.807 ERROR [b10-msgq.msgq/17782] MSGQ_RECV_ERR Error
 reading from socket 15: EOF
 }}}

 Yes it gets the FATAL as expected. Also see the msgq ERROR.

 Process ID 17782 is the already-running b10-msgq.

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