BIND 10 #1672: b10-resolver crashing with status 11
BIND 10 Development
do-not-reply at isc.org
Mon Feb 13 21:43:01 UTC 2012
#1672: b10-resolver crashing with status 11
-------------------------------------+-------------------------------------
Reporter: | Owner:
Jeffry A. Spain | Status: new
Type: | Milestone: New Tasks
defect | Resolution:
Priority: major | Sensitive: 0
Component: | Sub-Project: DNS
resolver | Estimated Difficulty: 0
Keywords: | Total Hours: 0
Defect Severity: High |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jreed):
I created a ticket for this report. http://bind10.isc.org/ticket/1672
I assume exit status 11 is EAGAIN or EWOULDBLOCK on this Ubuntu Linux
system.
Note it may be related to that last log message which is documented:
http://bind10.isc.org/docs/bind10-messages.html#BIND10_START_AS_NON_ROOT_RESOLVER
The resolver is being started or restarted without root privileges.
If the module needs these privileges, it may have problems starting.
Note that this issue should be resolved by the pending 'socket-creator'
process; once that has been implemented, modules should not need root
privileges anymore. See tickets #800 and #801 for more information.
But #801 and #802 are closed.
--
Ticket URL: <https://bind10.isc.org/ticket/1672#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list