BIND 10 #628: switching from auth or resolver is too noisy

[BIND 10 Development]

#628: switching from auth or resolver is too noisy
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:  jreed
                       Type:         |                Status:  assigned
  defect                             |             Milestone:
                   Priority:  minor  |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  0.0
            Defect Severity:  Low    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jreed):

 While the errors are gone. I think it is too verbose, too redundant. Here
 I reorder some of your logging:

 {{{
 2012-02-27 14:47:15.366 INFO  [b10-boss.boss]
 BIND10_CONFIGURATOR_RECONFIGURE reconfiguring running components
 }}}

 I don't think it is reconfiguring the running components. It is stopping
 or starting but not changing existing.

 {{{
 2012-02-27 14:47:15.367 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-xfrin is being stopped
 2012-02-27 14:47:15.367 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-xfrin to shut down
 2012-02-27 14:47:15.389 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 9272 of b10-xfrin ended with status 0
 }}}

 I think should only mention once at INFO. Others should be debug. Note
 that xfrin itself never logged anything about this.

 {{{
 2012-02-27 14:47:15.367 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-xfrout is being stopped
 2012-02-27 14:47:15.367 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-xfrout to shut down
 2012-02-27 14:47:15.368 INFO  [b10-xfrout.xfrout]
 XFROUT_RECEIVED_SHUTDOWN_COMMAND shutdown command received
 2012-02-27 14:47:15.394 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 9274 of b10-xfrout ended with status 0
 }}}

 Same comment: only log once to INFO and others to DEBUG. This one did have
 a log from xfrout too. Receiving a shutdown command seems like debug
 message, saying it does a shutdown seems like an INFO message.

 {{{
 2012-02-27 14:47:15.367 INFO  [b10-boss.boss] BIND10_COMPONENT_STOP
 component b10-auth is being stopped
 2012-02-27 14:47:15.367 INFO  [b10-boss.boss] BIND10_STOP_PROCESS asking
 b10-auth to shut down
 2012-02-27 14:47:15.382 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 9276 of b10-auth ended with status 0
 2012-02-27 14:47:15.384 INFO  [b10-boss.boss] BIND10_LOST_SOCKET_CONSUMER
 consumer 21 of sockets disconnected, considering all its sockets closed
 }}}

 Too much again. Change all this to debug. I think auth itself, if
 anything, should be the one show says it shutdown.

 {{{
 2012-02-27 14:47:15.368 INFO  [b10-boss.boss] BIND10_COMPONENT_START
 component b10-resolver is starting
 2012-02-27 14:47:15.368 INFO  [b10-boss.boss] BIND10_STARTING_PROCESS
 starting process b10-resolver
 2012-02-27 14:47:15.410 INFO  [b10-resolver.resolver] RESOLVER_STARTING
 starting resolver with command line 'b10-resolver'
 2012-02-27 14:47:15.420 INFO  [b10-resolver.resolver] RESOLVER_RECURSIVE
 running in recursive mode
 2012-02-27 14:47:15.420 WARN  [b10-resolver.resolver]
 RESOLVER_NO_ROOT_ADDRESS no root addresses available
 2012-02-27 14:47:15.421 INFO  [b10-resolver.resolver]
 RESOLVER_SET_QUERY_ACL query ACL is configured
 2012-02-27 14:47:15.421 INFO  [b10-boss.boss] BIND10_SOCKET_GET requesting
 socket [::1]:53 of type TCP from the creator
 2012-02-27 14:47:15.422 INFO  [b10-boss.boss] BIND10_SOCKET_CREATED
 successfully created socket 15
 2012-02-27 14:47:15.425 INFO  [b10-boss.boss] BIND10_SOCKET_GET requesting
 socket [::1]:53 of type UDP from the creator
 2012-02-27 14:47:15.425 INFO  [b10-boss.boss] BIND10_SOCKET_CREATED
 successfully created socket 19
 2012-02-27 14:47:15.427 INFO  [b10-boss.boss] BIND10_SOCKET_GET requesting
 socket [127.0.0.1]:53 of type TCP from the creator
 2012-02-27 14:47:15.428 INFO  [b10-boss.boss] BIND10_SOCKET_CREATED
 successfully created socket 20
 2012-02-27 14:47:15.430 INFO  [b10-boss.boss] BIND10_SOCKET_GET requesting
 socket [127.0.0.1]:53 of type UDP from the creator
 2012-02-27 14:47:15.430 INFO  [b10-boss.boss] BIND10_SOCKET_CREATED
 successfully created socket 21
 2012-02-27 14:47:15.431 INFO  [b10-resolver.resolver] RESOLVER_STARTED
 resolver started

 }}}

 I think I'd only keep the RESOLVER_STARTED as INFO, rest as DEBUG.

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