BIND 10 #2880: b10-stats timeout on cc session

[BIND 10 Development]

#2880: b10-stats timeout on cc session
-------------------------------------+-------------------------------------
            Reporter:  shane         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  Unclassified  |  Tasks
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Which version of BIND 10 is it?  If it's 1.0.0, I'd tweak the
 following part of zonemgr.py
 {{{#!python
             except isc.cc.session.SessionTimeout:
                 pass        # for now we just ignore the failure
         except socket.error:
             logger.error(ZONEMGR_SEND_FAIL, module_name)
 }}}
 to
 {{{#!python
             except isc.cc.session.SessionTimeout:
                 logger.error(ZONEMGR_SEND_FAIL, module_name + ': timeout')
                 pass        # for now we just ignore the failure
         except socket.error:
             logger.error(ZONEMGR_SEND_FAIL, module_name)
 }}}
 and see if the new "timeout" message is logged.

 What I suspect is happening is that zonemgr somehow couldn't get a
 response to its refresh command from xfrin, and this timeout was
 propagated all the way through b10-auth to stats.

 I'd also try to reproduce it more easily with a script like the
 attached one.

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