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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed (moved)
Open
Opened Jul 01, 2019 by Trac@tracbot

Hidden service sometimes unable to create circuit

I have a dedicated server with a few onoin-services on it. One of the services has some traffic to it and this service can't be reached a few times every day, lasting 5-15 minutes.

While it's not available, the other onions is working just fine, it's just this particular .onion (which is the important one).

The service is not of the kind that would get ddos'ed or similar, however, it can have some heavy peaks in traffic, which at some degree correlate with the unavailability. However, no server process is under heavy stress and other services, including other hidden services, is functioning normally)

Server specs:
  {{{
OS: CentOS/RHEL 7
TOR: 0.3.5.8-1.el7

torrc config:

RunAsDaemon 1
DataDirectory /var/lib/tor
TransPort 9040
TransListenAddress 127.0.0.1
DNSPort 127.0.0.1:54
  }}}
A few lines from journalctl output, "xxx" is the onion that can't be reached:
  {{{
Tor[19172]: Giving up launching first hop of circuit to rendezvous point [scrubbed] for service xxx.
Tor[19172]: Giving up launching first hop of circuit to rendezvous point [scrubbed] for service xxx.
Tor[19172]: Giving up launching first hop of circuit to rendezvous point [scrubbed] for service xxx.
Tor[19172]: Giving up launching first hop of circuit to rendezvous point [scrubbed] for service xxx.
Tor[19172]: Giving up launching first hop of circuit to rendezvous point [scrubbed] for service xxx.
Tor[19172]: Couldn't relaunch rendezvous circuit to '[scrubbed]'.
Tor[19172]: Giving up launching first hop of circuit to rendezvous point [scrubbed] for service xxx.
Tor[19172]: Couldn't relaunch rendezvous circuit to '[scrubbed]'.
Tor[19172]: Giving up launching first hop of circuit to rendezvous point [scrubbed] for service xxx.
Tor[19172]: Giving up launching first hop of circuit to rendezvous point [scrubbed] for service xxx.
Tor[19172]: Giving up launching first hop of circuit to rendezvous point [scrubbed] for service xxx.
Tor[19172]: Giving up launching first hop of circuit to rendezvous point [scrubbed] for service xxx.
Tor[19172]: Giving up launching first hop of circuit to rendezvous point [scrubbed] for service xxx.
Tor[19172]: Giving up launching first hop of circuit to rendezvous point
  }}}

I have not found a similar issue in other tickets and it's very important that I can provide 100% uptime for this .onion.

Many thanks for your time reading this, highly appreciated.

Trac:
Username: dylanholand

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