Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #40185

Closed
Open
Created Nov 09, 2020 by toralf@toralf

relay with 0.4.5.1-alpha-dev (git-dd119b27) ignores -INT and -USR1

It happened here 2x in a row that a relay here could only be terminated (-HUP worked all the time for what it is worth). OS is a hardened Linux.

FWIW there are 2 relays running at the same hardware under a hardened Gentoo Linux. The one which is listing at default ports (80 and 443) behaves fine, the other (9001 and 9030 and being a FallbackDir too) however is affected by this issue. Update: It is independent from being a FallbackDir or not, with bc6c37b2 now the other relay refused to restart - and today -TERM was ignored too at 1 relay.

Nowadays a kill -HUP is ignored after an uptime of only few hours. I use this cronjob for now to keep both relays aware of signals

@hourly (/sbin/rc-service tor reload; /sbin/rc-service tor2 reload) 1>/dev/null
Edited Dec 18, 2020 by toralf
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking