Re: [tor-relays] General overload -> DNS timeouts
> 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 the reporting of an overloaded state. E.g. place the following in your torrc: OverloadStatistics 0 May be worth considering until the reporting feature becomes a bit more mature and the issues around DNS resolution become a bit clearer. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Loss of Stable flag
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 situation is still not terribly > > stable or predictable. The two flags that appear to me to have > > been most affected are HSDir and Stable, but Fast has also come > > and gone occasionally since the instability began. I don't run > > a Guard relay, so I don't know about that flag's stability, but > > I would imagine that it would be affected by instability in the > > Stable and Fast flags. All three flags can come and go, seemingly > > at random, without regard to uptime of a relay or stability of its > > own characteristics and network connections. Yes I have also lost the Guard and HSDir flags. I agree with you that these seem to be predicated on gaining the Stable flag, which is my focus for this thread. Basically, most of the DAs do not believe my relay's reported uptime, which at the time of writing is over 12 days. I would like to understand why this is happening. I suspect network issues (routing, peering or socket resources) are at play here but instead of spending time speculating I would prefer if the DA operators could assist me with this. The DAs which are witholding the flag are tor26, gabelmoo, dannenberg, maatuska and bastet. I also agree with you that there appear to be wider problems with the consensus health overall, but to me the issues have increased noticably in the past few months. ‐‐‐ Original Message ‐‐‐ On Tuesday, November 16th, 2021 at 01:53, dg26 wrote: > How much RAM are you running Tor in your instance? Probably not enough > > RAM and getting the TCP Out of memory. 2GB of RAM overall and over 500MB still available. Not a RAM issue. > Would you mind sharing the results of `netstat -st` ? I'd rather not share those kinds of outputs publicly. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Loss of Stable flag
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 not aware of any issues. Would any of the directory authority operators be able to shed light on why some of the DAs are not assigning it the flag? Thanks! ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Overloaded state indicator on relay-search
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 that a single DNS timeout error within a 72-hour period will result in an overloaded state? If so, it seems overly-stringent given that there are no options available to tune the DNS timeout, max retry etc. parameters. Some lower-specced servers with less than optimal access to DNS resolvers will suffer because of this. Also, I was wondering why these timeouts were not being recorded in the Metrics output. I've done some digging and I believe there is a bug in the evdns_callback() function. The rep_hist_note_dns_error() is being called as follows: rep_hist_note_dns_error(type, result); but I've noticed the 'type' being set to zero whenever libevent returns a DNS error which means the correct dns_stats_t structure is never found, as zero is outside the expected range of values (DNS_IPv4_A, DNS_PTR, DNS_IPv6_). Adding the BUG assertion confirms this. Please let me know if I should raise this in the bug tracker or if you need anything else. Thanks, Arlen ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Overloaded state indicator on relay-search
> 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 the cause :-/___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Overloaded state indicator on relay-search
> 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=VinculumGate Thanks, I was looking at the cached-descriptors file which I can see now is well out of date. Would anyone have any other suggestions regarding why the relay is overloaded? ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Overloaded state indicator on relay-search
> 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 server descriptor. It seems to be missing the 'overload-general' flag which means it now isn't overloaded? Yet the relay search page says it is? This is all seems a bit more troublesome than it should be. Presumably the relay itself knows why it is overloaded so can it not just state the reason clearly in the logs?___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Overloaded state indicator on relay-search
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 retrieved the metrics into a file and inspected it but it is still not clear to me what the problem is. The only non-zero values I can see are reason="success" or action="processed". Nothing sticks out in the process logs either. Can anyone assist? Regards, Arlen ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Unreachable DirPorts
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 unreachable or unconfigured and is not showing the 'Latest server descriptor' and 'Latest extra-info descriptor' buttons at the bottom of the page. Would anyone be able help me troubleshoot this? Many thanks and regards, Arlen ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
