In #12997comment:6 nickm requested to open a new ticket if someone gets that warning again.
I get that warning since weeks on 0.4.1.6 about once a day on different relays.
Even if legacy/trac#12997 (moved) is implemented i never saw a more specific warning than that simple line.
This is all the log shows me:
Dec 09 10:36:03.000 [notice] DoS mitigation since startup: 10 circuits killed with too many cells. 1835037 circuits rejected, 91 marked addresses. 711976 connections closed. 10660 single hop clients refused.Dec 09 12:29:48.000 [warn] Tried to establish rendezvous on non-edge circuitDec 09 16:36:03.000 [notice] Heartbeat: Tor's uptime is 47 days 0:00 hours, with 23309 circuits open. I've sent 56816.96 GB and received 56583.09 GB.
Trac: Username: computer_freak
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
I just see that the ticket legacy/trac#12997 (moved) is not exactly the same error message than the one i get.
Seems Google trapped me into it:)
So if possible please rename this ticket.
Anyway i get the error message i provided and dont know what to do with it.
Trac: Summary: Tried to establish rendezvous on non-OR or non-edge circuit to Tried to establish rendezvous on non-edge circuit Parent: N/Atolegacy/trac#15618 (moved)
Yes, I think turning those into protocol-warns is a good direction to go. (I haven't looked at each of them to be convinced that each of them should change, but I expect and hope that we find they should.)
I have just noticed the same [warn] thirty-six (36) times on eleven (11) of my sixteen (16) relays. The first one, and the most recent one, being:-
Dec 07 03:49:28.000 [warn] Tried to establish rendezvous on non-edge circuitDec 12 10:23:33.000 [warn] Tried to establish rendezvous on non-edge circuit
All of my relays are the same, namely "Ubuntu 18.04.3 LTS bionic" and Tor version "0.4.1.6". They are spread across ten internet providers and seven countries.
I've turned a number of log statement to protocol warning within rendmid.c. I believe all of them can be triggered remotely so no need to warn or info if they happen.