BIND 10 #1672: b10-resolver crashing with status 11
BIND 10 Development
do-not-reply at isc.org
Mon Feb 13 21:36:01 UTC 2012
#1672: b10-resolver crashing with status 11
-------------------------------------+-------------------------------------
Reporter: Jeffry A. | Owner:
Spain | Status: new
Type: defect | Milestone: New
Priority: major | Tasks
Component: resolver | Keywords:
Sensitive: 0 | Defect Severity: High
Sub-Project: DNS | Feature Depending on Ticket:
Estimated Difficulty: 0 | Add Hours to Ticket: 0
Total Hours: 0 | Internal?: 0
-------------------------------------+-------------------------------------
In my most recent build of bind10-devel-20110119, built according to
http://bind10.isc.org/wiki/SystemNotesUbuntuOneiric, b10-resolver is
failing after being given the query 'dig @localhost jaspain.net a', or any
query for that matter. Most of the installed prerequisites are newer
versions than those in the standard Ubuntu packages that I have used
previously with success, so I will try to figure out which one may be
causing the problem. Based on the following log excerpts, if you have a
sense of where the problem lies, would you please let me know. Thanks.
The following is log from bind10-users mailing list.
https://lists.isc.org/pipermail/bind10-users/2012-February/000216.html
Apparently any query caused resolver to crash.
{{{
2012-02-12 23:00:20.613 DEBUG [b10-resolver.resolver]
RESOLVER_QUERY_ACCEPTED query accepted: 'jaspain.net./A/IN' from
127.0.0.1#37965
2012-02-12 23:00:20.613 DEBUG [b10-resolver.resolver]
RESOLVER_NORMAL_QUERY processing normal query
2012-02-12 23:00:20.613 DEBUG [b10-resolver.reslib] RESLIB_RESOLVE asked
to resolve <jaspain.net. IN A> (resolve() instance 2)
2012-02-12 23:00:20.613 DEBUG [b10-resolver.reslib]
RESLIB_RECQ_CACHE_NO_FIND did not find <jaspain.net. IN A> in the cache,
starting RunningQuery (resolve() instance 2)
2012-02-12 23:00:20.613 DEBUG [b10-resolver.reslib] RESLIB_NSAS_LOOKUP
looking up nameserver for zone . in the NSAS
2012-02-12 23:00:20.613 DEBUG [b10-resolver.nsas] NSAS_SEARCH_ZONE_NS
searching NSAS for nameservers for zone .
2012-02-12 23:00:20.613 DEBUG [b10-resolver.reslib] RESLIB_RESOLVE asked
to resolve <. IN NS> (resolve() instance 1)
2012-02-12 23:00:20.613 DEBUG [b10-resolver.nsas] NSAS_FIND_NS_ADDRESS
asking resolver to obtain A and AAAA records for l.root-servers.net.
2012-02-12 23:00:20.613 DEBUG [b10-resolver.reslib] RESLIB_RESOLVE asked
to resolve <l.root-servers.net. IN A> (resolve() instance 1)
2012-02-12 23:00:20.613 DEBUG [b10-resolver.reslib] RESLIB_RESOLVE asked
to resolve <l.root-servers.net. IN AAAA> (resolve() instance 1)
2012-02-12 23:00:20.676 DEBUG [b10-resolver.nsas] NSAS_SEARCH_ZONE_NS
searching NSAS for nameservers for zone net.
2012-02-12 23:00:20.676 DEBUG [b10-resolver.reslib] RESLIB_RESOLVE asked
to resolve <net. IN NS> (resolve() instance 1)
2012-02-12 23:00:20.678 INFO [b10-boss.boss] BIND10_LOST_SOCKET_CONSUMER
consumer 20 of sockets disconnected, considering all its sockets closed
2012-02-12 23:00:20.678 INFO [b10-boss.boss] BIND10_PROCESS_ENDED process
1855 of b10-resolver ended with status 11
2012-02-12 23:00:20.678 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
component b10-resolver (pid 1855) failed with 11 exit status
2012-02-12 23:00:20.678 INFO [b10-boss.boss] BIND10_COMPONENT_START
component b10-resolver is starting
2012-02-12 23:00:20.678 WARN [b10-boss.boss]
BIND10_START_AS_NON_ROOT_RESOLVER starting b10-resolver as a user, not
root. This might fail.
2012-02-12 23:00:20.678 INFO [b10-boss.boss] BIND10_STARTING_PROCESS
starting process b10-resolver
2012-02-12 23:00:20.685 DEBUG [b10-boss.boss] BIND10_STARTED_PROCESS_PID
started b10-resolver (PID 1867)
}}}
--
Ticket URL: <https://bind10.isc.org/ticket/1672>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list