Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2022-10-17T19:28:07Zhttps://gitlab.torproject.org/legacy/trac/-/issues/19969tor client does not immediately open new circuits after standby2022-10-17T19:28:07Zweasel (Peter Palfrader)tor client does not immediately open new circuits after standbyViktor writes via https://bugs.debian.org/835119:
I use tor only as a client to connect icedove to the tor network with
the extension Torbirdy (on port 9050). With the tor version 0.2.8.6 I
can't immediately connect to any mail server o...Viktor writes via https://bugs.debian.org/835119:
I use tor only as a client to connect icedove to the tor network with
the extension Torbirdy (on port 9050). With the tor version 0.2.8.6 I
can't immediately connect to any mail server or news feed after the pc
woke up from standby ("long" time in standby) and I started icedove. I
have to wait for several minutes in order to connect successfully, but
the timespan seems to be random. This does not occur after a (re)boot.
The first version I remember to have this issue is 0.2.8.6-2, I did an
upgrade from 0.2.7.6-1 to 0.2.8.6-2, so I skipped the alpha and rc
versions and the first upload to unstable. I am very sure that the issue
didn't occur in version 0.2.7.6-1 which I used for several months. I can
exclude network connectivity problems because e.g. I can immediately
start the Tor Browser after standby.
Today I purged tor, installed version 0.2.7.6-1, copied the old "state"
file to /var/lib/tor, and set the pc in standby mode for a couple of
minutes. After waking up from standby I immediately tried to connect to
a mail server which worked. Then I upgraded step by step to every
version of tor 0.2.8 which I could find on snapshot.debian.org and tried
to connect to a mail server immediately after waking up from standby.
Unfortunately I could not reproduce the bug then. Finally with version
0.2.8.6-3 the bug occured again, but only after a "long" standby time
(almost 90 minutes).
Attached are two log files from the weekend and the complete log from
today after the installation of version 0.2.7.6-1.
As you can see, the bug is not easily reproducible, and the logs don't
show any particular reason for why tor does not open new circuits
immediately. Please tell me what I can do to give you more information
about the bug.Tor: 0.2.8.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/19966torproxy goes south with more than 1 connection attempt per second to a hidde...2020-06-13T15:00:28ZTractorproxy goes south with more than 1 connection attempt per second to a hidden serviceI have a web service running as a tor hidden service. I have a test script that connects to the hidden service through tor proxy, sends a short string, gets a short reply, and then the hidden service closes the connection. Each time th...I have a web service running as a tor hidden service. I have a test script that connects to the hidden service through tor proxy, sends a short string, gets a short reply, and then the hidden service closes the connection. Each time the test script connects, it uses a different socks username, so it should get a fresh tor circuit each time.
This works mostly ok with Tor v0.2.7.6 (git-7a489a6389110120) running on Windows 7 with Libevent 2.0.22-stable, OpenSSL 1.0.1t and Zlib 1.2.8. With four test scripts, it makes about 1 connection per second. Obviously, with any network, it is going to get some connection and network errors, but it recovers eventually.
With Tor v0.2.8.6 (git-4d217548e3f05569) running on Windows 7 with Libevent 2.0.22-stable, OpenSSL 1.0.1t and Zlib 1.2.8, it doesn't run so well. Up to about one connection every two seconds, it runs ok, but as soon as I go above that, tor proxy goes south and starts refusing all connections and the logging error messages shown below. This behavior makes is unsuitable/unreliable to use in a "production" environment.
It seems to not matter what version of tor I use on the hidden service side--only the version on the client side seems to matter, and that is where the errors messages are seen.
This is the contents of my torrc file, which works under v0.2.7.6 but not under v0.2.8.6.
Log notice stdout
LogMessageDomains 1
SafeLogging 0
MaxClientCircuitsPending 200
KeepalivePeriod 15
SocksTimeout 60
NewCircuitPeriod 1
LearnCircuitBuildTimeout 1
CircuitBuildTimeout 60
NumEntryGuards 20
The error messages are:
Aug 23 18:30:32.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:32.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:34.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:34.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:35.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:35.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:35.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:35.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:36.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:36.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:36.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:36.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:36.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:36.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:37.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:37.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:37.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:37.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:37.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:37.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:37.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:37.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:38.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:38.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:39.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:39.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:39.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:39.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:39.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:40.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:40.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:40.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:40.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:40.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:40.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:40.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:40.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:41.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:41.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:42.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:42.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:42.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:42.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:42.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:42.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:42.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:42.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:42.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:42.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:42.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:42.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:43.000 [warn] {REND} Fetching v2 rendezvous descriptor failed. Retrying at another directory.
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
Aug 23 18:30:43.000 [notice] {REND} Closing stream for 'vgfdgkr7tudleiq3.onion': hidden service is unavailable (try again later).
**Trac**:
**Username**: AlanTor: 0.3.1.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/19953DataDirectoryGroupReadable does not take effect when relay enabled2020-06-13T15:00:24ZTracDataDirectoryGroupReadable does not take effect when relay enabledAdd 'DataDirectoryGroupReadable 1'
Permissions on /var/lib/tor are as expected: 0750
Now, uncomment 'ORPort 9001':
Permissions on /var/lib/tor briefly switch to 0750 but then back to 0700,
despite DataDirectoryGroupReadable being still ...Add 'DataDirectoryGroupReadable 1'
Permissions on /var/lib/tor are as expected: 0750
Now, uncomment 'ORPort 9001':
Permissions on /var/lib/tor briefly switch to 0750 but then back to 0700,
despite DataDirectoryGroupReadable being still set to 1.
The patch for Ticket #17562 that adds DataDirectoryGroupReadable option did not change all calls to check_private_dir:
https://trac.torproject.org/projects/tor/attachment/ticket/17562/0002-Introduce-DataDirectoryGroupReadable-boolean.patch
Patch that fixes the issue is attached to this ticket. But, ideally, should factor the check for data dir into a function, but I figured a dev can do that instead of me dabbling with the code.
**Trac**:
**Username**: redfishTor: 0.3.0.x-finalDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/19937Merge isis patch [ticket#?] to 028 stable2020-06-13T15:00:21ZIsabela FernandesMerge isis patch [ticket#?] to 028 stablehttps://gitlab.torproject.org/legacy/trac/-/issues/19931curve25519-donna runtime math errors on armhf2020-06-13T15:00:20ZTraccurve25519-donna runtime math errors on armhfOn a rasppi3, run Ubuntu Core,
http://people.canonical.com/~mvo/all-snaps/16/all-snaps-pi2.img.xz
unxz, dd to card. boot. ubuntu/ubuntu username and password.
Install the tor-middle-relay snap, which was compiled with --enable-expens...On a rasppi3, run Ubuntu Core,
http://people.canonical.com/~mvo/all-snaps/16/all-snaps-pi2.img.xz
unxz, dd to card. boot. ubuntu/ubuntu username and password.
Install the tor-middle-relay snap, which was compiled with --enable-expensive-hardening and --enable-gcc-warnings: 'sudo snap install tor-middle-relay'
It will run, and emit to /var/log/syslog
src/ext/curve25519_donna/curve25519-donna.c:310:25: runtime error: left shift of negative value -54871
src/ext/curve25519_donna/curve25519-donna.c:300:23: runtime error: left shift of negative value -34426
src/ext/curve25519_donna/curve25519-donna.c:218:27: runtime error: left shift of negative value -1052007405335134
src/ext/curve25519_donna/curve25519-donna.c:219:27: runtime error: left shift of negative value -1052007405335134
src/ext/curve25519_donna/curve25519-donna.c:224:27: runtime error: left shift of negative value -3270924659300114
src/ext/curve25519_donna/curve25519-donna.c:225:27: runtime error: left shift of negative value -3270924659300114
src/ext/curve25519_donna/curve25519-donna.c:230:27: runtime error: left shift of negative value -1471294915178450
src/ext/curve25519_donna/curve25519-donna.c:231:27: runtime error: left shift of negative value -1471294915178450
src/ext/curve25519_donna/curve25519-donna.c:209:27: runtime error: left shift of negative value -829694144934512
src/ext/curve25519_donna/curve25519-donna.c:210:27: runtime error: left shift of negative value -829694144934512
src/ext/curve25519_donna/curve25519-donna.c:212:27: runtime error: left shift of negative value -2269747493562282
src/ext/curve25519_donna/curve25519-donna.c:213:27: runtime error: left shift of negative value -2269747493562282
src/ext/curve25519_donna/curve25519-donna.c:215:27: runtime error: left shift of negative value -2894814430932928
src/ext/curve25519_donna/curve25519-donna.c:216:27: runtime error: left shift of negative value -2894814430932928
src/ext/curve25519_donna/curve25519-donna.c:221:27: runtime error: left shift of negative value -3930039718593350
src/ext/curve25519_donna/curve25519-donna.c:222:27: runtime error: left shift of negative value -3930039718593350
src/ext/curve25519_donna/curve25519-donna.c:227:27: runtime error: left shift of negative value -7442567708082396
src/ext/curve25519_donna/curve25519-donna.c:228:27: runtime error: left shift of negative value -7442567708082396
src/ext/curve25519_donna/curve25519-donna.c:233:27: runtime error: left shift of negative value -1428303790038902
src/ext/curve25519_donna/curve25519-donna.c:234:27: runtime error: left shift of negative value -1428303790038902
src/ext/curve25519_donna/curve25519-donna.c:314:27: runtime error: left shift of negative value -79097269
src/ext/curve25519_donna/curve25519-donna.c:315:27: runtime error: left shift of negative value -79097269
src/ext/curve25519_donna/curve25519-donna.c:324:23: runtime error: left shift of negative value -22
src/ext/curve25519_donna/curve25519-donna.c:461:10: runtime error: left shift of negative value -21802520
src/ext/curve25519_donna/curve25519-donna.c:462:10: runtime error: left shift of 1352663040 by 8 places cannot be represented in type 'int'
src/ext/curve25519_donna/curve25519-donna.c:463:10: runtime error: left shift of 1073741824 by 4 places cannot be represented in type 'int'
src/ext/curve25519_donna/curve25519-donna.c:599:12: runtime error: left shift of 34457694 by 6 places cannot be represented in type 'int'
src/ext/curve25519_donna/curve25519-donna.c:464:10: runtime error: left shift of negative value -2147483648
src/ext/curve25519_donna/curve25519-donna.c:465:10: runtime error: left shift of negative value -2147483648
which seems bad. It doesn't happen on amd64 snap.
**Trac**:
**Username**: chadmillerTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/19824/var/run/tor/control socket not created because of /var/run/tor permission issue2020-06-13T14:59:54Zadrelanos/var/run/tor/control socket not created because of /var/run/tor permission issueUsing Tor `0.2.8.6` from deb.torproject.org, `/var/run/tor/control` is no longer created because of a permission issue. As a manual workaround, `sudo chmod --recursive 700 /var/run/tor` works.
The symptom in Tor's log is the following:
...Using Tor `0.2.8.6` from deb.torproject.org, `/var/run/tor/control` is no longer created because of a permission issue. As a manual workaround, `sudo chmod --recursive 700 /var/run/tor` works.
The symptom in Tor's log is the following:
```
Aug 03 17:36:33.000 [warn] Permissions on directory /var/run/tor are too permissive.
```
Rather than `755` Tor's `/lib/systemd/system/tor@default.service` should use `700`. I.e. rather than using:
```
ExecStartPre=/usr/bin/install -Z -m 02755 -o debian-tor -g debian-tor -d /var/run/tor
```
`/lib/systemd/system/tor@default.service` should use:
```
ExecStartPre=/usr/bin/install -Z -m 02700 -o debian-tor -g debian-tor -d /var/run/tor
```Tor: 0.3.1.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/19821--expensive-hardening makes configure check for curve25519-donna-c64 to fail2020-06-13T14:59:53Zyurivict271--expensive-hardening makes configure check for curve25519-donna-c64 to failOn FreeBSD 10.3 the error message is:
```
# cc -o conftest -O2 -pipe -fstack-protector -fno-strict-aliasing -static -fsanitize=address -fsanitize=undefined -fno-omit-frame-pointer -fasynchronous-unwind-tables -Is
rc/common -Wl,-rpath...On FreeBSD 10.3 the error message is:
```
# cc -o conftest -O2 -pipe -fstack-protector -fno-strict-aliasing -static -fsanitize=address -fsanitize=undefined -fno-omit-frame-pointer -fasynchronous-unwind-tables -Is
rc/common -Wl,-rpath,/usr/local/lib -fstack-protector x.c -lpthread -lexecinfo
/tmp/x-85cb71.o: In function `asan.module_ctor':
x.c:(.text+0x65): undefined reference to `__asan_init_v3'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
```
Another failure in configure phase 'checking size of int8_t... 0' makes it to fail entirely.
Sanitizer options are causing this.
expensive-hardening isn't normally enabled by the port. I tried to enable it and ran into this problem.
To reproduce: in FreeBSD port security/tor add this line 'CONFIGURE_ARGS+=--enable-expensive-hardening' and run make.Tor: 0.2.8.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/19819100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.62020-06-13T14:59:52ZTrac100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6Upgraded from Tor 0.2.8.5-rc to 0.2.8.6 on a pi2 using http://deb.torproject.org/torproject.org/dists/jessie/
on start-up it goes to 100% CPU usage and after about 3 minutes default service kills and restarts tor, this goes into a loop...Upgraded from Tor 0.2.8.5-rc to 0.2.8.6 on a pi2 using http://deb.torproject.org/torproject.org/dists/jessie/
on start-up it goes to 100% CPU usage and after about 3 minutes default service kills and restarts tor, this goes into a loop, last message in tor log: Bootstrapped 0%: Starting
**Trac**:
**Username**: hackticTor: 0.2.8.x-final