OK, thanks, I think that worked. Nyx is running and tor-arm is uninstalled.
And: Yes there is a log which I enclosed to this message. I not able to see
anything helpful in it.
Tor has now a uptime of about 22 hrs, it ran with an up-/download-average of
about 47 KB/sec which is really low.
Now
> Suggestion: DoSCircuitCreationMinConnections=1 be established in consensus
The man page for the above option says:
"Minimum threshold of concurrent connections before a client address can be
flagged as executing a circuit creation DoS. In other words, once a client
address reaches the circui
Came in a day early with six authorities voting yea and three voting nay.
Implies the median uptime percentage for guard candidates is slightly under
95.8.
NSDFreedom_guard_recovery.xls
Description: Binary data
___
tor-relays mailing list
tor-relays@l
Please note:
Here parameter DoSCircuitCreationMinConnections=1 is set (rather than the
default value of 3).
Mar 11 17:23:53 Tor[]: DoS mitigation since startup: 0 circuits rejected . . .
. . .
Mar 22 11:23:54 Tor[]: DoS mitigation since startup: 299608 circuits rejected.
. .
Mar 22 17:23:54 Tor
On 21.03.2018 13:46, Gary wrote:
> Firstly, delete what you dont want from
> /usr/share/tor/tor-service-defaults-torrc file and its copies.
Please don't. As general advice, really avoid messing with configuration
files that ship with the distribution. Editing files in /usr/share is
*never* a good
Understandably I got the following question from an operator (off-list):
> How do we fix this?
This was my answer:
For fast exits we generally recommend to run a local caching and validating
resolver like unbound, without using forwarding.
Besides being more reliable this also improves latency
Hi,
smichel0:
> This morning nyx was still working but tor was down - now restarting.
The Tor daemon (instance) is unrelated to nyx, arm or other software that
monitors your Tor relay. In order to verify if the Tor daemon is running on your
system you should check the logs usually under '/var/log
