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

Closed
Open
Created Sep 19, 2013 by cypherpunks@cypherpunks

Stem configs resetting to default

After some time, Tor receives a HUP signal (during a long period without any user interaction) and any configuration changes made in Stem are replaced with whatever is in the torrc file. Specifically, this change occurs at the precise moment that the tor log is rotated. Stem maintains authentication and can still communicate with tor...

My concern is with the purpose of Tor's HUP signal and the loss of any configuration made in Stem...

Example log tail: ..... Sep 1 01:25:57.000 [notice] new bridge descriptor 'XXXXXX' (fresh): $0000000000000000000000000000000000000000~XXXXXX at 1.23.4.5 Sep 1 01:39:04.000 [notice] Received reload signal (hup). Reloading config and resetting internal state. Sep 1 01:39:04.000 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Sep 1 01:39:04.000 [notice] Read configuration file "/etc/tor/torrc".

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