Opened 5 years ago

Closed 5 years ago

#14352 closed enhancement (worksforme)

Your computer is too slow to handle this many circuit creation requests

Reported by: igb Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: Tor: 0.2.6.2-alpha
Severity: Keywords: Your computer is too slow to handle this many circuit creation requests
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Running a middle relay on a beaglebone black (slightly more powerful than a raspberry pi, but not much). It has been running for a few months and I've never hit this issue before (had an unrelated downtime near xmas)

https://atlas.torproject.org/#details/E747773C61CF671A222EB913DE17DA33074A6D76

tor --version
Tor version 0.2.6.2-alpha (git-6cb1daf062df5252).

I was reading tickets and posts that were guessing this was related to getting hit with a ton of requests once becoming a hsdir or guard for a popular HS. Currently atlas shows the flags that my relay had before it was killed as:

Fast HSDir Running Stable V2Dir Valid

torrc:
DirPort 9
ORPort 443
#ControlPort 9051
#CookieAuthentication 1
Exitpolicy reject *:*
Nickname hailden
SocksPort 0
User debian
DataDirectory /usr/local/etc/tor
BandwidthRate 7MBytes
BandwidthBurst 10MBytes
AvoidDiskWrites 1
EntryStatistics 1
ConnDirectionStatistics 1
HiddenServiceStatistics 1

ulimits (stupidly set too high for open files at least)
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 3948
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 20000
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 3948
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

Under normal operating mode the relay would hover around 1200-1800 current open connections (as reported by netstat -tnp|grep tor|wc -l
The log below shows I had 1661 active circuits before the event.

log:
Jan 25 07:03:30.000 [notice] Heartbeat: Tor's uptime is 21 days 11:58 hours, with 1661 circuits open. I've sent 825.06 GB and received 785.37 GB.
Jan 25 07:03:30.000 [notice] Average packaged cell fullness: 99.111%
Jan 25 07:03:30.000 [notice] TLS write overhead: 2%
Jan 25 07:03:30.000 [notice] Circuit handshake stats since last time: 15429/15437 TAP, 31594/31610 NTor.
Jan 25 09:49:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a mor
e restricted exit policy.
Jan 25 09:50:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [464 similar message(s) suppressed in last 60 seconds]
Jan 25 09:51:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [3637 similar message(s) suppressed in last 60 seconds]
Jan 25 09:52:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [11818 similar message(s) suppressed in last 60 seconds]
Jan 25 09:53:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [12897 similar message(s) suppressed in last 60 seconds]
Jan 25 09:54:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [9473 similar message(s) suppressed in last 60 seconds]
Jan 25 09:55:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [6647 similar message(s) suppressed in last 60 seconds]
Jan 25 09:56:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [6465 similar message(s) suppressed in last 60 seconds]
Jan 25 09:57:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [4433 similar message(s) suppressed in last 60 seconds]
Jan 25 09:58:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [4016 similar message(s) suppressed in last 60 seconds]
Jan 25 09:59:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [4118 similar message(s) suppressed in last 60 seconds]
Jan 25 10:00:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [3643 similar message(s) suppressed in last 60 seconds]
Jan 25 10:01:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [4178 similar message(s) suppressed in last 60 seconds]
Jan 25 10:02:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [4087 similar message(s) suppressed in last 60 seconds]
Jan 25 10:03:22.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [4708 similar message(s) suppressed in last 60 seconds]
Killed

cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 993.47
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2

Hardware : Generic AM33XX (Flattened Device Tree)
Revision : 0000
Serial : 0000000000000000

Admittedly I set my torrc bandwidth configs a little high (but not orders of magnitude too high), along with my ulimit open files. I'll fix those and see if it happens again.
I'm guessing my OS killed the tor process due to resource constraints, along with no core file being generated.

All the related tickets and discussion I could find were from over a year ago so I wanted to let anyone that cared know this can still happen with the latest alpha release.

Let me know if there is more I can do.

related:
https://lists.torproject.org/pipermail/tor-relays/2013-August/002642.html
https://lists.torproject.org/pipermail/tor-relays/2013-June/002184.html
http://archives.seul.org/or/talk/Dec-2007/msg00303.html

Child Tickets

Change History (1)

comment:1 Changed 5 years ago by nickm

Resolution: worksforme
Status: newclosed

Hi! The tor-relays mailing list can help with this issue. This bug tracker isn't a great place for support.

Note: See TracTickets for help on using tickets.