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

Closed (moved)
(moved)
Open
Created Oct 22, 2012 by cypherpunks@cypherpunks

Tor fails to build circuits hours after daemon initialization (12+ hours)

Upgraded from Tor 0.2.2.36 to 0.2.3.22-rc. I'm observing an issue with Tor 0.2.3.22-rc. After around 12+ hours of uptime for a tor system daemon, tor fails to build circuits even though relays and exit nodes are still online. Tor does not recover on its own, the process must be stopped and restarted. Restarting the daemon "/etc/init.d/tor restart" results in normal behavior and tor starts to build circuits without a problem.

I've attached sanitized log files. The first log shows Tor activity over a two day period. The second log shows output from Tor after restart with "/etc/init.d/tor restart" It's also interesting to note that Tor does not recognize "Excludenodes {uk}"

Without including a copy of torrc, I think it is relevant to mention some additional parameters. Hopefully these aren't the cause of the problem, but it's possible they might interfere in some way.

Client 1 ExcludeNodes {uk}, {us} ExcludeExitNodes {uk}, {us} StrictNodes 1

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