> > On 21 Mar 2017, at 01:42, Geoff Down <geoffdown@xxxxxxxxxxxx> wrote: > ... > The usual SIGINT shutdown hangs as well - have to send a second SIGINT. No, this is by design, to allow users to migrate connections. See ShutdownWaitLength in the tor manual page. This could also be happening if your relay's clock changes during the ShutdownWaitLength period. What is ShutdownWaitLength set to in your torrc or default torrc? > On 22 Mar 2017, at 07:03, Geoff Down <geoffdown@xxxxxxxxxxxx> wrote: > > 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 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 > 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 [warn] Your system clock just jumped 102 seconds > forward; assuming established circuits no longer work. > -- (Please don't put -- in your emails. Some people use broken mail readers that hide everything below a -- .) > Mar 21 15:35:13.000 [debug] connection_bucket_refill_helper(): > global_relayed_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. That's helpful. Thanks! I made a note on #20423: https://trac.torproject.org/projects/tor/ticket/20423 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