Relay overload information has been added to relay descriptors since 0.4.6+ but it was not until Tor >= 0.4.7.1-alpha that an interface to the underlying relay metrics was available: the metrics port. To understand the well-being of Tor relays and the Tor network it is vital to provide and have access to relay metrics. You need to add the configuration to /etc/nf or to a file in /etc/sysctl.d/ to make it permanent. Keep in mind that tuning sysctl as described is not permanent and will be lost upon restart. If you are experiencing TCP port exhaustion consider expanding your local port range. Tuning sysctl for network, memory and CPU load TCP port exhaustion If you notice that your relay is overloaded please:Ĭheck for any known issues in the "Tor network" category.Ĭonsider tuning sysctl for your system for network, memory and CPU load.Ĭonsider enabling MetricsPort to understand what is happening. Note that if a relay reaches an overloaded state we show it for 72 hours after the relay has recovered. Any Tor OOM invocation due to memory pressure. ![]() This means that one or many of the following load metrics have been triggered: On relay search we show an amber dot next to the relay nickname when it is overloaded.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |