Re: [tor-relays] How Many Mbps Does A Tor Relay Need To Be A Guard?

2020-05-13 Thread Arlen Yaroslav
Given that your relay is being hosted by OVH in a data-centre I think you will have more than sufficient bandwidth to get the Guard flag. It will be weeks before you see an increase in the utilisation of the bandwidth. If you haven't already, I recommend reading this article: https://blog.torpr

Re: [tor-relays] TOR relays killing internet speed

2021-04-10 Thread Arlen Yaroslav
Hi, Have you set the 'RelayBandwidthRate' and 'RelayBandwidthBurst' configuration parameters in your torrc? If not then you should. ‐‐‐ Original Message ‐‐‐ On Friday, April 9, 2021 6:25 PM, John Csuti wrote: > Hello everyone, > > I am hosting 3 VM's limited at 10Mbps all together. Ea

[tor-relays] Unreachable DirPorts

2021-10-07 Thread Arlen Yaroslav via tor-relays
Hi to all relay operators! I run two Tor relays: 77D08850C1EE8587451F838D3F49874F75B0B1AC 09A70E396DE93F54D4541BBB0EC8E2B23761F34F They both have DirPorts configured on port 80. I can connect to this port on both hosts externally. However, Relay Search is showing the ports as either unreachabl

Re: [tor-relays] Overloaded state indicator on relay-search

2021-10-14 Thread Arlen Yaroslav via tor-relays
Hi all, My relay (77D08850C1EE8587451F838D3F49874F75B0B1AC) is showing as overloaded on the Relay Search page: https://metrics.torproject.org/rs.html#details/77D08850C1EE8587451F838D3F49874F75B0B1AC I have enabled MetricsPort and MetricsPortPolicy in the torrc configuration file. I have retrie

Re: [tor-relays] Overloaded state indicator on relay-search

2021-10-14 Thread Arlen Yaroslav via tor-relays
> Did you use a lot of ram or cpu power recently? I got flagged as overloaded > when I was compiling something and used a lot of cpu. Nothing out of the ordinary. The server is a virtual machine which is dedicated to running a Tor relay. I don't use it for anything else. I've just checked the s

Re: [tor-relays] Overloaded state indicator on relay-search

2021-10-14 Thread Arlen Yaroslav via tor-relays
> I am not sure where you are looking but if you take a look at what > > Onionoo[1] is saying you get > > overload_general_timestamp 163418040 > > which means 10/14/2021 03:00:00 UTC, thus today. > > Georg > > [1] https://onionoo.torproject.org/details?limit=4&search=VinculumGate Thanks, I was

Re: [tor-relays] Overloaded state indicator on relay-search

2021-10-14 Thread Arlen Yaroslav via tor-relays
> The problem is that it’s *not* currently overloaded, there’s nothing to see. > Maybe you can check your syslogs for anything out of the ordinary system-wide? I've checked dmesg. Nothing that stands out as being problematic. Even if there was something there's no way to tell if it's actually th

Re: [tor-relays] Overloaded state indicator on relay-search

2021-10-17 Thread Arlen Yaroslav via tor-relays
Hi, I've done some further analysis on this. The reason my relay is being marked as overloaded is because of DNS timeout errors. I had to dive into the source code to figure this out. In dns.c, a libevent DNS_ERR_TIMEOUT is being recorded as an OVERLOAD_GENERAL error. Am I correct in saying th

[tor-relays] Loss of Stable flag

2021-11-15 Thread Arlen Yaroslav via tor-relays
Hello to all relay operators! My relay Deepsky (09A70E396DE93F54D4541BBB0EC8E2B23761F34F) has not been receiving the 'Stable' flag from the DA consensus. Up until recently (the past month or so) it had been assigned the full complement of flags. Nothing has been changed on the server and I am n

Re: [tor-relays] Loss of Stable flag

2021-11-16 Thread Arlen Yaroslav via tor-relays
On Monday, November 15th, 2021 at 21:53, Scott Bennett wrote: > The authority relays have exhibited very unstable behavior > > for, I think, nearly two years now, as I have pointed out several > > times on this list. For about three months now, there have been > > signs of improvement, but the si

Re: [tor-relays] General overload -> DNS timeouts

2021-11-18 Thread Arlen Yaroslav via tor-relays
> Some folks might consider switching to non-exit nodes to just get rid of > > the overload message. Please bear with us while we are debugging the > > problem and don't do that. :) We'll keep this list in the loop. The undocumented configuration option 'OverloadStatistics' can be used to disable