[tor-bugs] #30520 [Core Tor/Tor]: Onion Service (v2) hosting Tor instance reporting under high load: Failed to find node for hop #1 of our path. Discarding this circuit.

[Tor Bug Tracker & Wiki]

#30520: Onion Service (v2) hosting Tor instance reporting under high load: Failed
to find node for hop #1 of our path. Discarding this circuit.
--------------------------+------------------------------------
 Reporter:  s7r           |          Owner:  (none)
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:
Component:  Core Tor/Tor  |        Version:  Tor: 0.4.0.1-alpha
 Severity:  Normal        |     Resolution:
 Keywords:  tor-hs        |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------
Description changed by s7r:

Old description:

> An onion hosting Tor instance is reporting strange stuff for the last 3
> days. The server was attacked (DOS / SYN Flood last days), so maybe this
> could have triggered some network connection changes but the connection
> remained active / online. The torrc is very simple:
> {{{
> SocksPort 127.0.0.1:9050
> ControlPort 0
> HiddenServiceDir /var/lib/tor/tor_hs
> HiddenServiceVersion 2
> HiddenServicePort <port> 127.0.0.1:<port>
> }}}
>

> #1
> {{{
> May 12 11:16:08.000 [notice] Your network connection speed appears to
> have changed. Resetting timeout to 60s after 18 timeouts and 362
> buildtimes.
> May 12 22:20:32.000 [notice] No circuits are opened. Relaxed timeout for
> circuit 398807 (a Hidden service: Connecting to rendezvous point 4-hop
> circuit in state doing handshakes with channel state open) to 106324ms.
> However, it appears the circuit has timed out anyway. [16 similar
> message(s) suppressed in last 3600 seconds]
> }}}
>
> #2
> {{{
> May 13 11:05:36.000 [notice] No circuits are opened. Relaxed timeout for
> circuit 399137 (a General-purpose client 3-hop circuit in state waiting
> to see how other guards perform with channel state open) to 106324ms.
> However, it appears the circuit has timed out anyway. [27 similar
> message(s) suppressed in last 3600 seconds]
> }}}
>
> #3
> {{{
> May 14 21:27:36.000 [warn] Failed to find node for hop #1 of our path.
> Discarding this circuit.
> May 14 21:27:36.000 [notice] Our circuit 0 (id: 400112) died due to an
> invalid selected path, purpose General-purpose client. This may be a
> torrc configuration issue, or a bug. [8 similar message(s) suppressed in
> last 3600 seconds]
> }}}
>
> I wish I could reproduce the last one. Could this be a bug that occurs
> when our primary #1 Guard is in consensus but not reachable just for a
> certain machine / IP?

New description:

 An onion hosting Tor instance is reporting strange stuff for the last 3
 days. The server was attacked (DOS / SYN Flood last days), so maybe this
 could have triggered some network connection changes but the connection
 remained active / online. The torrc is very simple:
 {{{
 SocksPort 127.0.0.1:9050
 ControlPort 0
 HiddenServiceDir /var/lib/tor/tor_hs
 HiddenServiceVersion 2
 HiddenServicePort <port> 127.0.0.1:<port>
 }}}


 1)
 {{{
 May 12 11:16:08.000 [notice] Your network connection speed appears to have
 changed. Resetting timeout to 60s after 18 timeouts and 362 buildtimes.
 May 12 22:20:32.000 [notice] No circuits are opened. Relaxed timeout for
 circuit 398807 (a Hidden service: Connecting to rendezvous point 4-hop
 circuit in state doing handshakes with channel state open) to 106324ms.
 However, it appears the circuit has timed out anyway. [16 similar
 message(s) suppressed in last 3600 seconds]
 }}}

 2)
 {{{
 May 13 11:05:36.000 [notice] No circuits are opened. Relaxed timeout for
 circuit 399137 (a General-purpose client 3-hop circuit in state waiting to
 see how other guards perform with channel state open) to 106324ms.
 However, it appears the circuit has timed out anyway. [27 similar
 message(s) suppressed in last 3600 seconds]
 }}}

 3)
 {{{
 May 14 21:27:36.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 May 14 21:27:36.000 [notice] Our circuit 0 (id: 400112) died due to an
 invalid selected path, purpose General-purpose client. This may be a torrc
 configuration issue, or a bug. [8 similar message(s) suppressed in last
 3600 seconds]
 }}}

 I wish I could reproduce the last one. Could this be a bug that occurs
 when our primary #1 Guard is in consensus but not reachable just for a
 certain machine / IP?

--

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30520#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online