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

To: tor-relays@xxxxxxxxxxxxxxxxxxxx

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

From: AMuse <tor-amuse@xxxxxxxxxx>

Date: Thu, 6 Jan 2022 23:19:32 -0800

Delivered-to: archiver@xxxxxxxx

Delivery-date: Fri, 07 Jan 2022 06:33:53 -0500

In-reply-to: <a55bd425-2e80-a1d7-86cf-2b6ae3e4fa1d@riseup.net>

List-archive: <http://lists.torproject.org/pipermail/tor-relays/>

List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>

List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>

List-post: <mailto:tor-relays@lists.torproject.org>

List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>

List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>

References: <20211105150534.BC3B73F63D@exit1-nl.msgsafe.io> <CAJepwD1EpbrmkW7e4KqqmMRiROZmK4hvTYn=KaKBjdo6+S3wyw@mail.gmail.com> <406cf750c083e800053592cde533439f@coolcomputers.info> <YZVMMXSXZRdpIxKB@oyster.imrejonk.nl> <0e5932b1-fec5-7341-743b-e427a7265e2c@torproject.org> <-3E0c_pKfH6bwD4kDMmvigy3QTPqe9lU51vsn8yaqOFTCsnYB4uAR6GhRwsk45WTuqLO9h0lUGBWvrW3Hb5Vc7Le2-o5OLWhvdV_qLZYdUY=@protonmail.com> <20211209145828.mp67rv3ido2thq44@raoul> <d0db9aec-2b76-5deb-2783-00b41170d846@riseup.net> <bd01efd3-95a4-ab41-611c-263d5bb3d33d@torproject.org> <a55bd425-2e80-a1d7-86cf-2b6ae3e4fa1d@riseup.net>

Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx

Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

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@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

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