Hello.
The node we run is in our library and we have a raspberry pi SSH'ed into the node and an LCD displaying the output from Arm. Arm is bugging out on a random basis and appears to be receiving a C keystroke that I believe is the clear log command. I ran the pi with no keyboard and I even used another machine to display the ARM output from the SSH session and it did the same thing. Has anyone else seen this and is there a solution? It's a real bummer because we use this as a learning tool in our library and the pretty graphs of incoming and outgoing traffic really get people interested. When this phantom keystroke happens the graphs stop and somebody has to press N on the keyboard to get the pretty graphs rolling again. This can happen in 2-3 hours or upto 12 hours. See pic here. http://imgur.com/a/wrMhT
Cheers,
Matt
That's pretty awesome, Matt! I love it.
I don't know what's happening offhand, but I have an idea that will fix one kind of problem.
When you start arm, if you never need to type into it, you can kill all input from outside the program by making its input something else.
$ arm </dev/null
You can still use control-C to interrupt it, but no regular keypresses will flow into arm.
If it could be another problem, I'd think it's that a 'c' isn't being pressed and causing logs to be cleared, but that a log rotator is renaming and expunging logs and that looks like clearing logs and that could look like 'c'. That's a big ugly guess, though.
Hope this helps.
ps, an arg like "-e5" will show few monitor messages and make room for more Tor messages for patrons to gawk at.
On Fri, Sep 23, 2016 at 10:29 AM, Matt Helps matthelps@gmail.com wrote:
Hello.
The node we run is in our library and we have a raspberry pi SSH'ed into the node and an LCD displaying the output from Arm. Arm is bugging out on a random basis and appears to be receiving a C keystroke that I believe is the clear log command. I ran the pi with no keyboard and I even used another machine to display the ARM output from the SSH session and it did the same thing. Has anyone else seen this and is there a solution? It's a real bummer because we use this as a learning tool in our library and the pretty graphs of incoming and outgoing traffic really get people interested. When this phantom keystroke happens the graphs stop and somebody has to press N on the keyboard to get the pretty graphs rolling again. This can happen in 2-3 hours or upto 12 hours. See pic here. http://imgur.com/a/wrMhT
Cheers,
Matt
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Matt Helps:
Hello.
The node we run is in our library and we have a raspberry pi SSH'ed into the node and an LCD displaying the output from Arm. Arm is bugging out on a random basis and appears to be receiving a C keystroke that I believe is the clear log command. I ran the pi with no keyboard and I even used another machine to display the ARM output from the SSH session and it did the same thing. Has anyone else seen this and is there a solution?
Yes, it's a known issue that has been in arm for a while, random clobbering of the output and even random 'xx' and 'cc' commands.
It's a real bummer because we use this as a learning tool in our library and the pretty graphs of incoming and outgoing traffic really get people interested. When this phantom keystroke happens the graphs stop and somebody has to press N on the keyboard to get the pretty graphs rolling again. This can happen in 2-3 hours or upto 12 hours. See pic here. http://imgur.com/a/wrMhT
A nasty fix might be to send a fake esc or ^L keystroke every minute or so to restore normal output.
Hi Matt, sorry this is nailing you. I've seen it as well and have been pretty puzzled by it. The issue first started manifesting in the late 1.4.x series making me suspect it's related to the interpreter panel but I never found out exactly what was up. Unfortunately the bug can take days to manifest, making it tough to reproduce.
As you may have noticed arm hasn't had a release since 2012. This last year I've focused on fixing that. Nyx is the new version of arm, rebuilt from the ground up under the hood...
https://gitweb.torproject.org/nyx.git/log/
No doubt it'll initially have lots of warts of its own, but between Stem and test coverage should grow to be much more stable in the long run. I don't have a release date for you yet but I'll let this list know when I'm ready for beta testers.
Cheers! -Damian (nyx's author)
On Fri, Sep 23, 2016 at 7:29 AM, Matt Helps matthelps@gmail.com wrote:
Hello.
The node we run is in our library and we have a raspberry pi SSH'ed into the node and an LCD displaying the output from Arm. Arm is bugging out on a random basis and appears to be receiving a C keystroke that I believe is the clear log command. I ran the pi with no keyboard and I even used another machine to display the ARM output from the SSH session and it did the same thing. Has anyone else seen this and is there a solution? It's a real bummer because we use this as a learning tool in our library and the pretty graphs of incoming and outgoing traffic really get people interested. When this phantom keystroke happens the graphs stop and somebody has to press N on the keyboard to get the pretty graphs rolling again. This can happen in 2-3 hours or upto 12 hours. See pic here. http://imgur.com/a/wrMhT
Cheers,
Matt
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org