BIND 10 #2248: FATAL [b10-auth.auth] AUTH_SERVER_FAILED logged twice
BIND 10 Development
do-not-reply at isc.org
Tue Sep 18 11:46:55 UTC 2012
#2248: FATAL [b10-auth.auth] AUTH_SERVER_FAILED logged twice
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: | Status: closed
defect | Milestone: New Tasks
Priority: | Resolution: duplicate
medium | Sensitive: 0
Component: | Sub-Project: DNS
Unclassified | Estimated Difficulty: 0
Keywords: | Total Hours: 0
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by jreed):
* status: new => closed
* resolution: => duplicate
Comment:
It is acting like two auth servers are being ran:
{{{
2012-09-03 16:03:18.771 DEBUG [b10-auth.datasrc] DATASRC_SQLITE_NEWCONN
SQLite3Database is being initialized
2012-09-03 16:03:18.771 DEBUG [b10-auth.datasrc] DATASRC_SQLITE_CONNOPEN
Opening sqlite database file '/opt/bind10/var/bind10-devel/zone.sqlite3'
2012-09-03 16:03:18.771 DEBUG [b10-auth.datasrc] DATASRC_SQLITE_NEWCONN
SQLite3Database is being initialized
2012-09-03 16:03:18.771 DEBUG [b10-auth.datasrc] DATASRC_SQLITE_CONNOPEN
Opening sqlite database file '/opt/bind10/var/bind10-devel/zone.sqlite3'
...
2012-09-03 16:03:18.875 DEBUG [b10-auth.cc] CC_DISCONNECT disconnecting
from
message queue daemon
2012-09-03 16:03:18.875 DEBUG [b10-auth.cc] CC_DISCONNECT disconnecting
from
message queue daemon
}}}
(This is from an off-list email sent to me by the original reporter.)
Now I see the second component:
{{{
2012-09-03 16:03:18.876 DEBUG [b10-boss.boss] BIND10_CONFIGURATOR_BUILD
building plan '{'b10-stats': ({'kind': 'dispensable', 'address': 'Stats'},
<isc.bind10.component.Component object at 0x7fa609083590>), 'cfgmgr':
({'kind': 'core', 'special': 'cfgmgr', 'priority': 198},
<isc.bind10.special_component.CfgMgr object at 0x7fa609b0d2d0>),
'b10-zonemgr': ({'kind': 'needed', 'priority': 10},
<isc.bind10.component.Component object at 0x7fa6090839d0>), 'b10-xfrin':
({'kind': 'needed', 'priority': 10}, <isc.bind10.component.Component
object
at 0x7fa609083450>), 'b10-cmdctl': ({'kind': 'needed', 'special':
'cmdctl'},
<isc.bind10.special_component.CmdCtl object at 0x7fa60906a790>),
'sockcreator': ({'kind': 'core', 'special': 'sockcreator', 'priority':
200},
<isc.bind10.special_component.SockCreator object at 0x7fa609b0d350>),
'msgq': ({'kind': 'core', 'special': 'msgq', 'priority': 199},
<isc.bind10.special_component.Msgq object at 0x7fa609b0d310>),
'b10-auth-0':
({'kind': 'needed', 'special': 'auth', 'priority': 10},
<isc.bind10.special_component.Auth object at 0x7fa609083a10>),
'b10-auth-1':
({'kind': 'needed', 'special': 'auth', 'priority': 10},
<isc.bind10.special_component.Auth object at 0x7fa609083a50>)}' -> '{}'
}}}
So my real problem was much of the logging was just "b10-auth" and no
indication it was b10-auth-0 versus b10-auth-1.
This is a duplicate of #2177.
--
Ticket URL: <http://bind10.isc.org/ticket/2248#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list