<html>
<head>
<style>
.sw_message P{margin:0px;padding:0px;}
.sw_message {FONT-SIZE: 12pt;FONT-FAMILY:Tahoma,Arial,Helvetica,sans-serif;background:white;}
.sw_message blockquote{margin-left:5px;padding-left:5px;border-left:2px solid #144fae;color: #144fae;}
.sw_message blockquote blockquote{border-left:2px solid #006312;color: #006312;}
.sw_message blockquote blockquote blockquote{border-left:2px solid #8e5656;color: #8e5656;}
.sw_message blockquote blockquote blockquote blockquote{border-left:2px solid #888;color: #888;}
</style>
</head>
<body class="sw_message">
<div>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.<br><br>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). <br><br><br> <br></div><div id="editor_signature"></div><div>On Friday 30/08/2013 at 4:09 pm, David Carlson wrote: </div><blockquote type="cite">On 8/29/2013 11:09 PM, Andreas Krey wrote:<br><blockquote type="cite"> On Thu, 29 Aug 2013 19:35:37 +0000, Gordon Morehouse wrote:<br> ...<br><blockquote type="cite"> Aug 29 18:19:14.000 [notice] Your network connection speed appears to<br> have changed. Resetting timeout to 60s after 18 timeouts and 172<br> buildtimes.<br></blockquote> Random data point: I had these yesterday on a VPS-based relay.<br><br><blockquote type="cite"> My main question: How do circuit creation requests on one's Tor relay<br> cause load on one's network infrastructure? Is it DNS requests? Is<br> it TCP connection state entries? It's not bandwidth, we observed that<br> above, and my router can handle far faster pipes than the one it's on<br> currently. The DNS failing is a sign that the router is under severe<br> stress.<br></blockquote> Possibly your uplink is full (supposing you're on some DSL), and is<br> starting to build up ping time; then DNS requests to the outside can<br> start to timeout.<br><br> Andreas<br><br><br></blockquote><br>Over roughly the same time frame I received an incredibly high number of<br>spam e-mails in one e-mail account that normally gets 20 or so a day on<br>quiet days. Perhaps this is another example of mal-ware in action.<br><br>David C<br>_______________________________________________<br>tor-relays mailing list<br>tor-relays@lists.torproject.org<br><a target="_blank" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br></blockquote><br>
</body></html>