Re: Tor 0.1.2.2-alpha eventdns timeouts
Nick Mathewson <[EMAIL PROTECTED]> 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/ signature.asc Description: PGP signature
Re: Tor 0.1.2.2-alpha eventdns timeouts
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. yrs, -- Nick Mathewson pgptOe8IBfR0T.pgp Description: PGP signature
Re: Tor 0.1.2.2-alpha eventdns timeouts
Nick Mathewson <[EMAIL PROTECTED]> wrote:
> On Mon, Oct 23, 2006 at 12:48:48PM +0200, Fabian Keil wrote:
> [...]
> > Oct 23 12:09:06.074 [warn] eventdns: Nameserver 10.0.0.4 is back up
> >
> > This always seems to happen if there are more than a few (<5)
> > DNS requests per second. Am I the only one seeing this?
>
> No, this seems to be a (relatively harmless) bug with our eventdns
> code. I'm hoping to have it fixed soon; please let us know if it
> appears in later versions.
>
> Also, you can check to see whether bugs are already reported by
> checking our bugtracker at:
>
>http://bugs.noreply.org/flyspray/index.php?tasks=all&project=4
I'll keep that in mind, thanks.
> This is bug 326:
>
>http://bugs.noreply.org/flyspray/index.php?do=details&id=326
Is "timeout threshold is set too low, and the threshold for declaring
a server down is set too low" still the current analysis?
I increased global_max_retransmits and global_max_nameserver_timeout
from 3 to 5 and changed global_timeout from {3, 0} to {20, 0}.
As eventdns used to complaint from time to time about
"Bad response 2 (server failed)" and I didn't find a threshold
for these cases, I also added {0, 0} at the beginning of
global_nameserver_timeouts[], to make sure the server wouldn't
be ignored for ten seconds.
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:
Oct 26 18:00:26.467 [warn] eventdns: Nameserver 81.169.148.34 has failed:
request timed out.
Oct 26 18:00:26.469 [warn] eventdns: Nameserver 81.169.148.34 is back up
[ten DNS requests successful]
Oct 26 18:00:35.962 [warn] eventdns: Nameserver 81.169.148.34 has failed:
request timed out.
Oct 26 18:00:36.017 [warn] eventdns: Nameserver 81.169.148.34 is back up
[thirteen DNS requests succesful]
Oct 26 18:00:55.992 [warn] eventdns: Nameserver 81.169.148.34 has failed:
request timed out.
Oct 26 18:00:56.008 [warn] eventdns: Nameserver 81.169.148.34 is back up
I assumed that there should be at least global_timeout seconds
between the last successful DNS requests, and a DNS server being
marked as down because of timeouts?
Fabian
--
http://www.fabiankeil.de/
signature.asc
Description: PGP signature
Re: Tor 0.1.2.2-alpha eventdns timeouts
On Mon, Oct 23, 2006 at 12:48:48PM +0200, Fabian Keil wrote: [...] > Oct 23 12:09:06.074 [warn] eventdns: Nameserver 10.0.0.4 is back up > > This always seems to happen if there are more than a few (<5) > DNS requests per second. Am I the only one seeing this? No, this seems to be a (relatively harmless) bug with our eventdns code. I'm hoping to have it fixed soon; please let us know if it appears in later versions. Also, you can check to see whether bugs are already reported by checking our bugtracker at: http://bugs.noreply.org/flyspray/index.php?tasks=all&project=4 This is bug 326: http://bugs.noreply.org/flyspray/index.php?do=details&id=326 yrs, -- Nick Mathewson pgpSjxLM119Lr.pgp Description: PGP signature
Re: Tor 0.1.2.2-alpha eventdns timeouts
Hi, I have the same problem each time I start my home server (Windows XP SP2), I get those lines a few times (however, it shows my local IP, not my remote IP) but despite that everything seems to be normal. Usually the last line ends like yours: .. is back up. So I believe since it ends with "is back up" everything is okay... I hope? Sincerely, Enigma -- German Tor mailing list / surveillance and its risks: http://www.anti1984.com Fabian Keil schrieb: > With Tor 0.1.2.2-alpha running as exit node on > FreeBSD 7.0-CURRENT I constantly get warnings > like: > > Oct 23 11:56:02.760 [warn] eventdns: Nameserver 10.0.0.4 is back up > Oct 23 11:56:21.183 [warn] eventdns: Nameserver 81.169.148.164 has failed: > Bad response 2 (server failed) > Oct 23 11:56:23.770 [warn] eventdns: Nameserver 81.169.148.34 has failed: > request timed out. > Oct 23 11:56:31.185 [warn] eventdns: Nameserver 81.169.148.164 is back up > Oct 23 11:56:33.776 [warn] eventdns: Nameserver 81.169.148.34 is back up > Oct 23 11:58:47.232 [warn] eventdns: Nameserver 81.169.148.34 has failed: > request timed out. > Oct 23 11:58:48.867 [warn] eventdns: Nameserver 81.169.148.34 is back up > Oct 23 11:59:05.767 [warn] eventdns: Nameserver 81.169.148.164 has failed: > request timed out. > Oct 23 11:59:15.802 [warn] eventdns: Nameserver 81.169.148.164 is back up > Oct 23 12:02:02.180 [warn] eventdns: Nameserver 81.169.148.34 has failed: > request timed out. > Oct 23 12:02:12.182 [warn] eventdns: Nameserver 81.169.148.34 is back up > Oct 23 12:08:50.727 [warn] eventdns: Nameserver 81.169.148.34 has failed: Bad > response 2 (server failed) > Oct 23 12:08:53.062 [warn] eventdns: Nameserver 81.169.148.164 has failed: > request timed out. > Oct 23 12:08:56.068 [warn] eventdns: Nameserver 10.0.0.4 has failed: request > timed out. > Oct 23 12:08:57.148 [warn] eventdns: Nameserver 81.169.148.34 is back up > Oct 23 12:09:03.064 [warn] eventdns: Nameserver 81.169.148.164 is back up > Oct 23 12:09:06.074 [warn] eventdns: Nameserver 10.0.0.4 is back up > > This always seems to happen if there are more than a few (<5) > DNS requests per second. Am I the only one seeing this? > > Fabian >
Tor 0.1.2.2-alpha eventdns timeouts
With Tor 0.1.2.2-alpha running as exit node on FreeBSD 7.0-CURRENT I constantly get warnings like: Oct 23 11:56:02.760 [warn] eventdns: Nameserver 10.0.0.4 is back up Oct 23 11:56:21.183 [warn] eventdns: Nameserver 81.169.148.164 has failed: Bad response 2 (server failed) Oct 23 11:56:23.770 [warn] eventdns: Nameserver 81.169.148.34 has failed: request timed out. Oct 23 11:56:31.185 [warn] eventdns: Nameserver 81.169.148.164 is back up Oct 23 11:56:33.776 [warn] eventdns: Nameserver 81.169.148.34 is back up Oct 23 11:58:47.232 [warn] eventdns: Nameserver 81.169.148.34 has failed: request timed out. Oct 23 11:58:48.867 [warn] eventdns: Nameserver 81.169.148.34 is back up Oct 23 11:59:05.767 [warn] eventdns: Nameserver 81.169.148.164 has failed: request timed out. Oct 23 11:59:15.802 [warn] eventdns: Nameserver 81.169.148.164 is back up Oct 23 12:02:02.180 [warn] eventdns: Nameserver 81.169.148.34 has failed: request timed out. Oct 23 12:02:12.182 [warn] eventdns: Nameserver 81.169.148.34 is back up Oct 23 12:08:50.727 [warn] eventdns: Nameserver 81.169.148.34 has failed: Bad response 2 (server failed) Oct 23 12:08:53.062 [warn] eventdns: Nameserver 81.169.148.164 has failed: request timed out. Oct 23 12:08:56.068 [warn] eventdns: Nameserver 10.0.0.4 has failed: request timed out. Oct 23 12:08:57.148 [warn] eventdns: Nameserver 81.169.148.34 is back up Oct 23 12:09:03.064 [warn] eventdns: Nameserver 81.169.148.164 is back up Oct 23 12:09:06.074 [warn] eventdns: Nameserver 10.0.0.4 is back up This always seems to happen if there are more than a few (<5) DNS requests per second. Am I the only one seeing this? Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
