BIND 10 #2617: MSGQ_RECV_ERR errors on clean shutdown

BIND 10 Development do-not-reply at isc.org
Tue Jan 8 15:29:30 UTC 2013


#2617: MSGQ_RECV_ERR errors on clean shutdown
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  New Tasks
                   Priority:  low    |              Keywords:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  Core
               CVSS Scoring:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 I sent a SIGTERM to bind10. This resulted in three ERRORs:

 {{{
 2013-01-08 10:12:05.984 INFO  [b10-boss.boss/3373] BIND10_RECEIVED_SIGNAL
 received signal SIGTERM
 2013-01-08 10:12:05.984 INFO  [b10-boss.boss/3373] BIND10_SHUTDOWN
 stopping the server
 2013-01-08 10:12:05.985 INFO  [b10-boss.boss/3373]
 BIND10_CONFIGURATOR_STOP bind10 component configurator is shutting down
 2013-01-08 10:12:05.985 INFO  [b10-boss.boss/3373] BIND10_COMPONENT_STOP
 component b10-auth is being stopped
 2013-01-08 10:12:05.985 INFO  [b10-boss.boss/3373] BIND10_STOP_PROCESS
 asking b10-auth to shut down
 2013-01-08 10:12:05.986 INFO  [b10-boss.boss/3373] BIND10_COMPONENT_STOP
 component Socket creator is being stopped
 2013-01-08 10:12:05.986 INFO  [b10-boss.boss/3373]
 BIND10_SOCKCREATOR_TERMINATE terminating socket creator
 2013-01-08 10:12:05.986 INFO  [b10-boss.boss/3373] BIND10_COMPONENT_STOP
 component msgq is being stopped
 2013-01-08 10:12:05.986 INFO  [b10-boss.boss/3373] BIND10_COMPONENT_STOP
 component cfgmgr is being stopped
 2013-01-08 10:12:05.986 INFO  [b10-boss.boss/3373] BIND10_STOP_PROCESS
 asking cfgmgr to shut down
 2013-01-08 10:12:05.987 INFO  [b10-auth.auth/3377]
 AUTH_DATASRC_CLIENTS_BUILDER_STOPPED data source builder thread stopped
 2013-01-08 10:12:05.987 ERROR [b10-msgq.msgq/3375] MSGQ_RECV_ERR Error
 reading from socket 8: EOF
 2013-01-08 10:12:05.987 ERROR [b10-msgq.msgq/3375] MSGQ_RECV_ERR Error
 reading from socket 7: EOF
 2013-01-08 10:12:05.991 ERROR [b10-msgq.msgq/3375] MSGQ_RECV_ERR Error
 reading from socket 5: <class 'socket.error'>
 2013-01-08 10:12:06.986 INFO  [b10-boss.boss/3373] BIND10_PROCESS_ENDED
 process 3374 of Socket creator ended with status 0
 2013-01-08 10:12:06.986 INFO  [b10-boss.boss/3373] BIND10_PROCESS_ENDED
 process 3376 of cfgmgr ended with status 0
 2013-01-08 10:12:06.986 INFO  [b10-boss.boss/3373] BIND10_PROCESS_ENDED
 process 3377 of b10-auth ended with status 0
 2013-01-08 10:12:06.986 INFO  [b10-boss.boss/3373] BIND10_SEND_SIGTERM
 sending SIGTERM to msgq (PID 3375)
 2013-01-08 10:12:07.086 INFO  [b10-boss.boss/3373] BIND10_PROCESS_ENDED
 process 3375 of msgq ended with status 0
 2013-01-08 10:12:07.086 INFO  [b10-boss.boss/3373]
 BIND10_SHUTDOWN_COMPLETE all processes ended, shutdown complete
 }}}

 I also received the errors when doing a "Boss shutdown":

 {{{
 2013-01-08 10:25:41.879 ERROR [b10-msgq.msgq/3704] MSGQ_RECV_ERR Error
 reading from socket 5: <class 'socket.error'>
 2013-01-08 10:25:41.883 ERROR [b10-msgq.msgq/3704] MSGQ_RECV_ERR Error
 reading from socket 7: EOF
 2013-01-08 10:25:41.885 ERROR [b10-msgq.msgq/3704] MSGQ_RECV_ERR Error
 reading from socket 8: EOF
 2013-01-08 10:25:41.885 ERROR [b10-msgq.msgq/3704] MSGQ_RECV_ERR Error
 reading from socket 9: EOF
 }}}

 The server should not have ERRORs during a clean shutdown. This will
 prompt an administrator to research if something is wrong or corrupted.

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


More information about the bind10-tickets mailing list