BIND 10 #1937: FATAL [b10-auth.auth] AUTH_SERVER_FAILED server failed: Can't assign requested address

BIND 10 Development do-not-reply at isc.org
Mon Nov 26 13:25:49 UTC 2012


#1937: FATAL [b10-auth.auth] AUTH_SERVER_FAILED server failed: Can't assign
requested address
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:
                   Priority:  high   |  Sprint-20121204
                  Component:         |            Resolution:
  b10-auth                           |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  High   |  Estimated Difficulty:  8
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jelte):

 AUTH_SERVER_FAILED is logged whenever *any* exception bubbles all the way
 up to main(). At this point it can't do anything but exit, and because we
 do have that catchall there debugging it is hard (no core, no exception
 type, only its message).

 Normally whenever I start to debug anything with AUTH_SERVER_FAILED in the
 logs, I start out by removing this catch, then try to reproduce the issue.

 So is this ticket now only about the log message? If so I think the 'fix'
 is to simply remove the try/catch block, and the message (and let it crash
 with an escaped exception).

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


More information about the bind10-tickets mailing list