BIND 10 #2617: MSGQ_RECV_ERR errors on clean shutdown

[BIND 10 Development]

#2617: MSGQ_RECV_ERR errors on clean shutdown
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:
           Component:  msgq          |  Sprint-20130205
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  Core          |              Defect Severity:  Low
Estimated Difficulty:  Discuss (4?)  |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jreed):

 I tested once before I tried the patch (using same old code from
 2013-01-08 and received:
 {{{
 2013-01-30 09:02:23.535 ERROR [b10-msgq.msgq/17635] MSGQ_SEND_ERR Error
 while sending to socket 8: EPIPE
 2013-01-30 09:02:23.535 ERROR [b10-msgq.msgq/17635] MSGQ_SEND_ERR Error
 while sending to socket 7: EPIPE
 2013-01-30 09:02:23.536 ERROR [b10-msgq.msgq/17635] MSGQ_READ_UNKNOWN_FD
 Got read on strange socket 7
 2013-01-30 09:02:23.536 ERROR [b10-msgq.msgq/17635] MSGQ_READ_UNKNOWN_FD
 Got read on strange socket 8
 2013-01-30 09:02:23.536 ERROR [b10-msgq.msgq/17635] MSGQ_RECV_ERR Error
 reading from socket 11: EOF
 2013-01-30 09:02:23.537 ERROR [b10-msgq.msgq/17635] MSGQ_RECV_ERR Error
 reading from socket 12: EOF
 2013-01-30 09:02:23.537 ERROR [b10-msgq.msgq/17635] MSGQ_SEND_ERR Error
 while sending to socket 9: EPIPE
 2013-01-30 09:02:23.537 ERROR [b10-msgq.msgq/17635] MSGQ_READ_UNKNOWN_FD
 Got read on strange socket 9
 2013-01-30 09:02:23.538 ERROR [b10-msgq.msgq/17635] MSGQ_RECV_ERR Error
 reading from socket 13: EOF
 2013-01-30 09:02:23.538 ERROR [b10-msgq.msgq/17635] MSGQ_RECV_ERR Error
 reading from socket 14: EOF
 2013-01-30 09:02:23.538 ERROR [b10-msgq.msgq/17635] MSGQ_SEND_ERR Error
 while sending to socket 5: EPIPE
 2013-01-30 09:02:23.539 ERROR [b10-msgq.msgq/17635] MSGQ_RECV_ERR Error
 reading from socket 10: EOF
 }}}

 So I manually applied the change (note this is older code so patch didn't
 apply as is):

 {{{
 2013-01-30 09:08:43.171 INFO  [b10-boss.boss/17666] BIND10_COMPONENT_STOP
 component msgq is being stopped
 ...
 2013-01-30 09:08:43.173 ERROR [b10-msgq.msgq/17668] MSGQ_RECV_ERR Error
 reading from socket 11: EOF
 2013-01-30 09:08:43.173 ERROR [b10-msgq.msgq/17668] MSGQ_SEND_ERR Error
 while sending to socket 7: EPIPE
 2013-01-30 09:08:43.174 ERROR [b10-msgq.msgq/17668] MSGQ_READ_UNKNOWN_FD
 Got read on strange socket 7
 2013-01-30 09:08:43.174 ERROR [b10-msgq.msgq/17668] MSGQ_SEND_ERR Error
 while sending to socket 8: EPIPE
 2013-01-30 09:08:43.174 ERROR [b10-msgq.msgq/17668] MSGQ_READ_UNKNOWN_FD
 Got read on strange socket 8
 2013-01-30 09:08:43.175 ERROR [b10-msgq.msgq/17668] MSGQ_RECV_ERR Error
 reading from socket 12: EOF
 2013-01-30 09:08:43.175 ERROR [b10-msgq.msgq/17668] MSGQ_SEND_ERR Error
 while sending to socket 9: EPIPE
 2013-01-30 09:08:43.175 ERROR [b10-msgq.msgq/17668] MSGQ_READ_UNKNOWN_FD
 Got read on strange socket 9
 2013-01-30 09:08:43.175 ERROR [b10-msgq.msgq/17668] MSGQ_RECV_ERR Error
 reading from socket 13: EOF
 2013-01-30 09:08:43.176 ERROR [b10-msgq.msgq/17668] MSGQ_RECV_ERR Error
 reading from socket 14: EOF
 2013-01-30 09:08:43.176 ERROR [b10-msgq.msgq/17668] MSGQ_RECV_ERR Error
 reading from socket 10: EOF
 2013-01-30 09:08:43.176 ERROR [b10-msgq.msgq/17668] MSGQ_RECV_ERR Error
 reading from socket 5: [Errno 104] Connection reset by peer
 }}}

 This is on the CentOS 5.3 system bind10-testing1.lab.

 I am able to repeat everytime to get ERRORs on sending term signal to
 boss.

 I don't get the response from the patch everytime, but it is often like:
 {{{
 2013-01-30 09:18:44.010 ERROR [b10-msgq.msgq/17715] MSGQ_RECV_ERR Error
 reading from socket 5: [Errno 104] Connection reset by peer
 }}}

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