Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #10449

Closed (moved)
Open
Opened Dec 20, 2013 by Roger Dingledine@arma

Tor launcher shuts down poorly when its Tor is a relay

Edit your TBB's torrc file to include "ORPort 9001". Start TBB, let it bootstrap and produce a browser window.

Then close Tor Browser. Your stdout will say:

Dec 20 01:30:01.000 [notice] Owning controller connection has closed -- shutting down.
Dec 20 01:30:01.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now.

and Tor Browser Bundle will exit:

Tor Browser exited cleanly.

Then thirty seconds later, we get

Dec 20 01:30:31.000 [notice] Clean shutdown finished. Exiting.

If you start your TBB again during this 30 second period, the old Tor process is still going, so your new Tor fails to start and things go bad.

What's going on here is due to Tor's ShutdownWaitLength default of 30 seconds.

Vidalia once solved this by popping up a window "you are a relay, do you want to close immediately or wait and close nicely"?

Maybe another answer is that Tor should close immediately, even if it's a relay, if it's closing because "Owning controller connection has closed".

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.5.x-final
Milestone
Tor: 0.2.5.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#10449