BIND 10 #1490: redundant logging with SRVCOMM_ADDRESS_FAIL and AUTH_CONFIG_UPDATE_FAIL and missing example

[BIND 10 Development]

#1490: redundant logging with SRVCOMM_ADDRESS_FAIL and AUTH_CONFIG_UPDATE_FAIL and
missing example
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 This ticket has multiple problems, all related. If I need more tickets,
 please let me know.

 This is related to #1419 but in this case I already had configuration in
 place so not using bindctl.

 I loaded a configuration that listed an IPv6 address that no longer
 existed on the interface. This resulted in:

 {{{

 2011-12-07 14:26:38.q ERROR [b10-auth.server_common] SRVCOMM_ADDRESS_FAIL
 failed to listen on addresses (Failed to initialize network servers: Can't
 assign requested address)
 2011-12-07 14:26:38.q ERROR [b10-auth.auth] AUTH_CONFIG_UPDATE_FAIL update
 of configuration failed: Server configuration failed: Failed to initialize
 network servers: Can't assign requested address

 }}}

 (Ignore the "q" in timestamp due to out of date log4cplus.)

 1) Why log twice?

 2) Please have it list the address(es) that has the problem. In my case,
 it was working with IPv4 and so I was initially confused.

 3) Why AUTH_CONFIG_UPDATE_FAIL -- this is not an attempt to "update the
 configuration". This configuration has been in place for over a month.
 Also the description for the AUTH_CONFIG_UPDATE_FAIL in the message file
 does not make sense: "At attempt to update the configuration the server
 with information from the configuration database has failed, the reason
 being given in the message."  I think it is missing some words or has
 wrong grammar.

 In addition I had a configuration with both IPv6 and IPv4 addresses that
 weren't configured on any interface:

 {{{

 2011-12-07 14:48:53.q DEBUG [b10-resolver.server_common]
 SRVCOMM_SET_LISTEN setting addresses to listen to
 2011-12-07 14:48:53.q DEBUG [b10-resolver.server_common]
 SRVCOMM_ADDRESS_VALUE address to set: 2001:4f8:3:d::95#53
 2011-12-07 14:48:53.q DEBUG [b10-resolver.server_common]
 SRVCOMM_ADDRESS_VALUE address to set: 149.20.48.80#53
 2011-12-07 14:48:53.q DEBUG [b10-resolver.server_common]
 SRVCOMM_ADDRESS_VALUE address to set: ::1#53
 2011-12-07 14:48:53.q DEBUG [b10-resolver.server_common]
 SRVCOMM_ADDRESS_VALUE address to set: 127.0.0.1#53
 2011-12-07 14:48:53.q ERROR [b10-resolver.server_common]
 SRVCOMM_ADDRESS_FAIL failed to listen on addresses (Failed to initialize
 network servers: Can't assign requested address)
 2011-12-07 14:48:53.q ERROR [b10-resolver.resolver] RESOLVER_CONFIG_ERROR
 error in configuration: Failed to initialize network servers: Can't assign
 requested address

 }}}

 This doesn't tell me which ones failed.

 And notice the SRVCOMM_SET_LISTEN line is incomplete or wrong grammar.
 Listen "on"?

 And why does the auth server have one log message that is quite different
 from the resolver's message?

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