Hello all, This is something that's bothered me for quite some time. I often use arm (https://www.torproject.org/projects/arm.html.en) for monitoring my relays and to keep a quick eye on things like overall bandwidth consumed, traffic stats and my favorite client locale statistics. I run it in a screen session and often when I re-attach the session often the keymapping is all messed up and the arrow keys will offer to close arm. Usually it will correct after I shift-m to get to the menu and switch around a few times. Has anyone else experienced this and how did you solve it? -Jason
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/07/2014 07:24 PM, jason@icetor.is wrote:
Hello all, This is something that's bothered me for quite some time. I often use arm (https://www.torproject.org/projects/arm.html.en) for monitoring my relays and to keep a quick eye on things like overall bandwidth consumed, traffic stats and my favorite client locale statistics. I run it in a screen session and often when I re-attach the session often the keymapping is all messed up and the arrow keys will offer to close arm. Usually it will correct after I shift-m to get to the menu and switch around a few times. Has anyone else experienced this and how did you solve it? -Jason _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
It happens to me too, sporadically when arm sits around for a while. Also, sometimes the screen output gets garbled and arm "thinks" I was pressing a key, like x for SIGHUP or q for quit. It looks like the traffic to and from arm gets somehow corrupted. I haven't found a good explanation or any solution yet, other than quitting and restarting arm.
I haven't experienced garbled keymappings yet. The only thing that doesn't seem to work for me is the graphs which don't get painted on OS X. Everything else seems to work just fine. Best regards MacLemon
I've noticed this also on a CentOS system that I manage for someone else.
On 02/07/2014 08:00 PM, MacLemon wrote:
I haven't experienced garbled keymappings yet. The only thing that doesn't seem to work for me is the graphs which don't get painted on OS X. Everything else seems to work just fine. Best regards MacLemon _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Additionally does anyone know what effects the client locale statistics on page 2? I've had those statistics come and go and I can't figure out what causes them to disappear. -J
On 02/07/2014 06:24 PM, jason@icetor.is wrote:
Hello all, This is something that's bothered me for quite some time. I often use arm (https://www.torproject.org/projects/arm.html.en) for monitoring my relays and to keep a quick eye on things like overall bandwidth consumed, traffic stats and my favorite client locale statistics. I run it in a screen session and often when I re-attach the session often the keymapping is all messed up and the arrow keys will offer to close arm. Usually it will correct after I shift-m to get to the menu and switch around a few times. Has anyone else experienced this and how did you solve it? -Jason _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Friday 07 February 2014 20:43:10 jason@icetor.is wrote:
Additionally does anyone know what effects the client locale statistics on page 2? I've had those statistics come and go and I can't figure out what causes them to disappear.
Your relay needs have have the Guard flag in order to see the client local statistics.
On Friday 07 February 2014 18:24:20 jason@icetor.is wrote:
Hello all, This is something that's bothered me for quite some time. I often use arm (https://www.torproject.org/projects/arm.html.en) for monitoring my relays and to keep a quick eye on things like overall bandwidth consumed, traffic stats and my favorite client locale statistics. I run it in a screen session and often when I re-attach the session often the keymapping is all messed up and the arrow keys will offer to close arm. Usually it will correct after I shift-m to get to the menu and switch around a few times. Has anyone else experienced this and how did you solve it?
For me same happens. I always press arrow up and then ESC. After that it works again.
Regards,
torland
1.When installing it on several supposedly identical VPSs ARM won't start on one because it can't find components where they should be. I got a limited, incomrehensible (to me) response from the author so it stays unresolved.
2.ARM asks for a password which doesn't exist which is connected to the opening of the control port in torrc i.e. removing the # at ControlPort 9051 and then choosing HashedControlPassword or CookieAuthentication 1.
It would seem that a graphic programme like ARM would be good to help people who want to run a relay but for whom the command line Linux will be insurmountable and deterrent.
Robert
Hi Jason. Yup, I've seen this as well. I'm hoping that the regression came in with the interpretor panel, which caused some other confusing side effects as well...
https://trac.torproject.org/6439
Unfortunately this issue doesn't have a good, reliable repro besides 'wait for a week and see if it happens' so I'm not yet sure if this addressed the issue or not.
Cheers! -Damian (arm's author)
tor-relays@lists.torproject.org
-
Damian Johnson -
I -
jason＠icetor.is -
MacLemon -
Random Tor Node Operator -
tor-admin