[tor-bugs] #32975 [Core Tor/Tor]: Tor Socks unresponsive behaviour after 24-36 hours of runtime
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Jan 16 12:13:57 UTC 2020
#32975: Tor Socks unresponsive behaviour after 24-36 hours of runtime
--------------------------+------------------------------
Reporter: ntrn | Owner: (none)
Type: defect | Status: new
Priority: Medium | Component: Core Tor/Tor
Version: Tor: 0.4.2.5 | Severity: Normal
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------+------------------------------
__'''Error description:'''__
After around 1 or 1.5 days the tor socks proxy is getting unresponsive.
There is actually no error message from tor itself. Only nyx is claiming
to not have available buffer (error 105) and does not start any more.
__'''Error message: '''__
`nyx -c .nyx/config -i 9951`
`Unable to connect to 127.0.0.1:9951: [Errno 105] No buffer space
available`
__'''Workaround:'''__
I could solve the problem by deleting the ~/.tor folder and restarting
tor.
__'''Environment:'''__
* 2 CPU VPS with 4GB RAM
* Tor version 0.4.2.5 build and installed from source[[BR]](also seen
this behaviour on CentOS 7 repo package of tor v0.3.5.8)
* CentOS 7[[BR]](Linux version 3.10.0-042stab139.1 (root at kbuild-
rh6-x64.eng.sw.ru) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) )
!#1 SMP Tue Jun 18 12:51:14 MSK 2019)
* non-exit relay
* controle port blocked by iptables for outside connection
* ssh port blocked by iptables for outside connection
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32975>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list