Opened 7 years ago

Closed 5 years ago

#2257 closed defect (wontfix)

noisy Boss shutdown -- socket.error: [Errno 104] Connection reset by peer

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: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 4 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


This is not master but latest snapshot. Brand new install, first time ran:

jreed@debian-64-4:~/src/bind10-devel-20120816$ echo Boss shutdown | bindctl

Exit from bindctl
jreed@debian-64-4:~/src/bind10-devel-20120816$ Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.1/", line 516, in _bootstrap_inner
  File "/usr/lib/python3.1/", line 469, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/libexec/bind10-devel/b10-cmdctl", line 351, in _handle_msg_from_msgq
  File "/usr/local/lib/python3/dist-packages/isc/config/", line 259, in check_command
    msg, env = self._session.group_recvmsg(nonblock)
  File "/usr/local/lib/python3/dist-packages/isc/cc/", line 275, in group_recvmsg
    env, msg  = self.recvmsg(nonblock, seq)
  File "/usr/local/lib/python3/dist-packages/isc/cc/", line 130, in recvmsg
    data = self._receive_full_buffer(nonblock)
  File "/usr/local/lib/python3/dist-packages/isc/cc/", line 239, in _receive_full_buffer
    raise se
  File "/usr/local/lib/python3/dist-packages/isc/cc/", line 212, in _receive_full_buffer
  File "/usr/local/lib/python3/dist-packages/isc/cc/", line 172, in _receive_len_data
    new_data = self._receive_bytes(self._recv_len_size)
  File "/usr/local/lib/python3/dist-packages/isc/cc/", line 158, in _receive_bytes
    data = self._socket.recv(size)
socket.error: [Errno 104] Connection reset by peer


Change History (5)

comment:1 Changed 7 years ago by jinmei

it's not clear exactly what is the problem, beyond that seeing a trace output due to
an uncaught exception isn't good in general.

comment:2 Changed 7 years ago by shane

Probably we should catch socket.error in, and handle it gracefully.

comment:3 Changed 7 years ago by shane

  • Milestone New Tasks deleted

comment:4 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:5 Changed 5 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.