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:  muks
                Type:  defect        |                       Status:
            Priority:  medium        |  reopened
           Component:  msgq          |                    Milestone:
            Keywords:                |  Sprint-20131015
           Sensitive:  0             |                   Resolution:
         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 muks):

 * status:  closed => reopened
 * resolution:  complete =>


Comment:

 Replying to [comment:8 kean]:
 > if you look at the code I pointed you to you will see how the decision
 is made.

 I think I was not clear in my last comments. I asked about **why** SIGKILL
 has to be sent, i.e., why it has to be shutdown forcefully like that. It
 is not about the code that sends the SIGKILL signal. In the normal way of
 things, components should gracefully shutdown.

 What happens that causes the ticket description's log?

 #1049 says we ought not to send the SIGKILL, but that is unrelated to what
 caused this component to not shutdown gracefully.

 Can you look at the traceback in the description, look at the code in
 question and diagnose:

 * What component is being shutdown? Is it `b10-msgq`?
 * Why is the component being shutdown at this point by `b10-init` when
 startup itself has failed and there is no process to kill?
 * If `b10-msgq` startup fails, it's fatal. How should `b10-init` handle
 it? Getting such a traceback would be bad. It would need to be logged
 appropriately and BIND 10 should stop gracefully. This problem will recur
 if we leave it as-is.

 These issues need not be fixed in this ticket. You can create new tickets
 for new work. But please diagnose what exactly went wrong.

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