“Tried to establish rendezvous on non-OR or non-edge circuit.”
Seen by an operator of a fairly large relay. The relay was also dropping CREATE cells due to CPU overload.
This message means that there is a bug somewhere. I don't know where.
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Robert Ransom changed milestone to %Tor: 0.2.3.x-final
changed milestone to %Tor: 0.2.3.x-final
- Author
The relay's operator was not using the relay as a client or hidden service.
I've seeing this too on 2 relays, one an exit node and the other a middle node.
In both cases the message started on Sept 15th. - the day after I upgraded from 0.2.2.32 to 0.2.2.33.
On the busier node (the exit node) the message has been logged 39 times in the last 19 days.
Trac:
Username: tmpname0901fluxe3 has three to 30 of these in its logs per day. I think we tracked it down and concluded this should be a protocol warning before but then forgot to do anything about it.
- Author
It looks like "non-edge" in that message means that the OR at which the client is trying to ESTABLISH_RENDEZVOUS isn't the last (farthest-from-client) OR on the circuit. At the very least, that part of the message needs to be reworded.
This should become a protocol warning, but we do need to figure out what is going on here if possible.
- Author
Trac:
Status: new to assigned
Owner: N/A to rransom Tentatively calling this "tor 0.2.3.x"
Trac:
Milestone: N/A to Tor: 0.2.3.x-finalTrac:
Cc: N/A to twilde@cymru.com- Author
This is caused by #4641 (moved).
#4641 (moved) is now fixed in master. Leaving this one open in case we want to downgrade it to protocol_warn.
Any support for downgrading this message? If not, I suggest we close.
Nobody thinks we should downgrade to protocol_warn. Closing.
Trac:
Status: assigned to closed
Resolution: N/A to fixedTrac:
Keywords: N/A deleted, tor-hs addedTrac:
Component: Tor Hidden Services to Tor- Trac closed
closed
- Robert Ransom mentioned in issue #4641 (moved)
mentioned in issue #4641 (moved)
- Trac moved to tpo/core/tor#4171 (closed)
moved to tpo/core/tor#4171 (closed)
- Trac mentioned in issue tpo/core/tor#4641 (closed)
mentioned in issue tpo/core/tor#4641 (closed)