George Kadianakis:
> I took a brief look at the relevant code, and I'm also not sure what's
> causing the issue. More digging required.
Toralf Förster:
> Something I should worry about ?
I think one should emphasize that relay operators shouldn't worry about
it since it's client(s) [hopefully
Little update :
No more "ESTABLISH_RENDEZVOUS" logged since this day...
07/10/2016 08:09, Petrusko :
> x2 too on a non-exit relay :
> Oct 06 13:35:22.000 (UTC+2)
>
> But nothing a 2nd relay process on the same machine...
--
Petrusko
PubKey EBE23AE5
C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2
Toralf Förster writes:
> [ text/plain ]
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Today I got this for the first since I run exits:
>
> Oct 06 08:23:03.000 [warn] Duplicate rendezvous cookie in
> ESTABLISH_RENDEZVOUS.
>
> Something I should worry
pa011:
> Several of those warnings here as well on Oct 06 - on exit as on non
> exit - at different times
Sure, type of relay doesn't matter here since a rendezvous client picks
random relay to act as Rendezvous Point. Somehow there are clients who
send more than one ESTABLISH_RENDEZVOUS cell to
Am 07.10.2016 um 20:20 schrieb Green Dream:
> One of my guard relays has a few entries on Oct 06 also:
>
> Oct 06 09:04:00.000 [warn] Duplicate rendezvous cookie in
> ESTABLISH_RENDEZVOUS.
> Oct 06 09:04:00.000 [warn] Duplicate rendezvous cookie in
> ESTABLISH_RENDEZVOUS.
> Oct 06
One of my guard relays has a few entries on Oct 06 also:
Oct 06 09:04:00.000 [warn] Duplicate rendezvous cookie in
ESTABLISH_RENDEZVOUS.
Oct 06 09:04:00.000 [warn] Duplicate rendezvous cookie in
ESTABLISH_RENDEZVOUS.
Oct 06 10:17:30.000 [warn] Duplicate rendezvous cookie in
Toralf Förster:
> nope, from "git blame" the appropriate line is part of git commit
> 339df5df and that commit is already part of tor-0.2.4.11-alpha :
>
> commit 339df5df085e2115c01881cf628abe5ed3fbd456
I'm unable find change to this line in
339df5df085e2115c01881cf628abe5ed3fbd456.
AFAICT,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/06/2016 06:29 PM, Logforme wrote:
> Maybe they are new in 0.2.8.8?
nope, from "git blame" the appropriate line is part of git commit 339df5df and
that commit is already part of tor-0.2.4.11-alpha :
commit
x2 too on a non-exit relay :
Oct 06 13:35:22.000 (UTC+2)
But nothing a 2nd relay process on the same machine...
06/10/2016 18:29, Logforme :
> I had 3 today on my non-exit relay. Can't remember seeing them before. Maybe
> they are new in 0.2.8.8? > Times are UTC+2 > > Oct 06 09:14:03.000
Same here, no clue why :(
markus
2016-10-06 10:45 GMT+02:00 Toralf Förster :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Today I got this for the first since I run exits:
>
> Oct 06 08:23:03.000 [warn] Duplicate rendezvous cookie in
>
:14.000 [warn] Duplicate rendezvous cookie in
ESTABLISH_RENDEZVOUS.
-- Originalmeddelande --
Från: "Toralf Förster" <toralf.foers...@gmx.de>
Till: tor-relays@lists.torproject.org
Skickat: 2016-10-06 10:45:49
Ämne: [tor-relays] new warn message: Duplicate r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Today I got this for the first since I run exits:
Oct 06 08:23:03.000 [warn] Duplicate rendezvous cookie in
ESTABLISH_RENDEZVOUS.
Something I should worry about ?
- --
Toralf
PGP: C4EACDDE 0076E94E, OTR: 420E74C8 30246EE7
-BEGIN PGP
12 matches
Mail list logo