Nick Mathewson <nickm@xxxxxxxxxxxxx> wrote: > On Thu, Oct 26, 2006 at 06:49:57PM +0200, Fabian Keil wrote: > [...] > > As a result I see indeed a lot less timeout warnings, > > and the servers are declared active right away, but it > > also looks as if the number of timeouts isn't reset > > correctly: > > My apologies for the delay here. Your diagnosis turned out to be > completely correct. I was looking for far more tricky problems, when > the root cause turned out to be (I think) that eventdns.c never > actually reset the timeout count. Oops! I've checked a patch in to > subversion as r9054; if you have a chance to see whether it fixes the > problem for you, I'd be most grateful. I patched Tor 0.1.2.4-alpha about half an hour ago, so I can't be sure yet, but it looks as if the patch causes less timeout warnings, but more "Bad response 2" messages. This is a log excerpt from vanilla Tor 0.1.2.4-alpha: Dec 12 18:55:11.676 [warn] eventdns: Nameserver 81.169.148.34 has failed: request timed out. Dec 12 17:46:01.083 [warn] eventdns: Nameserver 81.169.148.34 is back up Dec 12 17:53:45.157 [warn] eventdns: Nameserver 81.169.148.34 has failed: request timed out. Dec 12 17:53:55.158 [warn] eventdns: Nameserver 81.169.148.34 is back up Dec 12 18:02:27.201 [warn] eventdns: Nameserver 81.169.148.34 has failed: request timed out. Dec 12 18:02:37.242 [warn] eventdns: Nameserver 81.169.148.34 is back up Dec 12 18:12:59.581 [warn] eventdns: Nameserver 81.169.148.34 has failed: request timed out. Dec 12 18:13:09.582 [warn] eventdns: Nameserver 81.169.148.34 is back up Dec 12 18:13:19.784 [warn] eventdns: Nameserver 81.169.148.34 has failed: request timed out. Dec 12 18:13:29.785 [warn] eventdns: Nameserver 81.169.148.34 is back up Dec 12 18:33:15.708 [warn] eventdns: Nameserver 81.169.148.34 has failed: request timed out. Dec 12 18:33:16.746 [warn] eventdns: Nameserver 81.169.148.34 is back up Dec 12 18:43:00.952 [warn] eventdns: Nameserver 81.169.148.34 has failed: request timed out. Dec 12 18:43:02.706 [warn] eventdns: Nameserver 81.169.148.34 is back up This is with your patch applied: Dec 12 18:47:11.260 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Dec 12 18:48:09.113 [notice] Performing bandwidth self-test. Dec 12 18:55:11.676 [warn] eventdns: Nameserver 81.169.148.34 has failed: request timed out. Dec 12 18:55:21.677 [warn] eventdns: Nameserver 81.169.148.34 is back up Dec 12 18:55:37.977 [warn] eventdns: Nameserver 81.169.148.34 has failed: Bad response 2 (server failed) Dec 12 18:55:47.978 [warn] eventdns: Nameserver 81.169.148.34 is back up Dec 12 18:59:26.843 [warn] eventdns: Nameserver 81.169.148.164 has failed: Bad response 2 (server failed) Dec 12 18:59:34.863 [warn] eventdns: Nameserver 81.169.148.34 has failed: Bad response 2 (server failed) Dec 12 18:59:34.864 [warn] eventdns: All nameservers have failed Dec 12 18:59:36.843 [warn] eventdns: Nameserver 81.169.148.164 is back up Dec 12 18:59:44.864 [warn] eventdns: Nameserver 81.169.148.34 is back up I already did get some "Bad response 2" before, so this could be a coincidence. As I said, it's not running long enough to be sure, but it at least looks as if there's still some problem left. Fabian -- http://www.fabiankeil.de/
Attachment:
signature.asc
Description: PGP signature