BIND 10 #1546: resolver not listening

BIND 10 Development do-not-reply at isc.org
Tue Jan 10 18:30:26 UTC 2012


#1546: resolver not listening
---------------------------------+-----------------------------------------
            Reporter:  jreed     |                        Owner:
                Type:  defect    |                       Status:  new
            Priority:  major     |                    Milestone:  New Tasks
           Component:  resolver  |                     Keywords:
           Sensitive:  0         |              Defect Severity:  High
         Sub-Project:  DNS       |  Feature Depending on Ticket:
Estimated Difficulty:  0         |          Add Hours to Ticket:  0
         Total Hours:  0         |                    Internal?:  0
---------------------------------+-----------------------------------------
 Following the guide, I did:

 {{{
 > config remove Boss/components b10-xfrout
 > config remove Boss/components b10-xfrin
 > config remove Boss/components b10-auth
 > config add Boss/components b10-resolver
 > config set Boss/components/b10-resolver/special resolver
 > config set Boss/components/b10-resolver/kind needed
 > config set Boss/components/b10-resolver/priority 10
 > config commit
 >
 }}}

 (no feedback there)

 The resolver is running:

 {{{
 > config show Resolver/listen_on
 Resolver/listen_on[0]/address   "::1"   string  (default)
 Resolver/listen_on[0]/port      53      integer (default)
 Resolver/listen_on[1]/address   "127.0.0.1"     string  (default)
 Resolver/listen_on[1]/port      53      integer (default)
 }}}

 But not listening.

 The default logging:

 {{{

 2012-01-10 12:08:07.339 INFO  [b10-boss.boss]
 BIND10_CONFIGURATOR_RECONFIGURE reconfiguring running components
 2012-01-10 12:08:07.340 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-xfrin is being stopped
 2012-01-10 12:08:07.340 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-xfrin to shut down
 2012-01-10 12:08:07.358 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-xfrout is being stopped
 2012-01-10 12:08:07.358 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-xfrout to shut down
 2012-01-10 12:08:07.359 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-auth is being stopped
 2012-01-10 12:08:07.359 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-autt configuration
 2012-01-10 12:05:05.508 INFO  [b10-xfrout.xfrout] XFROUT_NEW_CONFIG_DONE
 Update xfrout configuration done
 2012-01-10 12:05:05.636 INFO  [b10-stats.stats] STATS_STARTING starting
 2012-01-10 12:05:05.918 INFO  [b10-stats-httpd.stats-httpd]
 STATHTTPD_STARTED listening on 127.0.0.1#8000
 2012-01-10 12:05:08.854 INFO  [b10-boss.boss] BIND10_SOCKET_GET requesting
 socket [::]:53 of type TCP from the creator
 2012-01-10 12:05:08.874 INFO  [b10-boss.boss] BIND10_SOCKET_CREATED
 successfully created socket 19
 2012-01-10 12:05:08.894 INFO  [b10-boss.boss] BIND10_SOCKET_GET requesting
 socket [::]:53 of type UDP from the creator
 2012-01-10 12:05:08.896 INFO  [b10-boss.boss] BIND10_SOCKET_CREATED
 successfully created socket 21
 2012-01-10 12:05:08.903 INFO  [b10-boss.boss] BIND10_SOCKET_GET requesting
 socket [0.0.0.0]:53 of type TCP from the creator
 2012-01-10 12:05:08.903 INFO  [b10-boss.boss] BIND10_SOCKET_CREATED
 successfully created socket 22
 2012-01-10 12:05:08.907 INFO  [b10-boss.boss] BIND10_SOCKET_GET requesting
 socket [0.0.0.0]:53 of type UDP from the creator
 2012-01-10 12:05:08.907 INFO  [b10-boss.boss] BIND10_SOCKET_CREATED
 successfully created socket 23
 2012-01-10 12:05:08.917 INFO  [b10-auth.auth] AUTH_SERVER_STARTED server
 started
 2012-01-10 12:08:07.339 INFO  [b10-boss.boss]
 BIND10_CONFIGURATOR_RECONFIGURE reconfiguring running components
 2012-01-10 12:08:07.340 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-xfrin is being stopped
 2012-01-10 12:08:07.340 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-xfrin to shut down
 2012-01-10 12:08:07.358 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-xfrout is being stopped
 2012-01-10 12:08:07.358 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-xfrout to shut down
 2012-01-10 12:08:07.359 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-auth is being stopped
 2012-01-10 12:08:07.359 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-auth to shut down
 2012-01-10 12:08:07.360 INFO  [b10-boss.boss] BIND10_COMPONENT_START
 component b10-resolver is starting
 2012-01-10 12:08:07.360 INFO  [b10-boss.boss] BIND10_STARTING_PROCESS
 starting process b10-resolver
 2012-01-10 12:08:07.363 INFO  [b10-xfrout.xfrout]
 XFROUT_RECEIVED_SHUTDOWN_COMMAND shutdown command received
 2012-01-10 12:08:07.377 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 28511 of b10-xfrin ended with status 0
 2012-01-10 12:08:07.384 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 18900 of b10-auth ended with status 0
 2012-01-10 12:08:07.384 INFO  [b10-boss.boss] BIND10_LOST_SOCKET_CONSUMER
 consumer 20 of sockets disconnected, considering all its sockets closed
 2012-01-10 12:08:07.443 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 23139 of b10-xfrout ended with status 0
 2012-01-10 12:08:07.585 INFO  [b10-resolver.resolver] RESOLVER_STARTING
 starting resolver with command line 'b10-resolver'
 2012-01-10 12:08:07.613 INFO  [b10-resolver.resolver] RESOLVER_RECURSIVE
 running in recursive mode
 2012-01-10 12:08:07.613 WARN  [b10-resolver.resolver]
 RESOLVER_NO_ROOT_ADDRESS no root addresses available
 2012-01-10 12:08:07.614 INFO  [b10-resolver.resolver]
 RESOLVER_SET_QUERY_ACL query ACL is configured
 2012-01-10 12:08:07.616 INFO  [b10-boss.boss] BIND10_SOCKET_GET requesting
 socket [::1]:53 of type TCP from the creator
 2012-01-10 12:08:07.616 INFO  [b10-boss.boss] BIND10_SOCKET_CREATED
 successfully created socket 12
 2012-01-10 12:08:11.650 ERROR [b10-resolver.cc] CC_TIMEOUT timeout reading
 data from command channel
 2012-01-10 12:08:11.664 ERROR [b10-resolver.server_common]
 SRVCOMM_ADDRESS_FAIL failed to listen on addresses (Timeout while reading
 data from cc session)
 2012-01-10 12:08:11.665 ERROR [b10-resolver.resolver]
 RESOLVER_CONFIG_ERROR error in configuration: Timeout while reading data
 from cc session
 2012-01-10 12:08:11.665 INFO  [b10-resolver.resolver] RESOLVER_STARTED
 resolver started
 }}}

 I tried to restart:

 {{{
 > Resolver shutdown
 {
     "error": "Module 'Resolver' not responding"
 }
 }}}

 And logged:

 {{{
 2012-01-10 12:25:43.794 ERROR [b10-cmdctl.cmdctl] CMDCTL_COMMAND_ERROR
 error in command shutdown to module Resolver: Module 'Resolver' not
 responding
 }}}

 I stopped with Boss shutdown and restarted but resolver still failing:

 {{{
 2012-01-10 12:27:36.286 INFO  [b10-boss.boss] BIND10_SOCKET_GET requesting
 socket [::1]:53 of type TCP from the creator
 2012-01-10 12:27:36.287 INFO  [b10-boss.boss] BIND10_SOCKET_CREATED
 successfully created socket 17
 ...
 2012-01-10 12:27:40.373 ERROR [b10-resolver.cc] CC_TIMEOUT timeout reading
 data from command channel
 2012-01-10 12:27:40.387 ERROR [b10-resolver.server_common]
 SRVCOMM_ADDRESS_FAIL failed to listen on addresses (Timeout while reading
 data from cc session)
 2012-01-10 12:27:40.388 ERROR [b10-resolver.resolver]
 RESOLVER_CONFIG_ERROR error in configuration: Timeout while reading data
 from cc session

 }}}

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


More information about the bind10-tickets mailing list