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

Closed (moved)
Open
Opened Jun 04, 2017 by s7r@s7r🏁

Bridge oftenly reports Failed to find node for hop 0 of our path. Discarding this circuit.

I have just setup an obfs4 bridge on 0.3.1.2-alpha-dev (git-1763aa058b08a1c5) on FreeBSD. I am using it as a client from another computer and it works well, except I see this warn in the log files of the bridge relay instance:

Jun 03 21:54:41.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 21:58:08.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 22:01:30.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 22:04:37.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 22:07:45.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 22:11:27.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:03:04.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:06:14.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:09:49.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:13:19.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:16:08.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:19:41.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:23:48.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:27:13.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:30:52.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:34:55.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:38:13.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:41:54.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:45:18.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:48:39.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:52:21.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:55:56.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.

There are a lot of similar messages, no sense to provide all of them since they're all the same.

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