On Tue, Mar 21, 2017, at 09:27 AM, teor wrote: > > Can you try setting an explicit IP address for your bridge, using: > Address NNN.NNN.NNN.NNN > in the torrc? > > We might not have fixed all instances of this issue in 20423. > Done, (SIGINT still hadn't shut down after 10 minutes btw) then Mar 21 14:24:01.000 [notice] Tor 0.2.9.10 opening new log file. ... Mar 21 14:50:40.000 [debug] circuit_get_by_circid_channel_impl(): circuit_get_by_circid_channel_impl() returning circuit 0x6961720 for circ_id 3432589531, channel ID 4 (0x772e440) Mar 21 14:50:40.000 [debug] relay_lookup_conn(): found conn for stream 8331. Mar 21 14:50:40.000 [debug] circuit_receive_relay_cell(): Sending to origin. Mar 21 14:50:40.000 [debug] connection_edge_process_relay_cell(): Now seen 21024 relay cells here (command 2, stream 8331). Mar 21 14:50:40.000 [debug] connection_edge_process_relay_cell(): circ deliver_window now 991. Mar 21 14:50:40.000 [debug] connection_or_process_cells_from_inbuf(): 24: starting, inbuf_datalen 274 (0 pending in tls object). Mar 21 14:50:40.000 [debug] connection_bucket_refill_helper(): global_read_bucket now 1073741824. Mar 21 14:50:40.000 [debug] connection_bucket_refill_helper(): global_write_bucket now 1073741824. Mar 21 14:50:40.000 [debug] connection_bucket_refill_helper(): or_conn->read_bucket now 1073741824. Mar 21 14:50:40.000 [debug] connection_bucket_refill_helper(): or_conn->write_bucket now 1073741824. Mar 21 14:50:40.000 [warn] Your system clock just jumped 102 seconds forward; assuming established circuits no longer work. -- Mar 21 15:35:13.000 [debug] connection_bucket_refill_helper(): global_relayed_write_bucket now 1073741824. Mar 21 15:35:13.000 [debug] connection_bucket_refill_helper(): or_conn->read_bucket now 1073741824. Mar 21 15:35:13.000 [debug] connection_bucket_refill_helper(): or_conn->read_bucket now 1073741824. Mar 21 15:35:13.000 [debug] connection_bucket_refill_helper(): or_conn->write_bucket now 1073741824. Mar 21 15:35:13.000 [debug] connection_bucket_refill_helper(): or_conn->read_bucket now 1073741824. Mar 21 15:35:13.000 [debug] connection_bucket_refill_helper(): or_conn->write_bucket now 1073741824. Mar 21 15:35:13.000 [debug] connection_bucket_refill_helper(): or_conn->read_bucket now 1073741824. Mar 21 15:35:13.000 [debug] connection_bucket_refill_helper(): or_conn->read_bucket now 1073741824. Mar 21 15:35:13.000 [debug] connection_bucket_refill_helper(): or_conn->read_bucket now 1073741824. Mar 21 15:35:13.000 [debug] connection_bucket_refill_helper(): or_conn->write_bucket now 1073741824. Mar 21 15:35:13.000 [warn] Your system clock just jumped 2673 seconds forward; assuming established circuits no longer work.
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. -- http://www.fastmail.com - The way an email service should be _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays