On Fri, Mar 24, 2017, at 07:35 AM, teor wrote:
On 21 Mar 2017, at 01:42, Geoff Down geoffdown@fastmail.net wrote: ... The usual SIGINT shutdown hangs as well - have to send a second SIGINT.
What is ShutdownWaitLength set to in your torrc or default torrc?
Not set.
Done, (SIGINT still hadn't shut down after 10 minutes btw) then
Please see my reply above: this could be a clock issue on your side, or it could be a config issue, or it could be a bug in tor.
I opened #21809 for this: https://trac.torproject.org/projects/tor/ticket/21809
Doesn't his mean there should be 102-second and 2673-second gaps in the
logs? Unfortunately there is so much going on it is hard to spot any gaps. 2673 seconds is roughly the gap between those two warnings.
That's helpful. Thanks!
I'm still getting occasional read timeouts (via Polipo) from a site that is entirely reliable over clearnet, and occasional 'Failed to receive SOCKS5 connect request ack' from another site when using curl in socks5hproxy mode. I've had no more clock jumps in the last 70 hours though. If there's nothing more I can do to debug this (and since my IP could change at any time), I'll go back a Tor version and remove the Address line. GD