[tor-relays] General overload -> DNS timeouts

Mailing Lists tor-relays
21

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

22

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 stable repo has been updated to
tor 0.4.6.9
and the experimental repo contains
0.4.7.3-alpha which also includes your desired change.

kind regards,
nusenu

···

--
https://nusenu.github.io
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

23

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:

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 stable repo has been updated to
tor 0.4.6.9
and the experimental repo contains
0.4.7.3-alpha which also includes your desired change.

kind regards,
nusenu

24

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 itself, and added ipv6.

I suspect a decent amount of my DNS failures are actually lookups for AAAA records that don’t exist, because my exit supports v6 but the destination site doesn’t, or only half-configured it.

The system itself is definitely NOT overloaded. ( load averages: 0.07, 0.23, 0.24 )

···

On Fri, Dec 17, 2021 at 2:03 AM nusenu <nusenu-lists@riseup.net> wrote:

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 don’t think this change is easily to make.

To have the DNS trigger included in a shared trigger info
was a deliberate design decision as I understood it.

In my opinion it is better to remove this notice from Relay Search
for all affected versions, even if it will also remove the warning in
cases where the trigger was not DNS related, because
it potentially causes alarm fatique and operators will continue
to ignore the banner even after it got improved.

I think the best option here is to upgrade swiftly to
0.4.6.9/0.4.7.3-alpha.

That is not easy for all of the operators that use the Torproject’s Debian repos
since these versions are usually not “swiftly” available on deb.torproject.org yet
(unless you switch to nightly packages which I wouldn’t recommend).
currently: Version: 0.4.6.8-1~d10.buster+1 [1]

kind regards,
nusenu

[1] https://deb.torproject.org/torproject.org/dists/buster/main/binary-amd64/Packages

–
https://nusenu.github.io

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

25

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 tor itself, and added ipv6.

You appear to be running tor 0.4.6.8 on FreeBSD.

As has been previously stated on this thread the code involved
has been changed in tor 0.4.6.9 and 0.4.7.3-alpha.

So you will have to wait till FreeBSD ports ship that version.

After upgrading the tor version the overload indicator on
will disappear when it it was DNS related (there can be other reasons).

kind regards,
nusenu

···

--
https://nusenu.github.io
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 Like