Hi tor-relays@ mailing list,
I have set up two exit relays on a FreeBSD 12.0 dedicated server:
https://metrics.torproject.org/rs.html#details/1CD029594B08E07F29B9420410C2…https://metrics.torproject.org/rs.html#details/A0EB2BD840838FAD51BDAD86B0BA…
Looking at my top stats, I get CPU usage of 100% most of the time
(meaning 95% of the time) on both instances pushing around ~1 MB/s with
both instances.
The server is a HP Blade server and has a single Intel Xeon L5520 CPU
with 16GB of RAM.
Tor is configured to have 150 Mbps per instance, with a total of two
instances.
Why am I getting this abnormal CPU usage? What's the solution? I don't
want to use Linux but can use another *BSD or Solaris/Illumos if I must.
-Neel
===
https://www.neelc.org
Hello.
Did anyone noticed unusual connection count spikes for their relays?
My relay encountered several ~1k spikes with rise time ~= 10 minutes:
https://imgur.com/a/6JvB7gp
Maybe it is someone trying to fool anti-DDoS protection?
-- Vort
I run one relay and another tor instance for hidden services and socksport. Haven't had a problem until 0.4.0.2_alpha. Ive had it crash twice so far. Maybe my configs aren't sane?
[err] descriptor at 0x8a0acdb0830 begins with unexpected string "". Is another process running in our data directory? Exiting.
First config
User tor
PIDFile /var/run/tor2/tor2.pid
SOCKSPort 9052
ControlPort 9053
Log notice file /var/lib/tor2/notices.log
RunAsDaemon 1
DataDirectory /var/lib/tor2/data
CookieAuthentication 1
ClientUseIPv6 1
ClientPreferIPv6ORPort 1
ClientPreferIPv6DirPort 1
HiddenServiceDir /var/lib/tor2/ssh/
HiddenServicePort 22 127.0.0.1:22
HiddenServiceDir /var/lib/tor2/ssh-new/
HiddenServiceVersion 3
HiddenServicePort 22 127.0.0.1:22
HiddenServiceDir /var/lib/tor2/bitcoind/
HiddenServicePort 8333 127.0.0.1:8333
Second config
User tor
PIDFile /var/run/tor/tor.pid
Log notice syslog
Log notice file /var/log/tor/debug.log
#Log notice debug file /var/lib/tor/data/tor.log
DataDirectory /var/lib/tor/data
ControlPort 9051
HashedControlPassword
CookieAuthentication 1
ORPort 9001
ORPort []:9050
DirPort 9030
BandwidthRate 4 MBytes
BandwidthBurst 5 MBytes
Nickname PancakeWhore
ContactInfo
ExitPolicy reject *:*
ExitPolicy reject6 *:*
Hi all,
My tor relay has got the UnreachableIpv6 flag set once i mentionned an
OrPort with my ipv6 address.
>From what i can tell, my server is reachable over ipv6, and can contact the
directory authorities through ipv6 (following the instructions found there:
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Makesurerelaypo…
).
The node is behind an haproxy that relays ipv6 traffic to natted ipv4 (with
no logging for those concerned). It seems to work fine for web content over
ipv6, and traffic on both ips (v4 and v6) goes through this channel.
I can successfully telnet my node ORPort using my v6 address. The ports
have been defined this way in torrc:
ORPort 0.0.0.0:9001 NoAdvertise
ORPort 91.121.79.188:9001 NoListen
ORPort [2001:41d0:1:84bc::1]:9001 NoListen
Is there a way to make a tor client connect to a specific relay to debug
this kind of connectivity issues? Or any other mean?
In the meantime ive removed the advertized ip6.
Regards,
Charly
Just an fyi for those who might be interested...
With upgrading to 0.3.5.8 the memory usage of my Tor relay dropped again to reasonable levels. It suddenly started to increase end of January causing my relay to crash twice before leveling around 45% (a week before I had an ISP outage). Now it's back to around 25%. The relay bandwidth consumed over all the time was pretty much stable.
[Memory Used.png]