BIND 10 #3021: bad configuration caused cc timeout and tracebacks

BIND 10 Development do-not-reply at isc.org
Mon Jul 1 13:58:48 UTC 2013 

#3021: bad configuration caused cc timeout and tracebacks
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  New Tasks
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  Unclassified                       |  Estimated Difficulty:  0
               CVSS Scoring:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 I had a typo in a configuration and it resulted in the following:

 {{{
 DEBUG [b10-cfgmgr.pycc]: PYCC_LNAME_RECEIVED received local name:
 51d186bf_2 at bind10-testing1.lab.isc.org
 INFO [b10-cfgmgr.cfgmgr]: CFGMGR_CONFIG_FILE Configuration manager
 starting with configuration file:
 /home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/var/bind10/b10-config.db
 FATAL [b10-cfgmgr.cfgmgr]: CFGMGR_DATA_READ_ERROR error reading
 configuration database from disk: Configuration file out of date or
 corrupt, please update or remove
 /home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/var/bind10/b10-config.db
 Traceback (most recent call last):
   File
 "/home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/lib/python3.1
 /site-packages/isc/cc/session.py", line 223, in _receive_full_buffer
     self._receive_len_data()
   File
 "/home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/lib/python3.1
 /site-packages/isc/cc/session.py", line 183, in _receive_len_data
     new_data = self._receive_bytes(self._recv_len_size)
   File
 "/home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/lib/python3.1
 /site-packages/isc/cc/session.py", line 169, in _receive_bytes
     data = self._socket.recv(size)
 socket.timeout: timed out

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File
 "/home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/lib/python3.1
 /site-packages/isc/config/ccsession.py", line 371, in
 _add_remote_config_internal
     answer, _ = self._session.group_recvmsg(False, seq)
   File
 "/home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/lib/python3.1
 /site-packages/isc/cc/session.py", line 306, in group_recvmsg
     env, msg  = self.recvmsg(nonblock, seq)
   File
 "/home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/lib/python3.1
 /site-packages/isc/cc/session.py", line 139, in recvmsg
     data = self._receive_full_buffer(nonblock)
   File
 "/home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/lib/python3.1
 /site-packages/isc/cc/session.py", line 238, in _receive_full_buffer
     raise SessionTimeout("recv() on cc session timed out")
 isc.cc.session.SessionTimeout: recv() on cc session timed out

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File
 "/home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/libexec/bind10/b10-msgq",
 line 863, in <module>
     msgq.socket_file)
   File
 "/home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/lib/python3.1
 /site-packages/isc/config/ccsession.py", line 225, in __init__
     default_logconfig_handler)
   File
 "/home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/lib/python3.1
 /site-packages/isc/config/ccsession.py", line 447, in add_remote_config
     self._add_remote_config_internal(module_spec, config_update_callback)
   File
 "/home/jreed/dnsbench/work/bind10-bind10-1.1.0-release/20130701102040/install/lib/python3.1
 /site-packages/isc/config/ccsession.py", line 375, in
 _add_remote_config_internal
     module_name)
 isc.config.ccsession.ModuleCCSessionError: No answer from ConfigManager
 when asking about Remote module Logging
 INFO [b10-init.init]: BIND10_STARTING starting BIND10: bind10 20110223
 (BIND 10 1.1.0)
 DEBUG [b10-init.init]: BIND10_CHECK_MSGQ_ALREADY_RUNNING checking if msgq
 is already running
 INFO [b10-init.init]: BIND10_CONFIGURATOR_START bind10 component
 configurator is starting up
 DEBUG [b10-init.init]: BIND10_CONFIGURATOR_BUILD building plan '{}' ->
 '{'sockcreator': {'priority': 200, 'kind': 'core', 'special':
 'sockcreator'}, 'msgq': {'priority': 199, 'kind': 'core', 'special':
 'msgq'}, 'cfgmgr': {'priority': 198, 'kind': 'core', 'special':
 'cfgmgr'}}'
 DEBUG [b10-init.init]: BIND10_CONFIGURATOR_RUN running plan of 3 tasks
 DEBUG [b10-init.init]: BIND10_CONFIGURATOR_TASK performing task start on
 Socket creator
 INFO [b10-init.init]: BIND10_COMPONENT_START component Socket creator is
 starting
 INFO [b10-init.init]: BIND10_SOCKCREATOR_INIT initializing socket creator
 parser
 DEBUG [b10-init.init]: BIND10_STARTED_PROCESS_PID started b10-sockcreator
 (PID 31516)
 DEBUG [b10-init.init]: BIND10_CONFIGURATOR_TASK performing task start on
 msgq
 INFO [b10-init.init]: BIND10_COMPONENT_START component msgq is starting
 INFO [b10-init.init]: BIND10_STARTING_PROCESS starting process b10-msgq
 DEBUG [b10-init.init]: BIND10_STARTED_PROCESS_PID started b10-msgq (PID
 31517)
 DEBUG [b10-init.pycc]: PYCC_LNAME_RECEIVED received local name:
 51d186bf_1 at bind10-testing1.lab.isc.org
 DEBUG [b10-init.init]: BIND10_CONFIGURATOR_TASK performing task start on
 cfgmgr
 INFO [b10-init.init]: BIND10_COMPONENT_START component cfgmgr is starting
 INFO [b10-init.init]: BIND10_STARTING_PROCESS starting process b10-cfgmgr
 DEBUG [b10-init.init]: BIND10_STARTED_PROCESS_PID started b10-cfgmgr (PID
 31519)
 DEBUG [b10-init.init]: BIND10_WAIT_CFGMGR waiting for configuration
 manager process to initialize
 DEBUG [b10-init.init]: BIND10_WAIT_CFGMGR waiting for configuration
 manager process to initialize
 DEBUG [b10-init.init]: BIND10_WAIT_CFGMGR waiting for configuration
 manager process to initialize
 DEBUG [b10-init.init]: BIND10_WAIT_CFGMGR waiting for configuration
 manager process to initialize
 DEBUG [b10-init.init]: BIND10_WAIT_CFGMGR waiting for configuration
 manager process to initialize
 DEBUG [b10-init.init]: BIND10_WAIT_CFGMGR waiting for configuration
 manager process to initialize
 ERROR [b10-init.init]: BIND10_COMPONENT_START_EXCEPTION component cfgmgr
 failed to start: Read of 0 bytes: connection closed
 ERROR [b10-init.init]: BIND10_COMPONENT_FAILED component cfgmgr (pid None)
 failed: unknown condition
 FATAL [b10-init.init]: BIND10_COMPONENT_UNSATISFIED component cfgmgr is
 required to run and failed
 ERROR [b10-init.init]: BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator
 plan interrupted, only 2 of 3 done
 INFO [b10-init.init]: BIND10_KILLING_ALL_PROCESSES killing all started
 processes
 INFO [b10-init.init]: BIND10_SEND_SIGKILL sending SIGKILL to Socket
 creator (PID 31516)
 WARN [b10-init.init]: BIND10_SOCKCREATOR_KILL killing the socket creator
 INFO [b10-init.init]: BIND10_SEND_SIGKILL sending SIGKILL to msgq (PID
 31517)
 FATAL [b10-init.init]: BIND10_STARTUP_ERROR error during startup: Unable
 to start b10-cfgmgr: Read of 0 bytes: connection closed
 }}}

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

More information about the bind10-tickets mailing list