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
  • #9776

Closed (moved)
(moved)
Open
Created Sep 19, 2013 by Karsten Loesing@karsten

Long-running tor client doesn't build new circuits anymore

I'm running three tor 0.2.4.17-rc clients on ferrinii for Torperf, and one of them stopped building new circuits a while ago:

Sep 19 08:28:42.000 [notice] We'd like to launch a circuit to handle a connection, but we already have 33 general-purpose client circuits pending. Waiting until some finish. [1 similar message(s) suppressed in last 600 seconds]

The process is still running and I can debug it (though I should kill and restart it at some point to make Torperf work again). I sent it -USR1 and -USR2 signals to dump stats and switch to debug log level. I'm attaching the logs since last restarting it.

Here's the torrc:

DataDirectory .
SocksPort 9021
UseEntryGuards 0
RunAsDaemon 1
Log notice file log
ControlPort 10021
CookieAuthentication 1
PidFile tor.pid

Roger suspects it has to do with 0.2.4.x using guards as directory guards and this tor not using guards.

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