Re: [tor-relays] ARM crashes on connection tor

2011-12-10 Thread Klaus Layer
Thanks for the explanation. You are right. I mixed up socks port 9050 and control port 9051. Thanks, Klaus Damian Johnson wrote on 10.12.2011: > Hi Klaus. This is the first I've seen that particular error. What's > happening is that... > - arm has configured TorCtl to listen to the control po

Re: [tor-relays] ARM crashes on connection tor

2011-12-10 Thread Damian Johnson
Hi Klaus. This is the first I've seen that particular error. What's happening is that... - arm has configured TorCtl to listen to the control port (4711) - TorCtl then receives a message that's invalid according to the control spec from that port and raised that error My guess is that you gave arm

Re: [tor-relays] Logs full of "eventdns: All nameservers have failed"

2011-12-10 Thread Klaus Layer
"Steve Snyder" wrote on 10.12.2011: > > Yes, I also have a local caching nameserver, pointed to by the "nameserver >127.0.0.1" entry in /etc/resolve.conf. Also, it seems that Tor/libevent is >smart enough to filter out duplicate DNS servers as 3 copies of "nameserver >127.0.0.1" doesn't give

Re: [tor-relays] Logs full of "eventdns: All nameservers have failed"

2011-12-10 Thread Steve Snyder
On Saturday, December 10, 2011 5:58am, "Klaus Layer" said: >> Could you clarify the configuration? Is Tor doing DNS over the GigE or >> to localhost? >> >> -andy > Yes I have configure a local caching DNS server. cat /etc/resolve.conf shows > nameserver 127.0.0.1. So I assume TOR resolves via t

Re: [tor-relays] ARM crashes on connection tor

2011-12-10 Thread Jordi Espasa
Send an email to the author. He will help you kindly, sure. -- I will face my fear. I will permit it to pass over me and through me. And when it has gone past I will turn the inner eye to see its path. Where the fear has gone there will be nothing. Only I will remain. __

Re: [tor-relays] Bandwidth Authority PID Feedback Experiment #2 Starting

2011-12-10 Thread Moritz Bartl
On 10.12.2011 11:30, Andy Isaacson wrote: >> Please keep an eye on your relays and tell us if anything unexpected >> happens over the next week or so. > we're seeing a pretty significant rise in throughput on noisetor01, we > peaked at 530 Mbps at around 2011-12-09 17:00 PST, versus previous > peak

Re: [tor-relays] Logs full of "eventdns: All nameservers have failed"

2011-12-10 Thread Klaus Layer
Andy Isaacson wrote on 10.12.2011: > If it's a decent NIC (Intel or Broadcom) then I'd agree with you. If > it's a RTL or other sub-par vendor / driver, then you're overly > optimistic. lspci shows: 01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 02:00.0 Ethernet

Re: [tor-relays] Bandwidth Authority PID Feedback Experiment #2 Starting

2011-12-10 Thread Andy Isaacson
On Sat, Dec 03, 2011 at 06:57:22PM -0800, Mike Perry wrote: > We'll probably be running this next experiment for about a week (or > perhaps longer if it doesn't explode and seems to improve performance > on https://metrics.torproject.org/performance.html) starting tonight > or tomorrow. > > Please

Re: [tor-relays] Logs full of "eventdns: All nameservers have failed"

2011-12-10 Thread Andy Isaacson
On Mon, Dec 05, 2011 at 10:35:03PM +0100, Klaus Layer wrote: > Andy Isaacson wrote on 03.12.2011: > > Since DNS is the most frequent UDP traffic you'll see on a Tor node, > > perhaps this is simply a symptom of high packet loss on your NIC. > > It's a gigabit link, with at the moment only 30% load

[tor-relays] ARM crashes on connection tor

2011-12-10 Thread Klaus Layer
Hi, I am no longer able to connect with ARM to one of my relays. ARM crashes with the following error: debian-tor@host:/home/user$ arm -i 127.0.0.1:4711 Traceback (most recent call last): File "/usr/share/arm/TorCtl/TorCtl.py", line 710, in _loop isEvent, reply = self._read_reply() File