Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #32975

Closed (moved)
(moved)
Open
Created Jan 16, 2020 by Trac@tracbot

Tor Socks unresponsive behaviour after 24-36 hours of runtime

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 (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@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

Trac:
Username: ntrn

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking