[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #2825 [Torctl]: TorCtl 104 In _loop

#2825: TorCtl 104 In _loop
--------------------+-------------------------------------------------------
 Reporter:  atagar  |          Owner:     
     Type:  defect  |         Status:  new
 Priority:  minor   |      Milestone:     
Component:  Torctl  |        Version:     
 Keywords:          |         Parent:     
   Points:          |   Actualpoints:     
--------------------+-------------------------------------------------------
 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/TorCtl.py", line 690, in _loop
   isEvent, reply = self._read_reply()
 File "/home/atagar/Desktop/arm/src/TorCtl/TorCtl.py", line 836, in
 _read_reply
   line = self._s.readline()
 File "/home/atagar/Desktop/arm/src/TorCtl/TorUtil.py", 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".

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2825>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs