> On 21 Mar 2017, at 00:09, Geoff Down <geoffdown@xxxxxxxxxxxx> wrote: > > More information: > Mar 20 10:48:23.000 [warn] Your system clock just jumped 38788 seconds > forward; assuming established circuits no longer work. > This is starting to seem familiar: I searched the archives but nothing > recent. NTP seems fine. If no-one has any better ideas I'll go back a > version. > > On Sun, Mar 19, 2017, at 02:20 PM, Geoff Down wrote: >> Further information. >> Curl error >> Failed to receive SOCKS5 connect request ack. >> and from earlier, Tor log >> Mar 19 11:52:37.000 [notice] Tried for 32496 seconds to get a connection >> to [scrubbed]:80. Giving up. We fixed a bug like this in 0.2.9.6-rc. It was caused by DNS resolves that received no reply and didn't timeout. (DNS resolution occurs on the main thread.) Here's the ChangeLog entry and bug: https://gitweb.torproject.org/tor.git/tree/ChangeLog?id=1f6c8eda0073f464b7d23323251d72822f0a18bd#n262 https://trac.torproject.org/projects/tor/ticket/20423 You can help us diagnose this issue by providing the log lines just before: > [warn] Your system clock just jumped [0-9]* seconds > forward; assuming established circuits no longer work. Using debug logs should help us identify the exact function call causing the issue. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
Attachment:
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays