Re: [tor-relays] Strange behaviour Tor 0.2.9.10

[Geoff Down <geoffdown@xxxxxxxxxxxx>]

On Mon, Mar 20, 2017, at 01:44 PM, teor wrote:
> >> 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.
Mar 20 15:06:59.000 [debug] connection_or_process_cells_from_inbuf():
52: starting, inbuf_datalen 0 (0 pending in tls object).
Mar 20 15:06:59.000 [debug] connection_bucket_refill_helper():
global_read_bucket now 1073741824.
Mar 20 15:06:59.000 [debug] connection_bucket_refill_helper():
global_write_bucket now 1073741824.
Mar 20 15:06:59.000 [debug] connection_bucket_refill_helper():
global_relayed_read_bucket now 1073741824.
Mar 20 15:06:59.000 [debug] connection_bucket_refill_helper():
global_relayed_write_bucket now 1073741824.
Mar 20 15:06:59.000 [debug] connection_bucket_refill_helper():
or_conn->read_bucket now 1073741824.
{repeat}
Mar 20 15:06:59.000 [debug] connection_bucket_refill_helper():
or_conn->write_bucket now 1073741824.
Mar 20 15:06:59.000 [debug] connection_bucket_refill_helper():
or_conn->read_bucket now 1073741824.
{repeat}
Mar 20 15:06:59.000 [warn] Your system clock just jumped 555 seconds
forward; assuming established circuits no longer work.

-- 
http://www.fastmail.com - A no graphics, no pop-ups email service

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays