Re: [tor-relays] Faravahar acting up again / "Bad Gateway" while uploading descriptor

2017-01-05 Thread Kurt Besig 
On 1/5/2017 1:29 PM, anondroid wrote:
> I just set up a handful of new relays, and all of them have something
> like the following in their logs:
> 
>   [WARN] http status 502 ("Bad Gateway") reason unexpected while
> uploading descriptor to server '154.35.175.225:80'
>   [WARN] Received http status code 502 ("Bad Gateway") from server
> '154.35.175.225:80' while fetching...
> 
> This appears to be related to the authority Faravahar. I know this has
> happened before but I wanted to make sure the proper people were aware
> of the issue.
> 
> Thanks.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
I just stated up a new relay as well and received the same error. This
is the first time after running relays for several years that I've seen
this error/status code. A side note: this is also the first relay I've
run from the same LAN with the same ip, all others are on different VPS'.



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Faravahar acting up again / "Bad Gateway" while uploading descriptor

2017-01-05 Thread Sebastian Hahn 

> On 05 Jan 2017, at 23:26, Toralf Förster  wrote:
> Signed PGP part
> On 01/05/2017 10:40 PM, Sebastian Hahn wrote:
> > They send notifications within 10
> > minutes of the beginning of the hour.
> So, if the issue happens at the 11th minute - it would appear 1 hour before 
> someone noticed it ?

Yes.


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Faravahar acting up again / "Bad Gateway" while uploading descriptor

2017-01-05 Thread Toralf Förster 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 01/05/2017 10:40 PM, Sebastian Hahn wrote:
> They send notifications within 10
> minutes of the beginning of the hour.
So, if the issue happens at the 11th minute - it would appear 1 hour before 
someone noticed it ?

- -- 
Toralf
PGP: C4EACDDE 0076E94E
-BEGIN PGP SIGNATURE-

iHYEAREIAB4FAlhux/YXHHRvcmFsZi5mb2Vyc3RlckBnbXguZGUACgkQxOrN3gB2
6U746wD+MxjXMgKl+6yNsl4M2KO6QG/VCvga6BW6Nvnxq5Eyd9oA/jXq+OJYJK/N
E86Pm89g/70ITMCn9zXVpr0mV9egn0Xt
=10Kj
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Faravahar acting up again / "Bad Gateway" while uploading descriptor

2017-01-05 Thread Sebastian Hahn 

> On 05 Jan 2017, at 22:29, anondroid  wrote:
> 
> I just set up a handful of new relays, and all of them have something like 
> the following in their logs:
> 
>   [WARN] http status 502 ("Bad Gateway") reason unexpected while uploading 
> descriptor to server '154.35.175.225:80'
>   [WARN] Received http status code 502 ("Bad Gateway") from server 
> '154.35.175.225:80' while fetching...
> 
> This appears to be related to the authority Faravahar. I know this has 
> happened before but I wanted to make sure the proper people were aware of the 
> issue.
> 
> Thanks.

Thanks for letting us know, but it isn't necessary. We
have automated systems that identify issues with the
directory authorities. They send notifications within 10
minutes of the beginning of the hour.

Thanks for checking your relay's log!

Cheers
Sebastian
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays