#21969: We're missing descriptors for some of our primary entry guards
-----------------------------------------------+---------------------------
Reporter: asn | Owner: asn
Type: defect | Status:
| needs_information
Priority: Immediate | Milestone: Tor:
| 0.3.4.x-final
Component: Core Tor/Tor | Version: Tor:
| 0.3.0.6
Severity: Blocker | Resolution:
Keywords: tor-guard, tor-bridge, tor-client | Actual Points:
Parent ID: | Points: 1.5
Reviewer: | Sponsor: SponsorV
-----------------------------------------------+---------------------------
Comment (by asn):
Replying to [comment:71 cypherpunks]:
> Replying to [comment:69 asn]:
> > Hello, do you guys have any info logs for these issues by any chance?
That would be really useful!
>
> {{{
> [notice] Your system clock just jumped 3902 seconds forward; assuming
established circuits no longer work.
> [notice] Tried for 3915 seconds to get a connection to [scrubbed]:9878.
Giving up. (waiting for rendezvous desc)
> [notice] Tried for 3915 seconds to get a connection to [scrubbed]:9878.
Giving up. (waiting for rendezvous desc)
> [notice] Delaying directory fetches: No running bridges
> }}}
>
Thanks for the logs. Unfortunately, they are not info level which kinda
makes it harder.
Some questions so that I understand the situation a bit better (too many
cypherpunks in this ticket). Did you suspend your box for like an hour
(3902 seconds?). Also, are you using bridges? I guess they were up at that
time, and Tor was confused? Is this a ricochet setup?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21969#comment:72>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
