-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Just to add my experiences to the mix:
I started running a RPi relay back in January. It ran fine for several
months, until I started to get these circuit creation storms
periodically. It would come at random times, maybe once a week, and
would
You could modify the tor init script to limit the memory usable by
/usr/sbin/tor as described here:
http://jlebar.com/2011/6/15/Limiting_the_amount_of_RAM_a_program_can_use.html
But I don’t know if this works on RaspPi platform and what happens when
the tor process hits the memory limit.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
tor-admin:
You could modify the tor init script to limit the memory usable by
/usr/sbin/tor as described here:
http://jlebar.com/2011/6/15/Limiting_the_amount_of_RAM_a_program_can_use.html
But I don’t know if this works on RaspPi platform
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Andreas Krey:
My main question: How do circuit creation requests on one's Tor
relay cause load on one's network infrastructure? Is it DNS
requests? Is it TCP connection state entries? It's not
bandwidth, we observed that above, and my router
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
krishna e bera:
On 13-08-29 10:35 PM, Gordon Morehouse wrote:
What on earth is causing so many circuit creation requests in
such a short timespan?
One possibility, if i recall correctly, is that the Tor that comes
with the PirateBrowser
On Thu, Aug 29, 2013 at 11:30:33PM -0400, krishna e bera wrote:
On 13-08-29 10:35 PM, Gordon Morehouse wrote:
What on earth is causing so many circuit creation requests in such a
short timespan?
One possibility, if i recall correctly, is that the Tor that comes with
the PirateBrowser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Roger Dingledine:
On Thu, Aug 29, 2013 at 11:30:33PM -0400, krishna e bera wrote:
On 13-08-29 10:35 PM, Gordon Morehouse wrote:
What on earth is causing so many circuit creation requests in
such a short timespan?
[snip]
As for the circuit
I added a second core to my server and it's still getting Your
computer is too slow... error messages. Top shows cpu for the Tor
process hanging around 60-75%, which is where it was before. Top's
system total is hanging around Cpu(s) 25.9%. That plus the VM
manager's graph suggest that the
On 8/29/2013 11:09 PM, Andreas Krey wrote:
On Thu, 29 Aug 2013 19:35:37 +, Gordon Morehouse wrote:
...
Aug 29 18:19:14.000 [notice] Your network connection speed appears to
have changed. Resetting timeout to 60s after 18 timeouts and 172
buildtimes.
Random data point: I had these
On Fri, Aug 30, 2013 at 04:25:27PM -0400, t...@t-3.net wrote:
Also see a repeat of the odd log message with the 154.x net address
someone else described with the huge hexidecimal string (40 hex
chars, + sign, 40 more, on and on).
Just FYI, these messages were popping up pretty regularly in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Since I originally started keeping an eye on these on my Raspberry Pi
relay (read: slow, resource-limited), I've got to wonder if the
circuit creation storms I was seeing months ago weren't normal network
phenomena but some kind of test run.
We are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
So, I started having tubes clogged problems this evening and
realized, finally, that my Raspberry Pi powered relay had been
weathering a circuit creation storm since about 18:11 my time.
tl;dr main dev-related questions at bottom
Aug 29
On 13-08-29 10:35 PM, Gordon Morehouse wrote:
What on earth is causing so many circuit creation requests in such a
short timespan?
One possibility, if i recall correctly, is that the Tor that comes with
the PirateBrowser bundle is configured to build single hop circuits.
Make sure that these
On Thu, 29 Aug 2013 19:35:37 +, Gordon Morehouse wrote:
...
Aug 29 18:19:14.000 [notice] Your network connection speed appears to
have changed. Resetting timeout to 60s after 18 timeouts and 172
buildtimes.
Random data point: I had these yesterday on a VPS-based relay.
My main question:
14 matches
Mail list logo
