Opened 9 years ago

Closed 9 years ago

#2825 closed defect (duplicate)

TorCtl 104 In _loop

Reported by: atagar Owned by: mikeperry
Priority: Low Milestone:
Component: Torctl Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points: 2
Reviewer: Sponsor:


Hi Mike. While experimenting with HS configurations I started getting the following stacktrace when Tor was shut down:

Traceback (most recent call last):
File "/home/atagar/Desktop/arm/src/TorCtl/", line 690, in _loop

isEvent, reply = self._read_reply()

File "/home/atagar/Desktop/arm/src/TorCtl/", line 836, in _read_reply

line = self._s.readline()

File "/home/atagar/Desktop/arm/src/TorCtl/", line 203, in readline

s = self._s.recv(128)

error: [Errno 104] Connection reset by peer

Unfortunately when I tried to dig in more I stopped being able to repro so this looks like some transient edge case. Hopefully this'll be enough to add a little extra paranoia for the exception handling but if not feel free to close as "can't repro".

Child Tickets

Change History (3)

comment:1 Changed 9 years ago by atagar

Owner: set to mikeperry
Status: newassigned

comment:2 Changed 9 years ago by mikeperry

Points: 2

comment:3 Changed 9 years ago by atagar

Resolution: duplicate
Status: assignedclosed

Socket 104 errors are being addressed in the fix for:


Note: See TracTickets for help on using tickets.