BIND 10 #1858: sockcreator doesn't die

[BIND 10 Development]

#1858: sockcreator doesn't die
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:         |             Milestone:  Next-Sprint-
  defect                             |  Proposed
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:  Boss   |           Sub-Project:  Core
  of BIND                            |  Estimated Difficulty:  0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 This is a log when this happened.

 {{{
 2012-03-27 23:12:11.780 INFO  [b10-boss.boss] BIND10_CONFIGURATOR_STOP
 bind10 component configurator is shutting down
 2012-03-27 23:12:11.782 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-auth-2 is being stopped
 2012-03-27 23:12:11.782 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-auth-2 to shut down
 2012-03-27 23:12:11.783 ERROR [b10-boss.boss]
 BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only 0
 of 11 done
 2012-03-27 23:12:12.800 INFO  [b10-boss.boss] BIND10_SEND_SIGTERM sending
 SIGTERM to Socket creator (PID 29154)
 2012-03-27 23:12:12.801 WARN  [b10-boss.boss] BIND10_SOCKCREATOR_KILL
 killing the socket creator
 ...
 2012-03-27 23:12:12.993 ERROR [b10-xfrout.xfrout]
 XFROUT_RECEIVE_FILE_DESCRIPTOR_ERROR error receiving the file descriptor
 for an XFR connection
 (lots of this)
 ...
 2012-03-27 23:12:19.347 INFO  [b10-boss.boss] BIND10_SEND_SIGKILL sending
 SIGKILL to Socket creator (PID 29154)
 (lots of this)
 ...
 2012-03-27 23:13:21.874 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 29154 of Socket creator ended with status 15
 2012-03-27 23:13:21.875 INFO  [b10-boss.boss] BIND10_SHUTDOWN_COMPLETE all
 processes ended, shutdown complete
 }}}

 In this case I killed the socket creator by hand.  I guess the log at
 23:13:21.874 was due to this manual operation.

 So, what apparently happened is Boss's shutdown message to the socket
 creator was somehow lost, and while the Boss tried to kill it
 forcefully (and of course unsuccessfully because it didn't have the
 permission), bot Boss and the creator kept alive.

 The lost message is itself an issue, but the subsequent behavior is
 obviously very bad (if I didn't notice it, it could effectively result
 in a busy loop).  At least Boss should give up sending a signal
 if it fails due to permission denied because it would never succeed by
 a retry.

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