BIND 10 #1874: xfrout traceback EOF read where not expected
BIND 10 Development
do-not-reply at isc.org
Wed Apr 4 14:56:25 UTC 2012
#1874: xfrout traceback EOF read where not expected
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: medium | Milestone: New
Component: Unclassified | Tasks
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
This is on OpenBSD. I started bind10 as non-root using no custom
configuration.
{{{
2012-04-04 14:46:24.649 INFO [b10-boss.boss] BIND10_COMPONENT_START
component b10-xfrout is starting
2012-04-04 14:46:24.743 INFO [b10-boss.boss] BIND10_STARTING_PROCESS
starting process b10-xfrout
...
2012-04-04 14:46:25.229 INFO [b10-boss.boss] BIND10_SOCKET_GET requesting
socket [::]:53 of type TCP from the creator
2012-04-04 14:46:25.229 ERROR [b10-boss.boss] BIND10_SOCKET_ERROR error on
bind call in the creator: 1/Operation not permitted
2012-04-04 14:46:25.231 ERROR [b10-auth.server_common]
SRVCOMM_ADDRESS_FAIL failed to listen on addresses ("Error creating socket
on bind")
2012-04-04 14:46:25.231 ERROR [b10-auth.auth] AUTH_CONFIG_LOAD_FAIL load
of configuration failed: Server configuration failed: "Error creating
socket on bind"
2012-04-04 14:46:25.233 INFO [b10-auth.auth] AUTH_SERVER_STARTED server
started
Traceback (most recent call last):
File
"/home/jreed/builder/work/BIND10/20120404131458-OpenBSD5-amd64/install/libexec/bind10-devel/b10-xfrout",
line 30, in <module>
from isc.notify import notify_out
2012-04-04 14:46:25.470 File
"/home/jreed/builder/work/BIND10/20120404131458-OpenBSD5-amd64/install/lib/python3.2
/site-packages/isc/notify/__init__.py", line 1, in <module>
from isc.notify.notify_out import *
INFOEOFError: EOF read where not expected
[2012-04-04 14:46:25.535b10-stats.stats2012-04-04 14:46:25.540]
STATS_STARTING startingINFO
[b10-boss.boss] BIND10_PROCESS_ENDED process 8258 of b10-xfrout ended
with status 256
2012-04-04 14:46:25.545 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
component b10-xfrout (pid 8258) failed: process exited normally with exit
status 256
DEBUG [b10-cmdctl.cmdctl] CMDCTL_STARTED cmdctl is listening for
connections on 127.0.0.1:8080
2012-04-04 14:46:25.614 DEBUG [b10-stats-httpd.stats-httpd]
STATHTTPD_STARTING_CC_SESSION starting cc session
2012-04-04 14:46:25.637 INFO [b10-stats-httpd.stats-httpd]
STATHTTPD_STARTED listening on 127.0.0.1#8000
2012-04-04 14:46:34.751 INFO [b10-boss.boss] BIND10_COMPONENT_START
component b10-xfrout is starting
2012-04-04 14:46:34.751 INFO [b10-boss.boss] BIND10_STARTING_PROCESS
starting process b10-xfrout
2012-04-04 14:46:35.068 INFO [b10-xfrout.xfrout] XFROUT_NEW_CONFIG Update
xfrout configuration
2012-04-04 14:46:35.069 INFO [b10-xfrout.xfrout] XFROUT_NEW_CONFIG_DONE
Update xfrout configuration done
}}}
First time xfrout failed, but it was restarted.
--
Ticket URL: <http://bind10.isc.org/ticket/1874>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list