On Mon, Mar 20, 2017, at 01:44 PM, teor wrote:
On 21 Mar 2017, at 00:09, Geoff Down geoffdown@fastmail.net wrote:
More information: Mar 20 10:48:23.000 [warn] Your system clock just jumped 38788 seconds forward; assuming established circuits no longer work.
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=1f6c8eda0073f464b7d2... 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.
Thanks Tim, will do. The usual SIGINT shutdown hangs as well - have to send a second SIGINT. GD