Re: warning message question

2009-07-26 Thread Karsten Loesing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/26/2009 09:52 AM, Roger Dingledine wrote:
> On Sun, Jul 26, 2009 at 02:32:45AM -0500, Scott Bennett wrote:
>>  Saturday morning, I got the following message.
>>
>> Jul 25 09:33:57.004 [warn] Received http status code 502 ("Proxy Error") 
>> from server '80.190.246.100:80' while fetching consensus directory.
>>
>> Can anyone explain the situation(s) that can result in such a message?
> 
> 80.190.246.100:80 is the DirPort on gabelmoo, one of the v3 authorities.
> So your relay was trying to get an updated version of the v3 consensus
> from gabelmoo.
> 
> It looks like the way gabelmoo is listening on port 80 is by proxypassing
> it through apache. You can read more about that approach in this poorly
> organized faq entry:
> https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients
> 
> and at that particular moment, for some reason apache decided that
> sending back a 502 proxy error was better than passing your request on.

FYI, gabelmoo is passing directory requests through Apache for two
reasons: First, I have been using Apache as a first attempt to measure
how long clients take to download network statuses in order to derive
how fast clients are; this functionality is now in 0.2.2.0-alpha-dev, so
that Apache is not required anymore for this:

http://archives.seul.org/or/cvs/Jul-2009/msg00244.html

Second, I'm using port 80 both for serving the Tor directory and for
serving files for performance measurements:

http://freehaven.net/~karsten/volatile/torperf-2009-07-01.pdf

> For example, I bet this could happen if the gabelmoo relay was down at
> the time.

It's back online now.

- --Karsten

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpsMc8ACgkQ0M+WPffBEmWTTQCdFth19N02fKpJc7vAJE+pSMOW
+3sAoLGWwxPlkCXmSLD/BHldeeqGdpTU
=FvlG
-END PGP SIGNATURE-


Re: warning message question

2009-07-26 Thread Scott Bennett
 On Sun, 26 Jul 2009 03:52:38 -0400 Roger Dingledine 
wrote:
>On Sun, Jul 26, 2009 at 02:32:45AM -0500, Scott Bennett wrote:
>>  Saturday morning, I got the following message.
>> 
>> Jul 25 09:33:57.004 [warn] Received http status code 502 ("Proxy Error") 
>> from server '80.190.246.100:80' while fetching consensus directory.
>> 
>> Can anyone explain the situation(s) that can result in such a message?
>
>80.190.246.100:80 is the DirPort on gabelmoo, one of the v3 authorities.
>So your relay was trying to get an updated version of the v3 consensus
>from gabelmoo.
>
>It looks like the way gabelmoo is listening on port 80 is by proxypassing
>it through apache. You can read more about that approach in this poorly
>organized faq entry:
>https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients

 Eeeeuww!  That's hideous.  Why would someone configure a mess
like that when they could just as easily use an RDR rule?
>
>and at that particular moment, for some reason apache decided that
>sending back a 502 proxy error was better than passing your request on.

 How would a typical user know that the "proxy" in question was an
apache server on the other end?  Ugh.
>
>For example, I bet this could happen if the gabelmoo relay was down at
>the time.
>
 Bummer.  Thanks for the explanation, Roger.


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at cs.niu.edu  *
**
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**


Re: warning message question

2009-07-26 Thread Gitano
Scott Bennett wrote:

>  Saturday morning, I got the following message.
> 
> Jul 25 09:33:57.004 [warn] Received http status code 502 ("Proxy
Error") from server '80.190.246.100:80' while fetching consensus directory.

I've got similar messages too, always in conjunction with 'Got a bad
signature on a networkstatus vote' (Tor v0.2.1.17):

Jul 25 01:33:13.917 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:33:13.917 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:33:13.917 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:33:13.917 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:33:13.917 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:33:13.918 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:33:13.918 [warn] 0 unknown, 0 missing key, 0 good, 6 bad, 0 no
signature, 4 required
Jul 25 01:33:13.918 [warn] Not enough good signatures on networkstatus
consensus
Jul 25 01:33:13.918 [warn] Unable to load consensus directory downloaded
from server '137.56.75.117:11375'. I'll try again soon.
Jul 25 01:34:16.791 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:34:16.791 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:34:16.791 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:34:16.791 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:34:16.792 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:34:16.792 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:34:16.792 [warn] 0 unknown, 0 missing key, 0 good, 6 bad, 0 no
signature, 4 required
Jul 25 01:34:16.792 [warn] Not enough good signatures on networkstatus
consensus
Jul 25 01:34:16.792 [warn] Unable to load consensus directory downloaded
from server '216.146.46.30:9001'. I'll try again soon.
Jul 25 01:44:24.800 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:44:24.800 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:44:24.801 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:44:24.801 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:44:24.801 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:44:24.801 [warn] Got a bad signature on a networkstatus vote
Jul 25 01:44:24.801 [warn] 0 unknown, 0 missing key, 0 good, 6 bad, 0 no
signature, 4 required
Jul 25 01:44:24.801 [warn] Not enough good signatures on networkstatus
consensus
Jul 25 01:44:24.801 [warn] Unable to load consensus directory downloaded
from server '91.143.93.213:9002'. I'll try again soon.
Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote
Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote
Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote
Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote
Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote
Jul 25 02:18:58.903 [warn] Got a bad signature on a networkstatus vote
Jul 25 02:18:58.903 [warn] 0 unknown, 0 missing key, 0 good, 6 bad, 0 no
signature, 4 required
Jul 25 02:18:58.903 [warn] Not enough good signatures on networkstatus
consensus
Jul 25 02:18:58.904 [warn] Unable to load consensus directory downloaded
from server '88.159.81.251:110'. I'll try again soon.


Re: warning message question

2009-07-26 Thread Roger Dingledine
On Sun, Jul 26, 2009 at 02:32:45AM -0500, Scott Bennett wrote:
>  Saturday morning, I got the following message.
> 
> Jul 25 09:33:57.004 [warn] Received http status code 502 ("Proxy Error") from 
> server '80.190.246.100:80' while fetching consensus directory.
> 
> Can anyone explain the situation(s) that can result in such a message?

80.190.246.100:80 is the DirPort on gabelmoo, one of the v3 authorities.
So your relay was trying to get an updated version of the v3 consensus
from gabelmoo.

It looks like the way gabelmoo is listening on port 80 is by proxypassing
it through apache. You can read more about that approach in this poorly
organized faq entry:
https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients

and at that particular moment, for some reason apache decided that
sending back a 502 proxy error was better than passing your request on.

For example, I bet this could happen if the gabelmoo relay was down at
the time.

--Roger



warning message question

2009-07-26 Thread Scott Bennett
 Saturday morning, I got the following message.

Jul 25 09:33:57.004 [warn] Received http status code 502 ("Proxy Error") from 
server '80.190.246.100:80' while fetching consensus directory.

Can anyone explain the situation(s) that can result in such a message?
 Thanks in advance!


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at cs.niu.edu  *
**
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**