Noticed that one of my relays (OhNoAnotherRelay02) is showing as
off-line. Looking at the logs, I see a bunch of these messages:
Oct 18 08:39:16.000 [notice] Channel padding timeout scheduled 143041ms
in the past.
Oct 18 08:39:21.000 [notice] Channel padding timeout scheduled 156925ms
in the
On 17 Oct (13:54:22), Arlen Yaroslav via tor-relays wrote:
> Hi,
Hi Arlen!
>
> 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
All:
Are the DirectoryAuthority & FallbackDir directives only evaluated at startup
of a Tor instance? I recently ran into an issue where my Tor Relay Farm went
down, due to the manually configured DirectoryAuthority going down and the
FallbackDir didn't seem to back it up.
I know that the
Eddie:
> On 10/13/2021 11:29 PM, Eddie wrote:
>> I currently run 3 relays, across different servers and today I noticed
>> that one has now lost it's Guard and HS Dir flags. What's surprising
>> is that this particular relay has the highest Bandwidth and Consensus
>> Weight of all 3 and has not
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
On 10/16/21 5:56 PM, Bass Down Low via tor-relays wrote:
Hi all,
I am somewhat new to the project and trying to run a couple exits to
help out. I noticed my relay amazinglizard
F80494CE5B2441B67431FFA9CCA571D26BC4F6D8 has bee up for 4 days and not
turned into an exit yet. I noticed the
The bridge IPs should be private enough.
Thanks for your participation!
On 10/17/21 1:59 AM, Josh Lawson via tor-relays wrote:
I work for a bank and was informed that when I connect to my employer network,
it shows I am coming from a Tor IP and sets off an alert that then leads to me
being