ARM crashes on connection tor

List overview All Threads
Download

newer

older

bandwidth authority test

Logs full of "eventdns: All...

Klaus Layer

10 Dec 2011 10 Dec '11

9:49 a.m.

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 "/usr/share/arm/TorCtl/TorCtl.py", line 885, in _read_reply raise ProtocolError("Badly formatted reply line: unknown type %r"%tp) ProtocolError: Badly formatted reply line: unknown type 'P' Terminated

To another instance running on the same machine ARM connects without any problem. Has anyone experienced the same issue or knows how to fix it?

Thanks,

Klaus

Attachments:

signature.asc (application/pgp-signature — 316 bytes)

Show replies by date

Jordi Espasa

10 Dec 10 Dec

12:13 p.m.

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.

Damian Johnson

8:08 p.m.

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 the wrong port and there's something else sending data on that port. Per chance did you confuse the SocksPort and ControlPort? If you're sure that the port is correct then please do the following... - run "telnet localhost 4711 - enter "PROTOCOLINFO"

if all is well it should look something like this... atagar@loki:~$ telnet localhost 9051 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. PROTOCOLINFO 250-PROTOCOLINFO 1 250-AUTH METHODS=NULL 250-VERSION Tor="0.2.2.13-alpha" 250 OK QUIT 250 closing connection Connection closed by foreign host.

Cheers! -Damian

Klaus Layer

9:25 p.m.

Thanks for the explanation. You are right. I mixed up socks port 9050 and control port 9051.

Thanks,

Klaus

Damian Johnson atagar1@gmail.com 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 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 the wrong port and there's something else sending data on that port. Per chance did you confuse the SocksPort and ControlPort? If you're sure that the port is correct then please do the following...

run "telnet localhost 4711

enter "PROTOCOLINFO"

if all is well it should look something like this... atagar@loki:~$ telnet localhost 9051 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. PROTOCOLINFO 250-PROTOCOLINFO 1 250-AUTH METHODS=NULL 250-VERSION Tor="0.2.2.13-alpha" 250 OK QUIT 250 closing connection Connection closed by foreign host.

Cheers! -Damian _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

4763

Age (days ago)

4763

Last active (days ago)

tor-relays@lists.torproject.org

3 comments

3 participants

tags (0)

participants (3)

Damian Johnson
Jordi Espasa
Klaus Layer