Opened 8 years ago

Closed 6 years ago

#1874 closed defect (wontfix)

xfrout traceback EOF read where not expected

Reported by: jreed Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: Unclassified Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Medium
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 6 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


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/", 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
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
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.


Change History (4)

comment:1 Changed 8 years ago by jinmei

I suspect we cannot solve this unless we have a reliably reproduceable scenario.
It might also be related to the seeming kernel issue that caused the setsockopt failure
in that the failure mode seems very odd.

comment:2 Changed 8 years ago by shane

  • Defect Severity changed from N/A to Medium
  • Milestone New Tasks deleted

It actually seems like the Python interpreter had an error loading the modules needed by xfrout. Can this be reproduced, or has it been seen again?

comment:3 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:4 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check

Closing ticket.

Note: See TracTickets for help on using tickets.