[tor-relays] A bit more evidence on circuit creation storms

[tor at t-3.net]

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 server's not doing much with the 
second core.

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).





On Friday 30/08/2013 at 4:09 pm, David Carlson  wrote:
> On 8/29/2013 11:09 PM, Andreas Krey wrote:
>>
>> On Thu, 29 Aug 2013 19:35:37 +0000, 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:  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 can handle far faster pipes than the one it's on
>>> currently.  The DNS failing is a sign that the router is under severe
>>> stress.
>> Possibly your uplink is full (supposing you're on some DSL), and is
>> starting to build up ping time; then DNS requests to the outside can
>> start to timeout.
>>
>> Andreas
>>
>>
>
> Over roughly the same time frame I received an incredibly high number 
> of
> spam e-mails in one e-mail account that normally gets 20 or so a day 
> on
> quiet days.  Perhaps this is another example of mal-ware in action.
>
> David C
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20130830/0e8eae37/attachment.html>