[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #22489 [Core Tor/Tor]: Bridge oftenly reports Failed to find node for hop 0 of our path. Discarding this circuit.
#22489: Bridge oftenly reports Failed to find node for hop 0 of our path.
Discarding this circuit.
------------------------------------------------+--------------------------
Reporter: s7r | Owner: (none)
Type: defect | Status:
| needs_information
Priority: Medium | Milestone: Tor:
| 0.3.1.x-final
Component: Core Tor/Tor | Version: Tor:
| 0.3.1.2-alpha
Severity: Normal | Resolution:
Keywords: tor-client tor-bridge 030-backport | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
------------------------------------------------+--------------------------
Comment (by s7r):
On a more recent master `0.3.2.0-alpha-dev (git-209bfe715cc8c1c5)`:
{{{
Oct 04 11:17:27.000 [notice] Heartbeat: Tor's uptime is 32 days 11:59
hours, with 18 circuits open. I've sent 31.64 GB and received 31.90 GB.
Oct 04 11:17:27.000 [notice] Heartbeat: In the last 6 hours, I have seen
11 unique clients.
Oct 04 17:13:29.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 17:17:27.000 [notice] Heartbeat: Tor's uptime is 32 days 17:59
hours, with 14 circuits open. I've sent 31.78 GB and received 32.05 GB.
Oct 04 17:17:27.000 [notice] Heartbeat: In the last 6 hours, I have seen
11 unique clients.
Oct 04 17:20:24.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 17:28:25.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 17:34:29.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 17:38:36.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 17:45:23.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 17:50:04.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 17:54:06.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 17:58:18.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 18:03:28.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 18:07:39.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 18:11:44.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
Oct 04 20:12:42.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.
}}}
Again the client that uses this bridge to enter the Tor network didn't
notice anything when this occured nor logged anything strange, so can
confirm arma's comment:5 - we are looking at bridge's own circuits that it
was making for itself.
As I can see this also appears in #8185 - I'll keep an eye out for this
after upgrading to latest git master.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22489#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs