Opened 4 days ago

Last modified 4 days ago

#32975 new defect

Tor Socks unresponsive behaviour after 24-36 hours of runtime

Reported by: ntrn Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version: Tor:
Severity: Normal Keywords:
Cc: 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 [Errno 105] No buffer space available


I could solve the problem by deleting the ~/.tor folder and restarting tor.


  • 2 CPU VPS with 4GB RAM
  • Tor version build and installed from source
    (also seen this behaviour on CentOS 7 repo package of tor v0.3.5.8)
  • CentOS 7
    (Linux version 3.10.0-042stab139.1 (root@…) (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

Child Tickets

Change History (1)

comment:1 Changed 4 days ago by ntrn

activated "ConstrainedSockets 1" in torrc.
Testing behaviour.

Note: See TracTickets for help on using tickets.