AMuse:
Hey all, I wanted to chime in on this thread because I'm suddenly seeing
DNS "Overload" errors (and corresponding notices that my system is
overloaded on prometheus) lately as well.
The hardware and OS and configs for my public exit haven't changed - what
has changed is that I upgraded
Hey all, I wanted to chime in on this thread because I'm suddenly seeing
DNS "Overload" errors (and corresponding notices that my system is
overloaded on prometheus) lately as well.
The hardware and OS and configs for my public exit haven't changed - what
has changed is that I upgraded tor
Well, I have to say thanks to the update to tor 0.4.6.9 the DNS overload
issue is gone. My consensus Weight went down sightly due to the constant
overload flag. Lets see if time will help heal that.
Good work so far.
Thanks,
John C.
On 2021-12-21 07:39 AM, nusenu wrote:
bobby stickel:
bobby stickel:
It would be nice if we could make the DNS time out percentage threshold higher
in our config file so Tor isn't reporting our exit relays has overloaded
if you run debian and use deb.torproject.org packages,
running
apt update && apt upgrade
should be your solution now
since the
It would be nice if we could make the DNS time out percentage threshold higher in our config file so Tor isn't reporting our exit relays has overloaded___
tor-relays mailing list
tor-relays@lists.torproject.org
Georg Koppen:
Well, not all potential overload is DNS related overload. There are a
bunch of different criteria for emitting a general overload warning.
Onionoo and this relay search have a hard time differentiating
between DNS related (general) overload and other (general) overload.
Thus, I
nusenu:
To stop confusing operators it would make sense to remove the
"This relay is overloaded since"
banner from Relay Search for all tor versions prior to
0.4.6.9 and 0.4.7.3-alpha, no?
Well, not all potential overload is DNS related overload. There are a
bunch of different criteria for
On Thursday, December 16, 2021 2:41:27 PM CET nusenu wrote:
+1
Very wise suggestion.
> To stop confusing operators it would make sense to remove the
>
> "This relay is overloaded since"
>
> banner from Relay Search for all tor versions prior to
> 0.4.6.9 and 0.4.7.3-alpha, no?
>
> kind
+1
> On 16. Dec 2021, at 14:47, John Csuti via tor-relays
> wrote:
>
> Signed PGP part
> I agree its kinda pointless if you know the issue already...
>
> Thanks,
> John C.
>
>
>
> On 2021-12-16 08:41 AM, nusenu wrote:
>
>>
>> To stop confusing operators it would make sense to remove the
I agree its kinda pointless if you know the issue already...
Thanks,
John C.
On 2021-12-16 08:41 AM, nusenu wrote:
To stop confusing operators it would make sense to remove the
"This relay is overloaded since"
banner from Relay Search for all tor versions prior to
0.4.6.9 and
To stop confusing operators it would make sense to remove the
"This relay is overloaded since"
banner from Relay Search for all tor versions prior to
0.4.6.9 and 0.4.7.3-alpha, no?
kind regards,
nusenu
--
https://nusenu.github.io
___
tor-relays
On 18 Nov (10:01:09), Arlen Yaroslav via tor-relays wrote:
> > 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
On Thu, Nov 18, 2021 at 08:30:16AM +, Georg Koppen wrote:
> If the overload is related to non-DNS issues, please address it. For the DNS
> case it is currently a bit tricky. We are actively investigating what is
> going on and suspect we are dealing with a bunch of different issues leading
>
> 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
Imre Jonk:
On Tue, Nov 09, 2021 at 06:25:31AM -0500, John Csuti via tor-relays wrote:
Hello all,
I would have to agree on this it appears that the DNS failure timeout is
too low. I have more then enough bandwidth to host tor exit nodes, and
my own unbound full recursive relay and yet i still
bobby stickel:
I get that too I've noticed that Tor makes a lot of quest to non-existent
domains. I run a pihole DNS without the ad blocking. I think this is a bug. They
should at least give us the ability to control the warning level
It seems only one of your exit relays is affected by a
I get that too I've noticed that Tor makes a lot of quest to non-existent domains. I run a pihole DNS without the ad blocking. I think this is a bug. They should at least give us the ability to control the warning levelOn Nov 17, 2021 10:38 AM, Imre Jonk wrote:On Tue, Nov 09, 2021 at 06:25:31AM
My big family with the same behavior; in the metrics all relays "yellow"
after update of tor software.
Olaf
Am 17.11.21 um 19:38 schrieb Imre Jonk:
On Tue, Nov 09, 2021 at 06:25:31AM -0500, John Csuti via tor-relays wrote:
Hello all,
I would have to agree on this it appears that the DNS
On Tue, Nov 09, 2021 at 06:25:31AM -0500, John Csuti via tor-relays wrote:
> Hello all,
>
> I would have to agree on this it appears that the DNS failure timeout is
> too low. I have more then enough bandwidth to host tor exit nodes, and
> my own unbound full recursive relay and yet i still get
nusenu:
Anders Trier Olesen:
The Tor relay guide should recommend running your recursive resolver
(unbound) on a different IP than your exit:
https://community.torproject.org/relay/setup/exit/
yes, that is a good idea, here is a PR for it:
Anders Trier Olesen:
The Tor relay guide should recommend running your recursive resolver
(unbound) on a different IP than your exit:
https://community.torproject.org/relay/setup/exit/
yes, that is a good idea, here is a PR for it:
https://github.com/torproject/community/pull/169/files
Hello all,
I would have to agree on this it appears that the DNS failure timeout is
too low. I have more then enough bandwidth to host tor exit nodes, and
my own unbound full recursive relay and yet i still get the timeout
message 1-1.5%. Sometimes even weird amounts such as 40-50%.
I have
Hi Ibex
There's some discussion about this issue on #tor-relays. First of all, I
actually don't think there's any problem with your Exit node. IMO 1.5% is
expected and the current threshold is just too low (or the timeout too low).
We're hosting some fairly high capacity exit nodes (around
Hi,
since out of 447 exit relays that support the new overload system
(it got added in tor 0.4.6.x that recently hit the torproject's debian repo)
over 400 (minus those affected by an onionoo bug)
are overloaded as per tor's definition of it, I'll write some
general recommendations for the DNS
Hi everybody,
I am new to tor (as server operator) and try to support the network by
operating an exit node.
Machine is running Ubuntu 20.04 - Tor 0.4.6.8.
nyx is giving me a notive every 10 minutes or so: [NOTICE] General overload ->
DNS timeouts (6) fraction 1.4742% is above threshold of
25 matches
Mail list logo
