BIND 10 #432: b10-recurse failure to start with no error message

[BIND 10 Development]

#432: b10-recurse failure to start with no error message
-------------------------------+--------------------------------------------
      Reporter:  jreed         |        Owner:  jreed    
          Type:  defect        |       Status:  reviewing
      Priority:  major         |    Milestone:           
     Component:  Unclassified  |   Resolution:           
      Keywords:                |    Sensitive:  0        
Estimatedhours:  0.0           |        Hours:  0        
      Billable:  1             |   Totalhours:  0        
      Internal:  0             |  
-------------------------------+--------------------------------------------
Changes (by smann):

  * owner:  smann => jreed
  * status:  accepted => reviewing


Comment:

 This ticket reports the fact that if you try to start b10-recurse
 after an instance is already running, it silently terminates. If,
 however, you execute "b10-recurse -v", it tells you why it fails:

 $ /usr/local/libexec/bind10-devel/b10-recurse -v
 [b10-recurse] Command line: /usr/local/libexec/bind10-devel/b10-recurse -v
 [b10-recurse] Server created.
 [b10-recurse] Query shutdown
 [b10-recurse] Query setup
 [b10-recurse] IOService created.
 [b10-recurse] Configuration session channel created.
 [b10-recurse] New config comes: { "forward_addresses": [ { "address":
 "127.0.0.1", "port": 5302 } ], "listen_on": [ { "address": "172.17.0.6",
 "port": 53 }, { "address": "127.0.0.1", "port": 53 } ] }
 [b10-recurse] Setting listen addresses:
 [b10-recurse]  172.17.0.6:53
 [b10-recurse]  127.0.0.1:53
 [b10-recurse] Initialize TCP server at 172.17.0.6:53
 [b10-recurse] Unable to set new address: Failed to initialize network
 servers: Address already in use
 [b10-recurse] Server failed: std::exception
 [b10-recurse] Query shutdown
 [b10-recurse] Deleting the Recursor
 $

 this is expected.


 It turns out that other modules, like b10-auth, use cout/cerr so that
 these sorts of messages always get printed out.

 I think that the proper solution is to wait for the logging module
 described at http://bind10.isc.org/wiki/Logging.

 However, if it is important to make a change for this now, either dlog can
 be replaced with cout/cerr for certain messages or dlog could be changed
 to take an additional argument.

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