#32975: Tor Socks unresponsive behaviour after 24-36 hours of runtime
--------------------------+------------------------------
Reporter: ntrn | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Core Tor/Tor | Version: Tor: 0.4.2.5
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------+------------------------------
Comment (by arma):
Can you point us to which relay this is?
What are you doing to decide that the socksport is unresponsive? Or is it
something else, since you say 'socks proxy' not socksport?
The "No buffer space available" error seems weird and like a good hint:
maybe the vps is artificially constrained in some resource like sockets or
kernel buffers. I'd check 'dmesg' too.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32975#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
