BIND 10 #1049: bind10 should not resort to SIGKILL

[BIND 10 Development]

#1049: bind10 should not resort to SIGKILL
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  Year 3 Task
                   Priority:  major  |  Backlog
                  Component:  Boss   |            Resolution:
  of BIND                            |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  0.0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jreed):

 This problem continues. We should figure why components aren't exiting and
 don't resort to forced kill.

 Here are some examples:

 {{{
 2012-01-18 12:54:51.120 DEBUG [b10-boss.boss] BIND10_CONFIGURATOR_TASK
 performing task stop on Socket creator
 2012-01-18 12:54:51.120 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component Socket creator is being stopped
 2012-01-18 12:54:51.161 INFO  [b10-boss.boss] BIND10_SOCKCREATOR_TERMINATE
 terminating socket creator
 2012-01-18 12:54:51.295 DEBUG [b10-boss.boss] BIND10_CONFIGURATOR_TASK
 performing task stop on msgq
 2012-01-18 12:54:51.303 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component msgq is being stopped
 2012-01-18 12:54:51.303 DEBUG [b10-boss.boss] BIND10_CONFIGURATOR_TASK
 performing task stop on b10-cmdctl
 2012-01-18 12:54:51.303 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-cmdctl is being stopped
 2012-01-18 12:54:51.329 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-cmdctl to shut down
 2012-01-18 12:54:51.411 ERROR [b10-boss.boss]
 BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only 2
 of 8 done
 2012-01-18 12:54:52.503 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 1481 of Socket creator ended with status 0
 ...
 2012-01-18 12:54:52.580 INFO  [b10-boss.boss] BIND10_SEND_SIGTERM sending
 SIGTERM to cfgmgr (PID 1671)
 ...
 2012-01-18 12:54:52.626 INFO  [b10-boss.boss] BIND10_SEND_SIGTERM sending
 SIGTERM to b10-cmdctl (PID 1935)
 ...
 2012-01-18 12:54:52.628 INFO  [b10-boss.boss] BIND10_SEND_SIGTERM sending
 SIGTERM to msgq (PID 1778)
 ...
 2012-01-18 12:54:52.733 INFO  [b10-boss.boss] BIND10_SEND_SIGKILL sending
 SIGKILL to cfgmgr (PID 1671)
 2012-01-18 12:54:52.792 INFO  [b10-boss.boss] BIND10_SEND_SIGKILL sending
 SIGKILL to b10-cmdctl (PID 1935)
 2012-01-18 12:54:52.793 INFO  [b10-boss.boss] BIND10_SEND_SIGKILL sending
 SIGKILL to msgq (PID 1778)
 2012-01-18 12:54:52.903 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 1778 of msgq ended with status 9
 2012-01-18 12:54:52.903 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 1935 of b10-cmdctl ended with status 9
 2012-01-18 12:54:52.903 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 1671 of cfgmgr ended with status 9

 }}}

 Why try to SIGKILL so fast?

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